From: Jan Kiszka <jan.kiszka@web.de>
To: quintela@redhat.com
Cc: qemu-devel@nongnu.org, KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call agenda for April, Tuesday 3
Date: Mon, 02 Apr 2012 22:25:38 +0200 [thread overview]
Message-ID: <4F7A0B42.9060806@web.de> (raw)
In-Reply-To: <87398m74mf.fsf@elfo.elfo>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On 2012-04-02 13:30, Juan Quintela wrote:
>
> Hi
>
> Please send in any agenda items you are interested in covering.
- MSI injection to KVM irqchips from userspace devices models:
new direct MSI injection API for KVM and the right model for QEMU
to deal with the old API
- state of and plans for qemu-kvm tree
(I'd like to proceed with cleanups)
But maybe both topics are just stuck due to limited bandwidth on the
maintainer side. Some clarification would be good, though, as these
things are blocking me ATM.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2012-04-02 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 11:30 [Qemu-devel] KVM call agenda for April, Tuesday 3 Juan Quintela
2012-04-02 20:25 ` Jan Kiszka [this message]
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=4F7A0B42.9060806@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).