mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-08-26 10:49:33 +00:00
s390/pci: clarify comment in s390_mmio_read/write
The existing comment was talking about reading in the write part and vice versa. While we are here make it more clear why restricting the syscalls to MIO capable devices is okay. Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
This commit is contained in:
parent
411155820b
commit
4631f3ca49
1 changed files with 12 additions and 8 deletions
|
@ -155,10 +155,12 @@ SYSCALL_DEFINE3(s390_pci_mmio_write, unsigned long, mmio_addr,
|
|||
return -EINVAL;
|
||||
|
||||
/*
|
||||
* Only support read access to MIO capable devices on a MIO enabled
|
||||
* system. Otherwise we would have to check for every address if it is
|
||||
* a special ZPCI_ADDR and we would have to do a get_pfn() which we
|
||||
* don't need for MIO capable devices.
|
||||
* We only support write access to MIO capable devices if we are on
|
||||
* a MIO enabled system. Otherwise we would have to check for every
|
||||
* address if it is a special ZPCI_ADDR and would have to do
|
||||
* a get_pfn() which we don't need for MIO capable devices. Currently
|
||||
* ISM devices are the only devices without MIO support and there is no
|
||||
* known need for accessing these from userspace.
|
||||
*/
|
||||
if (static_branch_likely(&have_mio)) {
|
||||
ret = __memcpy_toio_inuser((void __iomem *) mmio_addr,
|
||||
|
@ -282,10 +284,12 @@ SYSCALL_DEFINE3(s390_pci_mmio_read, unsigned long, mmio_addr,
|
|||
return -EINVAL;
|
||||
|
||||
/*
|
||||
* Only support write access to MIO capable devices on a MIO enabled
|
||||
* system. Otherwise we would have to check for every address if it is
|
||||
* a special ZPCI_ADDR and we would have to do a get_pfn() which we
|
||||
* don't need for MIO capable devices.
|
||||
* We only support read access to MIO capable devices if we are on
|
||||
* a MIO enabled system. Otherwise we would have to check for every
|
||||
* address if it is a special ZPCI_ADDR and would have to do
|
||||
* a get_pfn() which we don't need for MIO capable devices. Currently
|
||||
* ISM devices are the only devices without MIO support and there is no
|
||||
* known need for accessing these from userspace.
|
||||
*/
|
||||
if (static_branch_likely(&have_mio)) {
|
||||
ret = __memcpy_fromio_inuser(
|
||||
|
|
Loading…
Reference in a new issue