From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Mar 8
Date: Tue, 8 Mar 2011 07:50:24 -0800 [thread overview]
Message-ID: <20110308155024.GA10392@x200.localdomain> (raw)
QAPI merge plans
- should be 100% back compat
- qmp moved over
- hmp moved over
- 1st pass, core infrastructure (includes test framework)
- 2nd pass, command conversion
- 3rd pass, more controversial bits
- adds dependencies: glib and python
- some testing based on kvm-unit-test micro-os instance (e.g. added a balloon
and run commands against it to test)
- add more functionality here? (kvm autotest is slow, above is quick)
- will hit some point where full functionality is needed
- have a mini linux to do this (lags where driver updates are part of test)
- generated code can obfuscate the debugging process
- code generator has some ugly corners (python writing C...)
- but generated code should be debuggable, readable, etc.
- some grumbling regarding glib dependency
- reducing NIH and relying on external functionality is solid way to
grow qemu as a project
Read wiki here and review closely:
http://wiki.qemu.org/Features/QAPI
virt-agent
- json string converted to command (and vice versa)
- add to qmp schema - allows generated marshalling code to sanity check in/out
- problem with qmp not being bi-directional (rpc - in, events - out)
- posted events allow migration to save and send unposted events
- any issues with guest agent interface extensibility
- will add command to return schema
- can add (optional) parameters to commands
- make libqmp a shared object for 0.16 (too much going on for 0.15)
- can terminate in qemu (e.g. vnc server internally qmp client to interact
with guest cut 'n paste) or externally proxying to/from endpoint
- possibly revisit dynamic schema in future
glib, main loop, events
- (context was setfd changes from amit)
- iothread work is more critical to do first and get merged
- glib work starting just in qapi
iothread merge?
- progressing slowly, marcelo working on it
- have found regressions (signal handling code) (ifdef'd away for now)
next reply other threads:[~2011-03-08 15:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 15:50 Chris Wright [this message]
2011-03-08 16:00 ` [Qemu-devel] KVM call minutes for Mar 8 Anthony Liguori
2011-03-08 16:09 ` Stefan Hajnoczi
2011-03-08 16:51 ` [Qemu-devel] " Jan Kiszka
2011-03-08 16:58 ` Paolo Bonzini
2011-03-08 17:10 ` Jan Kiszka
2011-03-08 17:15 ` Paolo Bonzini
2011-03-08 17:21 ` Jan Kiszka
2011-03-08 17:40 ` Avi Kivity
2011-03-08 17:41 ` Avi Kivity
2011-03-08 17:42 ` Jan Kiszka
2011-03-08 17:43 ` Jan Kiszka
2011-03-08 17:45 ` Avi Kivity
2011-03-15 3:38 ` Marcelo Tosatti
2011-03-15 7:13 ` Jan Kiszka
2011-03-09 9:25 ` [Qemu-devel] " Kevin Wolf
2011-03-09 13:13 ` Anthony Liguori
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=20110308155024.GA10392@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).