From: "Andreas Färber" <afaerber@suse.de>
To: Tiejun Chen <tiejun.chen@windriver.com>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [v2][PATCH 1/1] cpus: use cpu_is_stopped efficiently
Date: Fri, 02 Aug 2013 15:33:48 +0200 [thread overview]
Message-ID: <51FBB53C.8040708@suse.de> (raw)
In-Reply-To: <1375407789-5885-1-git-send-email-tiejun.chen@windriver.com>
Am 02.08.2013 03:43, schrieb Tiejun Chen:
> It makes more sense and simple later.
>
> Signed-off-by: Tiejun Chen <tiejun.chen@windriver.com>
> ---
> v1 -> v2:
>
> To optimize performance slightly, we can reorder the two conditions to
> avoid the non-inline function call if cpu->stopped.
Patch doesn't apply to qemu.git: next_cpu and cpu_thread_is_idle() use
CPUState since a few weeks and do_vm_stop() changed from void to int.
Please remember to rebase before sending patches.
Thanks, applied to qom-cpu-next (with modified commit message):
https://github.com/afaerber/qemu-cpu/commits/qom-cpu-next
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-08-02 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 1:43 [Qemu-devel] [v2][PATCH 1/1] cpus: use cpu_is_stopped efficiently Tiejun Chen
2013-08-02 13:33 ` Andreas Färber [this message]
2013-08-05 1:47 ` "“tiejun.chen”"
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=51FBB53C.8040708@suse.de \
--to=afaerber@suse.de \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tiejun.chen@windriver.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).