qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>, qemu-devel@nongnu.org
Cc: imammedo@redhat.com, mst@redhat.com, luonengjun@huawei.com,
	peter.huangpeng@huawei.com, hutao@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v2] vl: Adjust the place of calling mlockall to speedup VM's startup
Date: Fri, 26 Sep 2014 17:35:29 +0200	[thread overview]
Message-ID: <542587C1.2070809@redhat.com> (raw)
In-Reply-To: <5425253C.3070700@huawei.com>

Il 26/09/2014 10:35, zhanghailiang ha scritto:
> Hi,
> 
> This has been reviewed, Will anyone pick this up?;)

I think mst will.  It's Jewish new year this week, so it will have to
wait for next week.

Paolo

> Thanks,
> zhanghailiang
> On 2014/9/23 18:42, zhanghailiang wrote:
>> If we configure mlock=on and memory policy=bind at the same time,
>> It will consume lots of time for system to treat with memory,
>> especially when call mbind behind mlockall.
>>
>> Adjust the place of calling mlockall, calling mbind before mlockall
>> can remarkably reduce the time of VM's startup.
>>
>> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> ---
>>   v2:
>> - Add Acked-by
>> - change 'int' to 'bool' (Thanks Hu Tao)
>> ---
>>   vl.c | 11 +++++------
>>   1 file changed, 5 insertions(+), 6 deletions(-)
>>
>> diff --git a/vl.c b/vl.c
>> index dc792fe..35e5de6 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -134,6 +134,7 @@ const char* keyboard_layout = NULL;
>>   ram_addr_t ram_size;
>>   const char *mem_path = NULL;
>>   int mem_prealloc = 0; /* force preallocation of physical target
>> memory */
>> +bool enable_mlock = false;
>>   int nb_nics;
>>   NICInfo nd_table[MAX_NICS];
>>   int autostart;
>> @@ -1421,12 +1422,8 @@ static void smp_parse(QemuOpts *opts)
>>
>>   }
>>
>> -static void configure_realtime(QemuOpts *opts)
>> +static void realtime_init(void)
>>   {
>> -    bool enable_mlock;
>> -
>> -    enable_mlock = qemu_opt_get_bool(opts, "mlock", true);
>> -
>>       if (enable_mlock) {
>>           if (os_mlock() < 0) {
>>               fprintf(stderr, "qemu: locking memory failed\n");
>> @@ -3973,7 +3970,7 @@ int main(int argc, char **argv, char **envp)
>>                   if (!opts) {
>>                       exit(1);
>>                   }
>> -                configure_realtime(opts);
>> +                enable_mlock = qemu_opt_get_bool(opts, "mlock", true);
>>                   break;
>>               case QEMU_OPTION_msg:
>>                   opts = qemu_opts_parse(qemu_find_opts("msg"),
>> optarg, 0);
>> @@ -4441,6 +4438,8 @@ int main(int argc, char **argv, char **envp)
>>
>>       machine_class->init(current_machine);
>>
>> +    realtime_init();
>> +
>>       audio_init();
>>
>>       cpu_synchronize_all_post_init();
>>
> 
> 
> 
> 

  reply	other threads:[~2014-09-26 15:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 10:42 [Qemu-devel] [PATCH v2] vl: Adjust the place of calling mlockall to speedup VM's startup zhanghailiang
2014-09-26  8:35 ` zhanghailiang
2014-09-26 15:35   ` Paolo Bonzini [this message]
2014-09-28  6:05     ` zhanghailiang

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=542587C1.2070809@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=imammedo@redhat.com \
    --cc=luonengjun@huawei.com \
    --cc=mst@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhang.zhanghailiang@huawei.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;
as well as URLs for NNTP newsgroup(s).