From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] KVM call minutes April 3 Date: Wed, 04 Apr 2012 09:40:27 +0200 Message-ID: <4F7BFAEB.7070000@redhat.com> References: <4F7B610D.8000101@redhat.com> <20120404011843.GA2918@illuin> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Dor Laor , Markus Armbruster , qemu-devel@nongnu.org, KVM devel mailing list To: Michael Roth Return-path: Received: from mail-pz0-f52.google.com ([209.85.210.52]:58407 "EHLO mail-pz0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752550Ab2DDHkr (ORCPT ); Wed, 4 Apr 2012 03:40:47 -0400 Received: by dake40 with SMTP id e40so611424dak.11 for ; Wed, 04 Apr 2012 00:40:46 -0700 (PDT) In-Reply-To: <20120404011843.GA2918@illuin> Sender: kvm-owner@vger.kernel.org List-ID: 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