qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "\"“tiejun.chen”\"" <tiejun.chen@windriver.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] cpus: use cpu_is_stopped efficiently
Date: Fri, 2 Aug 2013 09:45:05 +0800	[thread overview]
Message-ID: <51FB0F21.9090009@windriver.com> (raw)
In-Reply-To: <51FA48AC.9070905@suse.de>

On 08/01/2013 07:38 PM, � wrote:
> Hi,
>
> Am 26.07.2013 10:47, schrieb Tiejun Chen:
>> It makes more sense and simple later.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
>> ---
>>   cpus.c |   14 +++++++-------
>>   1 file changed, 7 insertions(+), 7 deletions(-)
>>
>> diff --git a/cpus.c b/cpus.c
>> index c232265..a997632 100644
>> --- a/cpus.c
>> +++ b/cpus.c
>> @@ -62,6 +62,11 @@
>>
>>   static CPUArchState *next_cpu;
>>
>> +bool cpu_is_stopped(CPUState *cpu)
>> +{
>> +    return !runstate_is_running() || cpu->stopped;
>> +}
>> +
>>   static bool cpu_thread_is_idle(CPUArchState *env)
>>   {
>>       CPUState *cpu = ENV_GET_CPU(env);
>
> To optimize performance slightly, I would suggest to reorder the two
> conditions as they were below (avoiding the non-inline function call if
> cpu->stopped).

Good idea.

>
> Other than that it looks good to me, but no bugfix for 1.6.
> If you send a v2 I can queue it on qom-cpu for the next merge window in
> two weeks.

I already send this v2 just now.

>
> CC'ing me would have made me review it earlier. ;) And as you may have
> noticed, Avi is no longer with Red Hat, and Gleb and Paolo are
> maintaining KVM parts, which there are none in this patch. See
> MAINTAINERS file for the latest list.

Thanks for your information :)

Tiejun

>
> Regards,
> Andreas
>
>> @@ -69,7 +74,7 @@ static bool cpu_thread_is_idle(CPUArchState *env)
>>       if (cpu->stop || cpu->queued_work_first) {
>>           return false;
>>       }
>> -    if (cpu->stopped || !runstate_is_running()) {
>> +    if (cpu_is_stopped(cpu)) {
>>           return true;
>>       }
>>       if (!cpu->halted || qemu_cpu_has_work(cpu) ||
>> @@ -432,11 +437,6 @@ void cpu_synchronize_all_post_init(void)
>>       }
>>   }
>>
>> -bool cpu_is_stopped(CPUState *cpu)
>> -{
>> -    return !runstate_is_running() || cpu->stopped;
>> -}
>> -
>>   static void do_vm_stop(RunState state)
>>   {
>>       if (runstate_is_running()) {
>> @@ -455,7 +455,7 @@ static bool cpu_can_run(CPUState *cpu)
>>       if (cpu->stop) {
>>           return false;
>>       }
>> -    if (cpu->stopped || !runstate_is_running()) {
>> +    if (cpu_is_stopped(cpu)) {
>>           return false;
>>       }
>>       return true;
>>
>
>

      reply	other threads:[~2013-08-02  1:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  8:47 [Qemu-devel] [PATCH] cpus: use cpu_is_stopped efficiently Tiejun Chen
2013-08-01  8:12 ` "“tiejun.chen”"
2013-08-01 16:26   ` Marcelo Tosatti
2013-08-01 11:38 ` Andreas Färber
2013-08-02  1:45   ` "“tiejun.chen”" [this message]

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=51FB0F21.9090009@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=afaerber@suse.de \
    --cc=mtosatti@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).