summaryrefslogtreecommitdiffstats
path: root/tcg/tcg.c
diff options
context:
space:
mode:
authorHuang Ying <ying.huang@intel.com>2011-03-02 08:56:20 +0100
committerMarcelo Tosatti <mtosatti@redhat.com>2011-03-15 01:19:06 -0300
commit3c85e74fbf9e5a39d8d13ef91a5f3dd91f0bc8a8 (patch)
treec9e4334842cbf7a95ecc802722f4595b99bf9cf2 /tcg/tcg.c
parentcd19cfa23609dc1a35dd34f0b7554a8462337fde (diff)
downloadhqemu-3c85e74fbf9e5a39d8d13ef91a5f3dd91f0bc8a8.zip
hqemu-3c85e74fbf9e5a39d8d13ef91a5f3dd91f0bc8a8.tar.gz
KVM, MCE, unpoison memory address across reboot
In Linux kernel HWPoison processing implementation, the virtual address in processes mapping the error physical memory page is marked as HWPoison. So that, the further accessing to the virtual address will kill corresponding processes with SIGBUS. If the error physical memory page is used by a KVM guest, the SIGBUS will be sent to QEMU, and QEMU will simulate a MCE to report that memory error to the guest OS. If the guest OS can not recover from the error (for example, the page is accessed by kernel code), guest OS will reboot the system. But because the underlying host virtual address backing the guest physical memory is still poisoned, if the guest system accesses the corresponding guest physical memory even after rebooting, the SIGBUS will still be sent to QEMU and MCE will be simulated. That is, guest system can not recover via rebooting. In fact, across rebooting, the contents of guest physical memory page need not to be kept. We can allocate a new host physical page to back the corresponding guest physical address. This patch fixes this issue in QEMU-KVM via calling qemu_ram_remap() to clear the corresponding page table entry, so that make it possible to allocate a new page to recover the issue. [ Jan: rebasing and tiny cleanups] Signed-off-by: Huang Ying <ying.huang@intel.com> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'tcg/tcg.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud