From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] KVM call agenda for 2012-11-12
Date: Tue, 13 Nov 2012 15:29:37 +0100 [thread overview]
Message-ID: <50A25951.7090602@suse.de> (raw)
In-Reply-To: <20121113122955.GI8231@otherpad.lan.raisama.net>
Am 13.11.2012 13:29, schrieb Eduardo Habkost:
> On Mon, Nov 12, 2012 at 01:58:38PM +0100, Juan Quintela wrote:
>>
>> Please send in any agenda topics you are interested in.
>
> - Clarify 1.3 plans for CPU:
>From my submaintainer POV:
> DeviceState CPU,
I was specifically tasked with the qdev split by Anthony, so unless
major obstacles arise I will send a PULL until Thursday.
What I am still unsure about is whether it makes sense to actually apply
the final CPU-as-device change for v1.3 since that exposes the device
name(s) as public "ABI", cf. below. A safety option would be no_user = 1
to avoid users messing with untested use cases at this time.
> x86 CPU classes,
If I get through review quickly enough and RFC seems sane and I get a
PATCH, I might include it in the pull. To me, classes are prerequisites
to exposing CPU-as-a-device because otherwise the user specifies the
base class that we want to make abstract (which will then break
backwards compatibility) and has no API to set it to something useful.
Once applied, we would still have half a month for testing.
> x86 CPU properties
Won't make v1.3 due to timing constraints. There are also still
unresolved review comments related to property naming IIRC.
> (we still want to get any of this included, or all will have to wait for 1.4?)
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
next prev parent reply other threads:[~2012-11-13 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 12:58 [Qemu-devel] KVM call agenda for 2012-11-12 Juan Quintela
2012-11-12 22:31 ` Marcelo Tosatti
2012-11-13 14:20 ` Anthony Liguori
2012-11-13 14:48 ` Juan Quintela
2012-11-13 15:05 ` Eduardo Habkost
2012-11-13 12:29 ` Eduardo Habkost
2012-11-13 14:29 ` Andreas Färber [this message]
2012-11-13 15:17 ` Eduardo Habkost
2012-11-13 12:43 ` Zhi Yong Wu
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=50A25951.7090602@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jdenemar@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).