From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for Feb 1
Date: Tue, 1 Feb 2011 07:54:14 -0800 [thread overview]
Message-ID: <20110201155414.GF28968@x200.localdomain> (raw)
KVM upstream merge: status, plans, coordination
- Jan has a git tree, consolidating
- qemu-kvm io threading is still an issue
- Anthony wants to just merge
- concerns with non-x86 arch and merge
- concerns with big-bang patch merge and following stability
- post 0.14 conversion to glib mainloop, non-upstreamed qemu-kvm will be
a problem if it's not there by then
- testing and nuances are still an issue (e.g. stefan berger's mmio read issue)
- qemu-kvm still evolving, needs to get sync'd or it will keep diverging
- 2 implementations of main init, cpu init, Jan has merged them into one
- qemu-kvm-x86.c file that's only a few hundred lines
- review as one patch to see the fundamental difference
QMP support status for 0.14
- declare QMP fully supported
- caveats: specific errors aren't guaranteed yet (primarily documentation)
- human monitor passthrough command is best effort
- device tree structure is not reliable, use name not path
- will send out patch to update qmp-commands.hx to document this (and Cc
libvirt)
- schema file (json subset which is python) and code generator to
generate code with C structures, also generates client library for
test cases (can test against new and old qmp server to verify hasn't
changed)
- HMP implemented in terms of QMP only
- at the end should have a test framework to test all commands
- glib/gtest framework
0.14 stable fork today
already posted 0.14 patches?
- will pick up all those patches before forking, fork at the end of the day
- will grab latest SeaBIOS and vgabios
SeaBIOS update for 0.14 (AHCI boot capable version)
- need to check if (and why) AHCI is disabled by default
- assuming no fundamental issues, could be enabled and become an
experimental new 0.14 feature
Summer of code 2011
- http://wiki.qemu.org/Google_Summer_of_Code_2011
- update wiki page with project ideas (let Anthony or Luiz know if you
want to be a mentor)
- application is due at end of the month
- mentors...be prepared that projects may take longer than just the
summer of code to complete
- join #qemu-gsoc on OFTC for gsoc discussions
Going to FOSDEM? agraf will be there...
next reply other threads:[~2011-02-01 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 15:54 Chris Wright [this message]
2011-02-01 16:36 ` [Qemu-devel] Re: KVM call minutes for Feb 1 Jan Kiszka
2011-02-01 16:53 ` Anthony Liguori
2011-02-01 17:03 ` Jan Kiszka
2011-02-01 17:20 ` Anthony Liguori
2011-02-01 17:34 ` Jan Kiszka
2011-02-01 20:28 ` Anthony Liguori
2011-02-03 10:11 ` Marcelo Tosatti
2011-02-03 13:48 ` Anthony Liguori
2011-02-01 17:53 ` Christoph Hellwig
2011-02-03 10:13 ` Marcelo Tosatti
2011-02-03 12:36 ` Paolo Bonzini
2011-02-03 14:54 ` 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=20110201155414.GF28968@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).