From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v3] i386: keep cpu_model field in MachineState uptodate
Date: Mon, 7 Sep 2015 14:36:56 +0200 [thread overview]
Message-ID: <55ED84E8.5000907@redhat.com> (raw)
In-Reply-To: <55ED66A9.2030804@cn.fujitsu.com>
On 07/09/2015 12:27, Zhu Guihua wrote:
> This patch has been reviewed.
> Could anyone help merge it?
That would be Michael Tsirkin.
Paolo
> Thanks,
> Zhu
>
> On 08/28/2015 02:28 AM, Eduardo Habkost wrote:
>> On Thu, Aug 27, 2015 at 05:27:05PM +0800, Zhu Guihua wrote:
>>> Update cpu_model in MachineState for i386, so that the field can be used
>>> for cpu hotplug, instead of using a static variable.
>>>
>>> Signed-off-by: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
>> Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
>>
>
prev parent reply other threads:[~2015-09-07 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 9:27 [Qemu-devel] [PATCH v3] i386: keep cpu_model field in MachineState uptodate Zhu Guihua
2015-08-27 18:28 ` Eduardo Habkost
2015-09-07 10:27 ` Zhu Guihua
2015-09-07 12:36 ` Paolo Bonzini [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=55ED84E8.5000907@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=zhugh.fnst@cn.fujitsu.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).