From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Feb 15
Date: Tue, 15 Feb 2011 08:26:29 -0800 [thread overview]
Message-ID: <20110215162629.GN21720@x200.localdomain> (raw)
QAPI and QMP
- Anthony adding a new wiki page to describe all of this
- specified in formal schema using JSON
- includes documenation in javadoc-like syntax
- can generate api (possibly protocol) docs
- documenting each command and expected errors
- creates marshalling functions and C interfaces
- can generate C library
- facilitates unit tests/regression tests
- new and old code both exist in Anthony's tree
- allows unit tests to run on both to verify
- will remove old and force a flag day on merging in for 0.15
- still need to convert human monitor commands
- goal to convert all of human monitor to QMP
- events?
- still not consumable from internal use
- model signals and slots
- similar to notifier lists, but can pass arbitrary data
- client connects to signal via QMP
- how to extend?
- optional parameters (ABI bump)
- no way to know if client is aware of and consuming the optional
parameters
- add new events
- client required to register for new events when the know about
them, server can generate different logic based on clients
capability
- first release may not include shared library (lack of libconf/autotool)
- could
- QMP session in default well-known location
- allows iteration of all running QMP sessions
- per-user directory to handle user-level isolation
qdev future
- have an object model, but can't do polymorphism (i.e. bus level)
- could use more oop style, use GObject, use C++...no great ideas
- no major qdev plans for 0.15
- would be useful to have the ability to do device level unit testing
- cleaner device model, better encapsulation
- this is both the device side interfaces, but also interfaces back to qemu
- ability to do something like a virtual PCI bus to be a test harness
to interact with a device
- back to the GObject, oop, C++ questions?
- IDL based code generation to generate VMState in effort to make
migration more verifiable
- VMState
- need to focus on serialized guest visible state
- start with all state and remove obviously internal only state
- start with only guest visible state (structure separation)
- verfiable
- need a qdev tree maintainer?
- some disagreement on exactly how much
- qdev autodoc patches? (posted and ack'd multiple times)
bad patches committed that are not on list
- please inform of specifics incidents, this should not be happening
SeaBIOS update?
- w/out we will have features that can't be used
- need a release..
- 0.15 will need good planning and dates and communication with Kevin
0.14-rc2 tagged please review for any missing patches, 0.14.0 likely
tagged late today
revisit new -> old migration
- Amit offers virtio-serial patches and some legwork
- tabled discussion to list, possibly next week's call
next reply other threads:[~2011-02-15 16:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 16:26 Chris Wright [this message]
2011-02-15 23:13 ` [Qemu-devel] KVM call minutes for Feb 15 Anthony Liguori
2011-02-16 10:24 ` Avi Kivity
2011-02-16 13:34 ` Anthony Liguori
2011-02-17 9:26 ` Avi Kivity
2011-02-17 12:12 ` Anthony Liguori
2011-02-17 12:23 ` Avi Kivity
2011-02-17 13:10 ` Anthony Liguori
2011-02-17 13:25 ` Avi Kivity
2011-02-17 13:37 ` Anthony Liguori
2011-02-17 13:59 ` Peter Maydell
2011-02-17 14:01 ` Anthony Liguori
2011-02-17 14:06 ` Avi Kivity
2011-02-17 13:37 ` Anthony Liguori
2011-02-16 14:39 ` Amit Shah
2011-02-16 14:41 ` Anthony Liguori
2011-02-17 12:42 ` Amit Shah
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=20110215162629.GN21720@x200.localdomain \
--to=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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).