From: "Andreas Färber" <afaerber@suse.de>
To: "chen.fan.fnst@cn.fujitsu.com" <chen.fan.fnst@cn.fujitsu.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Marcel Apfelbaum <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] [RFC 0/3] cpu: add device_add foo-x86_64-cpu support
Date: Thu, 22 May 2014 12:49:26 +0200 [thread overview]
Message-ID: <537DD636.90500@suse.de> (raw)
In-Reply-To: <05953EE18EEC9148BE892F38DF8F8E8E5ED412@G08CNEXMBPEKD03.g08.fujitsu.local>
Hi,
Am 22.05.2014 04:33, schrieb chen.fan.fnst@cn.fujitsu.com:
> I think if we want to use 'device/device_add' to implement CPU,
> we must do some check before qemu_init_vcpu(). how can we to do that?
We ran into such problems before... If need be, we can change from the
old parent_realize scheme to the base class calling the derived realize
function in-order, or we can add new hooks to CPUClass as necessary.
Consider me a bit skeptical about MAX_CPUMASK_BITS in 1/3. This should
at least be tied to the maximum allowed for QEMUMachine/MachineClass
rather than hardcoded to 255, which people may forget to synchronize.
There was a recent attempt to increase the limits.
2/3 looks good apart from the subject; I could cherry-pick that, seeing
there is Reviewed-by, if you like.
3/3 is doing a bit much to digest at once for my taste.
Regards,
Andreas
> On Tue, 2014-05-13 at 18:08 +0800, Chen Fan wrote:
>> this patches tried to make cpu hotplug with device_add,
>> and made -device foo-x86_64-cpu available,also we can
>> set apic-id property with command line, if without setting
>> apic-id property, we added first unoccupied apic id as the
>> default new apic id. and hotplug cpu with device_add, we
>> must make check of APIC ID after cpu object initialization
>> that was different from 'cpu_add' command which check 'ids'
>> at the beginning.
>>
>> Chen Fan (3):
>> using CPUMASK bitmaps to calculate cpu index
>> cpu: introduce CpuTopoInfo structure for argument simplification
>> cpu: add device_add foo-x86_64-cpu support
>>
>> exec.c | 9 +++--
>> include/qom/cpu.h | 11 ++++++
>> include/sysemu/sysemu.h | 7 ----
>> qdev-monitor.c | 11 ++++++
>> target-i386/cpu.c | 91 ++++++++++++++++++++++++++++++++++++++++++++++++-
>> target-i386/topology.h | 51 ++++++++++++++++++---------
>> 6 files changed, 151 insertions(+), 29 deletions(-)
--
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:[~2014-05-22 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 10:08 [Qemu-devel] [RFC 0/3] cpu: add device_add foo-x86_64-cpu support Chen Fan
2014-05-13 10:08 ` [Qemu-devel] [RFC 1/3] using CPUMASK bitmaps to calculate cpu index Chen Fan
2014-05-22 13:26 ` Igor Mammedov
2014-05-13 10:08 ` [Qemu-devel] [RFC 2/3] cpu: introduce CpuTopoInfo structure for argument simplification Chen Fan
2014-05-13 10:08 ` [Qemu-devel] [RFC 3/3] cpu: add device_add foo-x86_64-cpu support Chen Fan
2014-05-22 13:55 ` Igor Mammedov
2014-05-22 2:33 ` [Qemu-devel] [RFC 0/3] " chen.fan.fnst
2014-05-22 10:49 ` Andreas Färber [this message]
2014-05-22 14:52 ` Eduardo Habkost
2014-05-22 13:33 ` Igor Mammedov
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=537DD636.90500@suse.de \
--to=afaerber@suse.de \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel.a@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).