From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Dor Laor <dlaor@redhat.com>,
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: Wed, 04 Apr 2012 09:40:27 +0200 [thread overview]
Message-ID: <4F7BFAEB.7070000@redhat.com> (raw)
In-Reply-To: <20120404011843.GA2918@illuin>
Il 04/04/2012 03:18, Michael Roth ha scritto:
> 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.
We can also keep the current vmstate descriptions, but access fields
from the automatically-generated visitors instead of struct fields.
This keeps the IDL simple.
Paolo
next prev parent reply other threads:[~2012-04-04 7:41 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
2012-04-04 7:40 ` Paolo Bonzini [this message]
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=4F7BFAEB.7070000@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.com \
--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).