From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Avi Kivity <avi@redhat.com>,
quintela@redhat.com,
Developers qemu-devel <qemu-devel@nongnu.org>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call minutes for November 29
Date: Wed, 30 Nov 2011 08:38:48 -0600 [thread overview]
Message-ID: <4ED63FF8.2040101@codemonkey.ws> (raw)
In-Reply-To: <20111130143523.GC19650@garlic.tlv.redhat.com>
On 11/30/2011 08:35 AM, Alon Levy wrote:
> On Wed, Nov 30, 2011 at 07:54:30AM -0600, Anthony Liguori wrote:
> [snip]
>> But the way we're structuring QOM, we could do very simple bindings
>> that just used introspection (much like GObject does).
>
> Is this the current tree?
> http://repo.or.cz/w/qemu/aliguori.git/tree/refs/heads/qom
That's the end goal, more or less. The current submission tree is:
https://github.com/aliguori/qemu/tree/qom-upstream.4
I just need to rebase and send those out.
Regards,
Anthony Liguroi
>
>>
>> The vast majority of work is fitting everything into an object
>> model. Doing the bindings is actually fairly simple.
>>
>> Regards,
>>
>> Anthony Liguori
>>
> [snip]
>
prev parent reply other threads:[~2011-11-30 14:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 15:51 KVM call minutes for November 29 Juan Quintela
2011-11-29 15:51 ` [Qemu-devel] " Juan Quintela
2011-11-29 16:59 ` Avi Kivity
2011-11-29 16:59 ` [Qemu-devel] " Avi Kivity
2011-11-29 19:10 ` Markus Armbruster
2011-11-29 19:10 ` Markus Armbruster
2011-11-30 1:18 ` Juan Quintela
2011-11-30 1:18 ` [Qemu-devel] " Juan Quintela
2011-12-01 9:32 ` Avi Kivity
2011-12-01 9:32 ` Avi Kivity
2011-11-29 22:59 ` Anthony Liguori
2011-11-29 22:59 ` Anthony Liguori
2011-11-30 9:22 ` Alon Levy
2011-11-30 9:22 ` [Qemu-devel] " Alon Levy
2011-11-30 9:54 ` Daniel P. Berrange
2011-11-30 13:54 ` Anthony Liguori
2011-11-30 13:54 ` Anthony Liguori
2011-11-30 14:35 ` Alon Levy
2011-11-30 14:35 ` Alon Levy
2011-11-30 14:38 ` Anthony Liguori [this message]
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=4ED63FF8.2040101@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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.