From: Chris Wright <chrisw@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] KVM call minutes for July 20
Date: Tue, 20 Jul 2010 07:45:51 -0700 [thread overview]
Message-ID: <20100720144551.GB32665@x200.localdomain> (raw)
0.12.stable
- start w/ git tree + pull requests
- release process is separate from commit access
- justin will put up a tree for pull requests
- there's current backlog, what about that?
- anthony's concern with -stable is the testing (upstream tree gets more
testing than -stable)
- 0.12.5?
- planning to do next w/ 0.13 release
- aurelien may cut a release
- justin will do some sanity testing, most patches are in fedora anyway
0.13
- rc RSN (hopefully this week, top priority for anthony)
kvm testsuite
- was planning to clean up and contribute to qemu
- now thinking perhaps just split it out to its own repo
- not really qemu code, not really kvm code, not cross compile, etc..
- could use std serial device
- could use vga (needs mmio space)
-
- would like to add nested svm and (more important) nested vmx
- small bit to copy l1 to l2 state, to make guest nested
- need framework, can then require nested patches come w/ regression tests
- current testsuite failing on qemu (shows softmmu issues, any takers?)
fw_cfg issues
- mostly on list
- concerns about dma interface (too close to use case specific hack)
- rep could be optimized in general
- each byte == function call
- possible pull in 4k (instead of 1k) on each exit
- bar for changes should be no new interfaces
next reply other threads:[~2010-07-20 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 14:45 Chris Wright [this message]
2010-07-20 16:29 ` [Qemu-devel] KVM call minutes for July 20 Aurelien Jarno
2010-07-20 17:55 ` Anthony Liguori
2010-07-20 16:40 ` [Qemu-devel] " David S. Ahern
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=20100720144551.GB32665@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).