From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu_vmalloc: align properly for transparent hugepages and KVM
Date: Mon, 05 Sep 2011 13:21:21 +0300 [thread overview]
Message-ID: <4E64A2A1.9060801@redhat.com> (raw)
In-Reply-To: <4E64A02B.9030502@siemens.com>
On 09/05/2011 01:10 PM, Jan Kiszka wrote:
> On 2011-09-05 10:07, Avi Kivity wrote:
> > To make good use of transparent hugepages, KVM requires that guest-physical
> > and host-virtual addresses share the low 21 bits (as opposed to just the low
> > 12 bits normally required).
> >
> > Adjust qemu_vmalloc() to honor that requirement. Ignore it for small regions
> > to avoid fragmentation.
> >
> > Signed-off-by: Avi Kivity<avi@redhat.com>
> > ---
> > oslib-posix.c | 14 +++++++++++++-
> > 1 files changed, 13 insertions(+), 1 deletions(-)
> >
> > diff --git a/oslib-posix.c b/oslib-posix.c
> > index 196099c..a304fb0 100644
> > --- a/oslib-posix.c
> > +++ b/oslib-posix.c
> > @@ -35,6 +35,13 @@
> > extern int daemon(int, int);
> > #endif
> >
> > +#if defined(__linux__)&& defined(__x86_64__)
> > + /* Use 2MB alignment so transparent hugepages can be used by KVM */
>
> Aren't transparent hugepages also available in TCG mode? Then just
> remove "by KVM" from subject and comment.
They are, but they don't require the special alignment.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-05 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 8:07 [Qemu-devel] [PATCH] qemu_vmalloc: align properly for transparent hugepages and KVM Avi Kivity
2011-09-05 10:10 ` Jan Kiszka
2011-09-05 10:21 ` Avi Kivity [this message]
2011-09-09 18:34 ` 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=4E64A2A1.9060801@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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.