diff options
author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2014-11-10 08:33:56 +0000 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2014-11-25 13:57:26 +0000 |
commit | bf4bea8e9a9058319a19f8c2710a6f0ef2459983 (patch) | |
tree | 192e21f7d1509b7ea3303ac64bc21f9123bffcd4 /drivers/usb/Kconfig | |
parent | 07a9748c78cfc39b54f06125a216b67b9c8f09ed (diff) | |
download | linux-bf4bea8e9a9058319a19f8c2710a6f0ef2459983.tar.gz linux-bf4bea8e9a9058319a19f8c2710a6f0ef2459983.tar.bz2 linux-bf4bea8e9a9058319a19f8c2710a6f0ef2459983.zip |
kvm: fix kvm_is_mmio_pfn() and rename to kvm_is_reserved_pfn()
This reverts commit 85c8555ff0 ("KVM: check for !is_zero_pfn() in
kvm_is_mmio_pfn()") and renames the function to kvm_is_reserved_pfn.
The problem being addressed by the patch above was that some ARM code
based the memory mapping attributes of a pfn on the return value of
kvm_is_mmio_pfn(), whose name indeed suggests that such pfns should
be mapped as device memory.
However, kvm_is_mmio_pfn() doesn't do quite what it says on the tin,
and the existing non-ARM users were already using it in a way which
suggests that its name should probably have been 'kvm_is_reserved_pfn'
from the beginning, e.g., whether or not to call get_page/put_page on
it etc. This means that returning false for the zero page is a mistake
and the patch above should be reverted.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'drivers/usb/Kconfig')
0 files changed, 0 insertions, 0 deletions