From: Chen Fan <chen.fan.fnst@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [Qemu-devel] [RFC 0/3] cpu: add device_add foo-x86_64-cpu support
Date: Tue, 13 May 2014 18:08:46 +0800 [thread overview]
Message-ID: <cover.1399974281.git.chen.fan.fnst@cn.fujitsu.com> (raw)
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(-)
--
1.8.1.4
next reply other threads:[~2014-05-13 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 10:08 Chen Fan [this message]
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
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=cover.1399974281.git.chen.fan.fnst@cn.fujitsu.com \
--to=chen.fan.fnst@cn.fujitsu.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@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).