From: Avi Kivity <avi@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Huang Ying <ying.huang@intel.com>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Dean Nelson <dnelson@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [PATCH -v2] Monitor command: pfa2hva, translate guest physical address to host virtual address
Date: Wed, 10 Nov 2010 22:58:35 +0200 [thread overview]
Message-ID: <4CDB077B.5000608@redhat.com> (raw)
In-Reply-To: <20101110191656.GC9011@basil.fritz.box>
On 11/10/2010 09:16 PM, Andi Kleen wrote:
> On Wed, Nov 10, 2010 at 07:47:11PM +0200, Avi Kivity wrote:
> > On 11/10/2010 07:44 PM, Andi Kleen wrote:
> > >> Doing it in userspace in easier, since we can replace the vma for
> > >> that section (and avoid mixed 4k/2M pages in hugetlbfs).
> > >
> > >You can't do that today, there's no way currently to access the non corrupted
> > >portion of the 2MB page. Once it's poisoned it's all gone.
> >
> > I see. Thanks.
>
> BTW my understanding is that KVM will only use hugepages with
> transparent huge pages anyways, correct?
There will always be those who want full control over every last bit;
they will use hugetlbfs and numactl for manual allocation of resources
for guests.
General usage will be with transparent huge pages, though.
> So it may be reasonable to simply fix this as part of the transparent
> hugepages work, but ignore it before that.
Transparent hugepages work only for anonymous memory.
However, hugetlbfs is not the only option for backing -mempath memory;
if poisoning works for tmpfs/shm or other file backed memory, we can use
that to get named access to memory.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-11-10 20:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 2:39 [PATCH -v2] Monitor command: pfa2hva, translate guest physical address to host virtual address Huang Ying
2010-11-01 16:09 ` Marcelo Tosatti
2010-11-01 18:49 ` Anthony Liguori
2010-11-01 19:20 ` Huang Ying
2010-11-01 19:22 ` Anthony Liguori
2010-11-04 16:53 ` Luiz Capitulino
2010-11-06 16:24 ` Avi Kivity
2010-11-08 1:29 ` Huang Ying
2010-11-08 3:39 ` Anthony Liguori
2010-11-08 20:46 ` Huang Ying
2010-11-09 3:06 ` Huang Ying
2010-11-10 6:56 ` Avi Kivity
2010-11-10 6:59 ` Avi Kivity
2010-11-10 7:41 ` Huang Ying
2010-11-10 8:28 ` Avi Kivity
2010-11-10 8:38 ` Huang Ying
2010-11-10 8:48 ` Avi Kivity
2010-11-10 16:42 ` Andi Kleen
2010-11-10 17:08 ` Avi Kivity
2010-11-10 17:44 ` Andi Kleen
2010-11-10 17:47 ` Avi Kivity
2010-11-10 19:16 ` Andi Kleen
2010-11-10 20:58 ` Avi Kivity [this message]
2010-11-10 8:21 ` Huang Ying
2010-11-10 8:34 ` Avi Kivity
2010-11-10 16:49 ` Anthony Liguori
2010-11-11 0:56 ` Huang Ying
2010-11-11 9:39 ` Avi Kivity
2010-11-12 1:16 ` Huang Ying
2010-11-14 11:08 ` Avi Kivity
2010-11-14 11:09 ` Avi Kivity
2010-11-15 1:46 ` Huang Ying
2010-11-15 10:02 ` Andi Kleen
2010-11-08 3:37 ` Anthony Liguori
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=4CDB077B.5000608@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=andi@firstfloor.org \
--cc=dnelson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.