From: pingfank@linux.vnet.com
To: linux-acpi@vger.kernel.org, qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, Liu Ping Fan <pingfank@linux.vnet.ibm.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
ryanh@us.ibm.com, shaohua.li@intel.com, lenb@kernel.org
Subject: [Qemu-devel] Enable x86 linux guest with cpu hotplug feature.
Date: Tue, 4 Oct 2011 19:13:35 +0800 [thread overview]
Message-ID: <1317726818-8514-1-git-send-email-pingfank@linux.vnet.com> (raw)
From: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
A bunch of patches, which are applied separately for kernel and qemu-kvm,
and make x86 based linux guest with cpu hotplug feature.
For kernel:
0001-ACPI-Call-ACPI-remove-handler-when-handling-ACPI-eje.patch
--call acpi eject event handler in acpi_bus_notify()
For qemu-kvm:
0001-ACPI-Update-cpu-hotplug-event-for-guest.patch
--trigger acpi cpu hotplug event for guest, so qemu-kvm can bring present cpu
to online state
0002-LAPIC-make-lapic-support-cpu-hotplug.patch
--make qemu-kvm support to bring possible cpu to present state.
After applying these patches, we can bring possible cpu online
by the following step.
1.Boot up qemu-kvm with the param "-smp 1,maxcpu=4",
2.Use "cpu_set 2 online" cmd in qemu monitor to bring possible cpu
to present state.
3.In guest,echo 1 > cpu2/online to bring the present cpu to online
state.
next reply other threads:[~2011-10-04 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 11:13 pingfank [this message]
2011-10-04 11:13 ` [Qemu-devel] [PATCH] ACPI: Call ACPI remove handler when handling ACPI eject event pingfank
2011-10-04 11:13 ` [Qemu-devel] [PATCH 1/2] ACPI: Update cpu hotplug event for guest pingfank
2011-10-04 11:13 ` [Qemu-devel] [PATCH 2/2] LAPIC: make lapic support cpu hotplug pingfank
2011-10-04 12:58 ` Anthony Liguori
2011-10-05 10:09 ` liu ping fan
2011-10-04 16:43 ` Jan Kiszka
2011-10-05 10:26 ` liu ping fan
2011-10-05 11:01 ` Jan Kiszka
2011-10-06 1:13 ` liu ping fan
2011-10-06 1:50 ` Anthony Liguori
2011-10-06 6:58 ` Jan Kiszka
2011-10-07 12:54 ` liu ping fan
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=1317726818-8514-1-git-send-email-pingfank@linux.vnet.com \
--to=pingfank@linux.vnet.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.ibm.com \
--cc=shaohua.li@intel.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).