From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Dor Laor <dlaor@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
KVM devel mailing list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call minutes April 3
Date: Tue, 3 Apr 2012 20:18:43 -0500 [thread overview]
Message-ID: <20120404011843.GA2918@illuin> (raw)
In-Reply-To: <4F7B610D.8000101@redhat.com>
On Tue, Apr 03, 2012 at 11:43:57PM +0300, Dor Laor wrote:
> On 04/03/2012 05:43 PM, Markus Armbruster wrote:
> >I'm afraid my notes are rather rough...
> >
> >* 1.1
> > soft freeze apr 15th (less than two weeks)
> > hard freeze may 1
> > three months cycle for 1.2
> > stable machine types only every few releases? "pc-next"
> >
> >* Maintainers, got distracted and my notes make no sense, sorry
> >
> >* MSI injection to KVM irqchips from userspace devices models
> >
> >* qemu-kvm tree: working towards upstream merge
> >
> > not much left, mostly device assignment
> >
> >* Migration: vmstate and visitors, decoupling the wire format
> > why not ASN.1
>
> Curiosity kills me of waiting for next week's meeting to get the answer
I believe when this had come up in the past the plan was to use ASN.1
for the wire protocol, but not to address the decoupling problem.
Theoretically it could handle both, but I believe that requires defining
device structures using ASN.1 definitions, which probably isn't suitable
for devices since it results in high level structures which require
special accessors (at least for the libraries I've looked at)
An IDL compiler that generates visitors based on a simple device code
annotations still seems to be the leading option.
Previously I'd jumped the gun a bit by piggy-backing off vmstate to get at
the protocol side, but that permanently baked QEMUFile markers into the
wire protocol which was the wrong approach.
Attacking the IDL/schema side first is the more rationale approach. From
there we can potentially generate ASN.1 BER/DER visitors for the protocol
side, or potentially even just vmstate bindings as a start. I've recently
started looking into the latter... it's completely feasible, the only
downside is it complicates the IDL due requiring support for a lot of
what are very much vmstate-specific items, but it should be possible to
do this in a manner where those annotations are self-contained and
ignorable if we opted to replace vmstate-style declarations.
>
> >
> >* qtest: test cases wanted
> >
>
>
next prev parent reply other threads:[~2012-04-04 1:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 14:43 [Qemu-devel] KVM call minutes April 3 Markus Armbruster
2012-04-03 20:43 ` Dor Laor
2012-04-04 1:18 ` Michael Roth [this message]
2012-04-04 7:40 ` Paolo Bonzini
2012-04-04 10:37 ` Michael Roth
2012-04-04 10:53 ` Dor Laor
2012-04-04 11:52 ` Anthony Liguori
2012-04-04 12:01 ` Dor Laor
2012-04-04 12:14 ` Michael Roth
2012-04-04 13:21 ` Igor Mammedov
2012-04-04 14:39 ` Michael Roth
2012-04-05 16:16 ` Avi Kivity
2012-04-04 11:48 ` 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=20120404011843.GA2918@illuin \
--to=mdroth@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=dlaor@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).