public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Huang Ying <ying.huang@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	Dean Nelson <dnelson@redhat.com>
Subject: Re: QEMU, MCE, unpoison memory address across reboot
Date: Sun, 26 Dec 2010 14:27:26 +0200	[thread overview]
Message-ID: <4D1734AE.30909@redhat.com> (raw)
In-Reply-To: <20101223142803.GD17819@amt.cnet>

On 12/23/2010 04:28 PM, Marcelo Tosatti wrote:
> On Wed, Dec 22, 2010 at 10:52:51AM +0800, Huang Ying wrote:
> >  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 invoke the unpoison
> >  mechanism implemented in Linux kernel to clear the corresponding page
> >  table entry, so that make it possible to allocate a new page to
> >  recover the issue.
> >
> >  Signed-off-by: Huang Ying<ying.huang@intel.com>
>
> >  +struct HWPoisonPage;
> >  +typedef struct HWPoisonPage HWPoisonPage;
> >  +struct HWPoisonPage
> >  +{
> >  +    void *vaddr;
> >  +    QLIST_ENTRY(HWPoisonPage) list;
> >  +};
> >  +
> >  +static QLIST_HEAD(hwpoison_page_list, HWPoisonPage) hwpoison_page_list =
> >  +    QLIST_HEAD_INITIALIZER(hwpoison_page_list);
> >  +
> >  +static void kvm_unpoison_all(void *param)
> >  +{
> >  +    HWPoisonPage *page, *next_page;
> >  +    unsigned long address;
> >  +    KVMState *s = param;
> >  +
> >  +    QLIST_FOREACH_SAFE(page,&hwpoison_page_list, list, next_page) {
> >  +        address = (unsigned long)page->vaddr;
> >  +        QLIST_REMOVE(page, list);
> >  +        kvm_vm_ioctl(s, KVM_UNPOISON_ADDRESS, address);
> >  +        qemu_free(page);
> >  +    }
> >  +}
>
> Can't you free and reallocate all guest memory instead, on reboot, if
> there's a hwpoisoned page? Then you don't need this interface.
>

Alternatively, MADV_DONTNEED?  We already use it for ballooning.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-12-26 12:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22  2:52 QEMU, MCE, unpoison memory address across reboot Huang Ying
2010-12-23 14:28 ` Marcelo Tosatti
2010-12-23 16:57   ` Andi Kleen
2010-12-24  1:21     ` Huang Ying
2010-12-24  3:30   ` Huang Ying
2010-12-27 21:27     ` Marcelo Tosatti
2010-12-26 12:27   ` Avi Kivity [this message]
2010-12-27 21:27     ` Marcelo Tosatti
2010-12-28  6:18       ` Huang Ying
2010-12-28  8:11       ` Avi Kivity
2010-12-28  8:32         ` Huang Ying
2010-12-28  9:05           ` Avi Kivity
2010-12-28  8:27       ` Gleb Natapov
2010-12-28  8:35         ` Huang Ying
2010-12-28  9:06           ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D1734AE.30909@redhat.com \
    --to=avi@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=dnelson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox