summaryrefslogtreecommitdiff
path: root/lib/locking-selftest-hardirq.h
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2014-11-10 11:33:56 +0300
committerPaolo Bonzini <pbonzini@redhat.com>2014-11-26 16:40:45 +0300
commitd3fccc7ef831d1d829b4da5eaa081db55b1e38f3 (patch)
treeb6c81a616eb4a7a43a6fa4641c6554f4d25955b2 /lib/locking-selftest-hardirq.h
parentbb55e9b131d70ab9e30d73ab1342ad4907f9e0de (diff)
downloadlinux-d3fccc7ef831d1d829b4da5eaa081db55b1e38f3.tar.xz
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: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'lib/locking-selftest-hardirq.h')
0 files changed, 0 insertions, 0 deletions