All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aarcange@redhat.com, jan.kiszka@siemens.com, aliguori@us.ibm.com,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Call MADV_HUGEPAGE for guest RAM allocations
Date: Tue, 16 Oct 2012 01:14:38 +0400	[thread overview]
Message-ID: <507C7CBE.5010103@msgid.tls.msk.ru> (raw)
In-Reply-To: <20121015155754.54f11e01@doriath.home>

On 15.10.2012 22:57, Luiz Capitulino wrote:
> On Fri, 5 Oct 2012 16:47:57 -0300
> Luiz Capitulino <lcapitulino@redhat.com> wrote:
> 
>> This makes it possible for QEMU to use transparent huge pages (THP)
>> when transparent_hugepage/enabled=madvise. Otherwise THP is only
>> used when it's enabled system wide.
>>
>> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> 
> ping?
> 
>> ---
>>  exec.c  | 1 +
>>  osdep.h | 5 +++++
>>  2 files changed, 6 insertions(+)
>>
>> diff --git a/exec.c b/exec.c
>> index 1114a09..7504909 100644
>> --- a/exec.c
>> +++ b/exec.c
>> @@ -2584,6 +2584,7 @@ ram_addr_t qemu_ram_alloc_from_ptr(ram_addr_t size, void *host,
>>      cpu_physical_memory_set_dirty_range(new_block->offset, size, 0xff);
>>  
>>      qemu_ram_setup_dump(new_block->host, size);
>> +    qemu_madvise(new_block->host, size, QEMU_MADV_HUGEPAGE);

FWIW, there was another attempt to do something like this:

https://lists.gnu.org/archive/html/qemu-devel/2012-08/msg02870.html

I'm not sure it is right or not, I just tried to guess, but that one
also went unanswered.  Maybe you will have better luck.

Thanks,

/mjt

  reply	other threads:[~2012-10-15 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 19:47 [Qemu-devel] [PATCH] Call MADV_HUGEPAGE for guest RAM allocations Luiz Capitulino
2012-10-15 18:57 ` Luiz Capitulino
2012-10-15 21:14   ` Michael Tokarev [this message]
2012-10-21  3:46   ` Aurelien Jarno
2012-10-22 13:50     ` Luiz Capitulino

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=507C7CBE.5010103@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=aarcange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lcapitulino@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 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.