From: Marcelo Tosatti <mtosatti@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Avi Kivity <avi@redhat.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: Mon, 27 Dec 2010 19:27:15 -0200 [thread overview]
Message-ID: <20101227212715.GA13518@amt.cnet> (raw)
In-Reply-To: <1293161437.22308.170.camel@yhuang-dev>
On Fri, Dec 24, 2010 at 11:30:37AM +0800, Huang Ying wrote:
> On Thu, 2010-12-23 at 22:28 +0800, Marcelo Tosatti wrote:
> > 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.
>
> Consider about this method. It seems that some guest RAMs are not
> allocated in qemu_ram_alloc_from_ptr(), that is, host parameter is
> allocated elsewhere and passed in. I found two:
>
> - assigned_dev_register_regions() in hw/device-assignment.c
> - create_shared_memory_BAR() and ivshmem_read() in hw/ivshmem.c
>
> There is no general method to reallocate these memory so far. We may
> need a flag in struct RAMBlock to track these memory, and ignore them
> during reallocation. But if there are hwpoisoned pages in these memory,
> we can not recover. Do you think that is OK?
Yes, these are not guest RAM so there should be no MCE for them.
next prev parent reply other threads:[~2010-12-27 21:30 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 [this message]
2010-12-26 12:27 ` Avi Kivity
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=20101227212715.GA13518@amt.cnet \
--to=mtosatti@redhat.com \
--cc=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=dnelson@redhat.com \
--cc=kvm@vger.kernel.org \
--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