From: Anthony Liguori <anthony@codemonkey.ws>
To: dlaor@redhat.com
Cc: Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call minutes April 3
Date: Wed, 04 Apr 2012 06:48:53 -0500 [thread overview]
Message-ID: <4F7C3525.7080301@codemonkey.ws> (raw)
In-Reply-To: <4F7B610D.8000101@redhat.com>
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
>>
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: 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: Wed, 04 Apr 2012 06:48:53 -0500 [thread overview]
Message-ID: <4F7C3525.7080301@codemonkey.ws> (raw)
In-Reply-To: <4F7B610D.8000101@redhat.com>
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
>>
>
>
next prev parent reply other threads:[~2012-04-04 11:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 14:43 KVM call minutes April 3 Markus Armbruster
2012-04-03 14:43 ` [Qemu-devel] " Markus Armbruster
2012-04-03 20:43 ` Dor Laor
2012-04-04 1:18 ` Michael Roth
2012-04-04 1:18 ` Michael Roth
2012-04-04 7:40 ` Paolo Bonzini
2012-04-04 7:40 ` Paolo Bonzini
2012-04-04 10:37 ` Michael Roth
2012-04-04 10:37 ` [Qemu-devel] " Michael Roth
2012-04-04 10:53 ` Dor Laor
2012-04-04 10:53 ` Dor Laor
2012-04-04 11:52 ` Anthony Liguori
2012-04-04 11:52 ` Anthony Liguori
2012-04-04 12:01 ` Dor Laor
2012-04-04 12:01 ` Dor Laor
2012-04-04 12:14 ` Michael Roth
2012-04-04 12:14 ` Michael Roth
2012-04-04 13:21 ` Igor Mammedov
2012-04-04 13:21 ` Igor Mammedov
2012-04-04 14:39 ` Michael Roth
2012-04-05 16:16 ` Avi Kivity
2012-04-05 16:16 ` Avi Kivity
2012-04-04 11:48 ` Anthony Liguori [this message]
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=4F7C3525.7080301@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.