From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
Andreas Faerber <afaerber@suse.de>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] QOM vs QAPI for QMP APIs
Date: Tue, 25 Feb 2014 14:39:51 +0100 [thread overview]
Message-ID: <20140225133951.GD3339@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <530C74CB.2000906@redhat.com>
Am 25.02.2014 um 11:47 hat Paolo Bonzini geschrieben:
> Il 25/02/2014 11:15, Stefan Hajnoczi ha scritto:
> >On Tue, Feb 25, 2014 at 10:46 AM, Kevin Wolf <kwolf@redhat.com> wrote:
> >>> External QOM interfaces have their place, especially for debugging or
> >>> trying out things before there is a proper API, but it's not as the
> >>> primary external interface.
> >Yes, I agree.
>
> -object is an exception to this though, isn't it?
I'd prefer if -object weren't the primary interface for anything.
We could define a few stable types that are meant to be created,
queried and manipulated using QOM, but it would blur the line.
Kevin
prev parent reply other threads:[~2014-02-25 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 9:16 [Qemu-devel] QOM vs QAPI for QMP APIs Stefan Hajnoczi
2014-02-21 14:29 ` Anthony Liguori
2014-02-21 14:37 ` Paolo Bonzini
2014-02-21 21:00 ` Eric Blake
2014-02-24 8:29 ` Markus Armbruster
2014-02-24 16:08 ` Eric Blake
2014-02-25 8:25 ` Markus Armbruster
2014-02-25 8:30 ` Andreas Färber
2014-02-25 8:30 ` Paolo Bonzini
2014-02-25 8:33 ` Andreas Färber
2014-02-21 14:32 ` Stefan Hajnoczi
2014-02-25 9:46 ` Kevin Wolf
2014-02-25 10:15 ` Stefan Hajnoczi
2014-02-25 10:47 ` Paolo Bonzini
2014-02-25 13:39 ` Kevin Wolf [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=20140225133951.GD3339@dhcp-200-207.str.redhat.com \
--to=kwolf@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@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 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).