qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH QEMU] transparent hugepage support
Date: Thu, 11 Mar 2010 17:52:16 +0200	[thread overview]
Message-ID: <4B9911B0.5000302@redhat.com> (raw)
In-Reply-To: <20100311151427.GE5677@random.random>

On 03/11/2010 05:14 PM, Andrea Arcangeli wrote:
> From: Andrea Arcangeli<aarcange@redhat.com>
>
> This will allow proper alignment so NPT/EPT can take advantage of linux host
> backing the guest memory with hugepages (only relevant for KVM and not for QEMU
> that has no NPT/EPT support). To complete it, it will also notify
> the kernel that this memory is important to be backed by hugepages with
> madvise (needed for both KVM and QEMU).
>
> Signed-off-by: Andrea Arcangeli<aarcange@redhat.com>
> ---
>
> diff --git a/exec.c b/exec.c
> index 891e0ee..aedd133 100644
> --- a/exec.c
> +++ b/exec.c
> @@ -2628,11 +2628,25 @@ ram_addr_t qemu_ram_alloc(ram_addr_t size)
>                                   PROT_EXEC|PROT_READ|PROT_WRITE,
>                                   MAP_SHARED | MAP_ANONYMOUS, -1, 0);
>   #else
> -        new_block->host = qemu_vmalloc(size);
> -#endif
> +#if defined(__linux__)&&  defined(TARGET_HPAGE_BITS)
> +	if (!kvm_enabled())
> +#endif
> +		new_block->host = qemu_vmalloc(size);
> +#if defined(__linux__)&&  defined(TARGET_HPAGE_BITS)
> +	else
> +		/*
> +		 * Align on HPAGE_SIZE so "(gfn ^ pfn)&
> +		 * (HPAGE_SIZE-1) == 0" to allow KVM to take advantage
> +		 * of hugepages with NPT/EPT.
> +		 */
> +		new_block->host = qemu_memalign(1<<  TARGET_HPAGE_BITS, size);
>    

That is a little wasteful.  How about a hint to mmap() requesting proper 
alignment (MAP_HPAGE_ALIGN)?

Failing that, modify qemu_memalign() to trim excess memory.

Come to think of it, posix_memalign() needs to do that (but doesn't).

> +#endif
>   #ifdef MADV_MERGEABLE
>           madvise(new_block->host, size, MADV_MERGEABLE);
>   #endif
> +#ifdef MADV_HUGEPAGE
> +        madvise(new_block->host, size, MADV_HUGEPAGE);
> +#endif
>       }


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

  reply	other threads:[~2010-03-11 15:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 15:14 [Qemu-devel] [PATCH QEMU] transparent hugepage support Andrea Arcangeli
2010-03-11 15:52 ` Avi Kivity [this message]
2010-03-11 16:05   ` Andrea Arcangeli
2010-03-13  8:28     ` Avi Kivity
2010-03-13 17:47       ` Andrea Arcangeli
2010-03-11 16:28   ` Paul Brook
2010-03-11 16:46     ` Andrea Arcangeli
2010-03-11 17:55       ` Paul Brook
2010-03-11 18:49         ` Andrea Arcangeli
2010-03-12 11:36           ` Paul Brook
2010-03-12 14:52             ` Andrea Arcangeli
2010-03-12 16:04               ` Paul Brook
2010-03-12 16:17                 ` Andrea Arcangeli
2010-03-12 16:24                   ` Paul Brook
2010-03-12 16:57                     ` Andrea Arcangeli
2010-03-12 17:10                       ` Paul Brook
2010-03-12 17:41                         ` Andrea Arcangeli
2010-03-12 18:17                           ` Paul Brook
2010-03-12 18:36                             ` Andrea Arcangeli
2010-03-12 18:41                               ` Paul Brook
2010-03-12 18:51                                 ` Andrea Arcangeli
2010-03-12 22:40                                   ` Jamie Lokier
2010-03-12 16:10               ` Paul Brook

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=4B9911B0.5000302@redhat.com \
    --to=avi@redhat.com \
    --cc=aarcange@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).