From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>,
libvir-list@redhat.com, Igor Mammedov <imammedo@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-ppc <qemu-ppc@nongnu.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
David Gibson <david@gibson.dropbear.id.au>,
Peter Maydell <peter.maydell@linaro.org>,
Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: vCPU hotplug roadmap
Date: Wed, 30 Jan 2013 14:02:16 +0100 [thread overview]
Message-ID: <510919D8.9070203@suse.de> (raw)
In-Reply-To: <20130130124910.GE5772@otherpad.lan.raisama.net>
Am 30.01.2013 13:49, schrieb Eduardo Habkost:
> On Wed, Jan 30, 2013 at 11:58:56AM +0100, Andreas Färber wrote:
>> * CPU class_init for -cpu host requires KVM init (imammedo)
>> [suggestion by ehabkost to use kvm_arch_vcpu_init, WIP by afaerber]
>
> I don't know what you mean by "use kvm_arch_vcpu_init()".
Sorry, scratch the _vcpu. I.e., the x86-specific KVM init hook.
> I sent a RFC
> following somebody's suggestion of simply make kvm_arch_init() call a
> function to finish the -cpu host initialization, as we can't initialize
> everything inside class_init.
>
> See x86_cpu_finish_host_class_init() at:
> Message-Id: <1357329382-20944-7-git-send-email-ehabkost@redhat.com>
> http://article.gmane.org/gmane.comp.emulators.qemu/186778
...and I have been working on making it even simpler for the
still-x86_def_t-based approach. I'm still busy looking at 1.4 issues
currently though.
Andreas
--
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:[~2013-01-30 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 16:16 Minutes for KVM call 2013-01-15 Juan Quintela
2013-01-30 10:58 ` vCPU hotplug roadmap (was: Minutes for KVM call 2013-01-15) Andreas Färber
2013-01-30 12:49 ` Eduardo Habkost
2013-01-30 13:02 ` Andreas Färber [this message]
2013-01-30 13:18 ` vCPU hotplug roadmap 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=510919D8.9070203@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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