From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:59481)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SFOi1-000130-DV
	for qemu-devel@nongnu.org; Wed, 04 Apr 2012 07:49:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SFOhv-0003w6-6t
	for qemu-devel@nongnu.org; Wed, 04 Apr 2012 07:49:04 -0400
Received: from mail-ob0-f173.google.com ([209.85.214.173]:62884)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <anthony@codemonkey.ws>) id 1SFOhv-0003vr-20
	for qemu-devel@nongnu.org; Wed, 04 Apr 2012 07:48:59 -0400
Received: by obbup19 with SMTP id up19so233462obb.4
	for <qemu-devel@nongnu.org>; Wed, 04 Apr 2012 04:48:56 -0700 (PDT)
Message-ID: <4F7C3525.7080301@codemonkey.ws>
Date: Wed, 04 Apr 2012 06:48:53 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
References: <m3hax0g9kt.fsf@blackfin.pond.sub.org>
	<4F7B610D.8000101@redhat.com>
In-Reply-To: <4F7B610D.8000101@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] KVM call minutes April 3
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: dlaor@redhat.com
Cc: Markus Armbruster <armbru@redhat.com>, KVM devel mailing list <kvm@vger.kernel.org>, qemu-devel@nongnu.org

On 04/03/2012 03:43 PM, 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

ASN.1 is an IDL format.  It's encoded in many ways including BER.  I think 
there's wide spread agreement that the next migration wire format should be 
encoded with BER which means it could be described via ASN.1 but I don't think 
we intend on using ASN.1 within the code base.

I don't think using ASN.1 to describe devices makes sense.  There really aren't 
very good Open Source ASN.1 compilers.  I also don't think the syntax is 
flexible enough to fully describe a device either.

Regards,

Anthony Liguori

>
>>
>> * qtest: test cases wanted
>>
>
>