From: "Andreas Färber" <afaerber@suse.de>
To: quintela@redhat.com
Cc: Chris Wright <chrisw@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 3
Date: Mon, 02 Jan 2012 14:46:42 +0100 [thread overview]
Message-ID: <4F01B542.8000800@suse.de> (raw)
In-Reply-To: <87ehvis3uj.fsf@trasno.mitica>
Am 02.01.2012 13:09, schrieb Juan Quintela:
> First of all, Happy New Year to everybody (even for the people whose
> calendar is different O:-)
+1
> Please send in any agenda items you are interested in covering.
QOM: If Anthony is available, I'd be interested in hearing an update on
the roadmap. In particular,
* when can we expect to be able to model SoCs rather than CPUs? Will
this affect command line usage - are we going to have '-device
ti-tms570' rather than '-cpu cortex-r4' then, or -cpu overriding the
container's default?
* are the announced remaining 3 series going to touch CPUState? a) Are
CPU features being refactored (standardized) for QOM or should we copy
current x86 code for controlling ARM FPU? b) Any plans for adding
inheritence, e.g., for CPU_COMMON and CPU reset?
* what's the effect on VMState? Will VMState continue to coexist with
QOM, or does QOM replace VMState at some point? Is it worth introducing
new size mechanisms now or should we postpone SD/AHCI migration until
QOM is merged?
Testing: A brief clarification on scope, goals and relations (overlap?)
of all frameworks proposed might be better than a flame war? ;)
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-01-02 13:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 12:09 [Qemu-devel] KVM call agenda for Tuesday 3 Juan Quintela
2012-01-02 13:46 ` Andreas Färber [this message]
2012-01-02 14:11 ` Paolo Bonzini
2012-01-03 1:12 ` Anthony Liguori
2012-01-03 8:54 ` Paolo Bonzini
2012-01-02 15:54 ` Peter Maydell
2012-01-03 1:14 ` Anthony Liguori
2012-01-03 10:26 ` Peter Maydell
2012-01-03 12:07 ` Alex Bradbury
2012-01-03 13:37 ` Anthony Liguori
2012-01-03 13:57 ` Peter Maydell
2012-01-03 14:02 ` Anthony Liguori
2012-01-03 14:13 ` Peter Maydell
2012-01-03 1:04 ` Anthony Liguori
2012-01-03 13:52 ` Andreas Färber
2012-01-03 13:59 ` Anthony Liguori
2012-01-03 8:33 ` Stefan Hajnoczi
2012-01-03 12:15 ` Dor Laor
2012-01-03 13:12 ` Stefan Hajnoczi
2012-01-03 14:10 ` Andreas Färber
2012-01-03 14:30 ` Vadim Rozenfeld
2012-01-04 2:47 ` Cao,Bing Bu
2012-01-04 11:25 ` Stefan Hajnoczi
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=4F01B542.8000800@suse.de \
--to=afaerber@suse.de \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peter.maydell@linaro.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).