diff options
author | Huang Ying <ying.huang@intel.com> | 2011-01-30 11:15:49 +0800 |
---|---|---|
committer | Marcelo Tosatti <mtosatti@redhat.com> | 2011-03-17 13:08:27 -0300 |
commit | fafc3dbaac6447ab8f78d2f7f32a521b24fc6b36 (patch) | |
tree | 3934fab022773bc03c8af20021be79d112f584fa /usr | |
parent | 69ebb83e13e514222b0ae4f8bd813a17679ed876 (diff) | |
download | linux-3.10-fafc3dbaac6447ab8f78d2f7f32a521b24fc6b36.tar.gz linux-3.10-fafc3dbaac6447ab8f78d2f7f32a521b24fc6b36.tar.bz2 linux-3.10-fafc3dbaac6447ab8f78d2f7f32a521b24fc6b36.zip |
KVM: Replace is_hwpoison_address with __get_user_pages
is_hwpoison_address only checks whether the page table entry is
hwpoisoned, regardless the memory page mapped. While __get_user_pages
will check both.
QEMU will clear the poisoned page table entry (via unmap/map) to make
it possible to allocate a new memory page for the virtual address
across guest rebooting. But it is also possible that the underlying
memory page is kept poisoned even after the corresponding page table
entry is cleared, that is, a new memory page can not be allocated.
__get_user_pages can catch these situations.
Signed-off-by: Huang Ying <ying.huang@intel.com>
Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'usr')
0 files changed, 0 insertions, 0 deletions