From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for August 31
Date: Tue, 31 Aug 2010 08:00:16 -0700 [thread overview]
Message-ID: <20100831150016.GA5784@x200.localdomain> (raw)
QMP/QPI
- declare what's in 0.13 supported
- means reasonable effort to avoid breaking something (deprecation is
possible)
- things that are left, shallow patch or human monitor conversion
- how to move forward?
- need to improve interfaces (no argument there)
- internal vs. external interfaces
- QMP == external, stable, extensible, discoverable, fwd/back compat
- internal == C, data structures, changeable, non-stable
- redefine internal interfaces and work up?
- this addresses concern that most changes are in monitor.c
- and addresses the concern that we aren't defining proper
extensible top level interfaces
- work top down from external?
- map to internal details...fix internals when external is
hard/impossible based on internals
- need to focus on QMP command addition in the face of internal details
- no disagreement there
- decouple monitor and QMP
- sane interfaces (proposal for migration from Anthony)
- error issues...
0.13 schedule
- rc1 tagged locally and under test, once testing completes, upload,
then one week to fix any outstanding issues
- will push tag later today and upload, announce once propagates (24hrs-ish)
qemu-kvm integration
- not getting a lot of cycles
- nothing major that anthony won't pull
- extboot still
- performance
- i/o threading model (merge both and fix in-tree)
- in-kernel apic
- device assignement (vfio against qemu tree)
- disable ia64
- avi will look at doing the pull request
reply other threads:[~2010-08-31 15:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100831150016.GA5784@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).