From: Anthony PERARD <anthony.perard@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
Xen Devel <xen-devel@lists.xen.org>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [RFC] Improving CPU hotplug for 4.3 with qemu-xen
Date: Fri, 19 Jul 2013 16:26:08 +0100 [thread overview]
Message-ID: <51E95A90.9050908@citrix.com> (raw)
Hi,
The cpu hotplug that have been backported from QEMU to qemu-xen (1.5 to
1.3) is incomplete. Especially, there is no way to know if a CPU is
already marked as online by qemu. This result by those error messages
from libxl:
libxl: error: libxl_qmp.c:289:qmp_handle_error_response: received an
error message from QMP server: Unable to add CPU: 0, it already exists
libxl: error: libxl_qmp.c:289:qmp_handle_error_response: received an
error message from QMP server: Unable to add CPU: 1, it already exists
So I tried to backport more patches so it will become possible for libxl
to get the list of online cpu.
But this result in *a lot* of patches.
Here is the git tree and see the list of patches at the end of the mail:
git://xenbits.xen.org/people/aperard/qemu-dm.git backport-cpu-device
There is still some work to be done like making sure everything is
working properly and making some patches to use it with libxl.
So George, is it worth getting those patches into Xen 4.3 to get ride of
the error message ?
cpu: Change parent type to Device
qdev: Fold state enum into bool realized
qdev: Prepare "realized" property
cpu: Prepare QOM realizefn
target-i386: Update X86CPU to QOM realizefn
cpu: Introduce cpu_resume(), for single CPU
target-i386: Split out CPU creation and features parsing
cpu: Resume CPU from DeviceClass::realize() if hot-plugged
Revert "xen: Implement hot_add_cpu hook."
Revert "acpi_piix4: Add infrastructure to send CPU hot-plug GPE to guest"
cpu: Introduce CPU hot-plug notifier
cpu: Add helper cpu_exists(), to check if CPU with specified id exists
acpi_piix4: Add infrastructure to send CPU hot-plug GPE to guest
target-i386: Introduce feat2prop() for CPU properties
target-i386: Introduce apic-id CPU property
target-i386: Do not allow to set apic-id once CPU is realized
target-i386: Replace MSI_SPACE_SIZE with APIC_SPACE_SIZE
qapi/qmp-registry.c: Include headers it needs
qga/channel-posix.c: Include headers it needs
user: Move *-user/qemu-types.h to main directory
user: Rename qemu-types.h to qemu-user-types.h
Create qemu-types.h for struct typedefs
qlist.h: Do not include qemu-common.h
sysbus: make SysBusDeviceClass::init optional
target-i386: Introduce ICC bus/device/bridge
target-i386: Attach ICC bus to CPU on its creation
a fix for cpu_x86_create
fix machine initialization.
extract/unify the constant 0xfee00000 as APIC_DEFAULT_ADDRESS
kvmvapic: Make dependency on sysbus.h explicit
target-i386: Move APIC to ICC bus
pc: Implement QEMUMachine::hot_add_cpu hook
--
Anthony PERARD
next reply other threads:[~2013-07-19 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 15:26 Anthony PERARD [this message]
2013-07-21 14:18 ` [RFC] Improving CPU hotplug for 4.3 with qemu-xen Stefano Stabellini
2013-07-22 15:38 ` George Dunlap
2013-08-07 11:04 ` Ian Jackson
2013-08-07 18:40 ` Stefano Stabellini
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=51E95A90.9050908@citrix.com \
--to=anthony.perard@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.