From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
Alexander Graf <agraf@suse.de>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] KVM call for 2013-01-15
Date: Tue, 15 Jan 2013 15:59:18 +0100 [thread overview]
Message-ID: <50F56EC6.7010005@suse.de> (raw)
In-Reply-To: <20130115103627.GF20133@otherpad.lan.raisama.net>
Am 15.01.2013 11:36, schrieb Eduardo Habkost:
> On Mon, Jan 14, 2013 at 02:26:12PM +0100, Juan Quintela wrote:
>> Please send in any agenda topics that you have.
>
> - CPU hotplug plan/design
For those that didn't read it, some food for thought:
http://lists.gnu.org/archive/html/qemu-devel/2013-01/msg01219.html
The basic assumptions that I have been operating under so far:
1) CPU hotplug will be x86-specific
2) The CPU is sufficiently different from a device to not use device_add
3) x86 CPU hotplug will not allow mixing different CPU types (Alex)
Previous art seems to be HMP cpu_set. Using any such specific operation
would allow us to abstract the ongoing QOM rework - I am about 2-3
series ahead of what has been posted but not there at QOM'ish hotplug
yet, so am open to any suggestions on the call.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-01-15 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 13:26 [Qemu-devel] KVM call for 2013-01-15 Juan Quintela
2013-01-15 10:36 ` Eduardo Habkost
2013-01-15 14:59 ` Andreas Färber [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=50F56EC6.7010005@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).