From: Avi Kivity <avi@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: chrisw@redhat.com, dlaor@redhat.com, qemu-devel@nongnu.org,
rjones@redhat.com, Amit Shah <amit.shah@redhat.com>
Subject: Re: [Qemu-devel] Re: Machine-readable or parseable qemu output
Date: Thu, 15 Jan 2009 23:48:06 +0200 [thread overview]
Message-ID: <496FAF16.6040205@redhat.com> (raw)
In-Reply-To: <20090115205842.GJ23380@redhat.com>
Daniel P. Berrange wrote:
>> But you can conditionally use the new library instead of your custom
>> parsing code for newer QEMU versions.
>>
>
> That is true, but if there are a number of apps around which want to
> support multiple versions of QEMU, it is beneficial to centralize
> this conditional logic in libqemumonitor.so instead, of making each
> app implement the compat logic for the existing monitor format. I'm
> not against adding a new machine friendly monitor format, I'd just
> prefer it if one library API could provide impl for both old and new
> format, obviously preferring to use the new format where available.
>
Perhaps libvirt can donate its parsing code for use as a fallback in
libqemumonitor.so.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-01-15 21:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 11:10 [Qemu-devel] Machine-readable or parseable qemu output Amit Shah
2009-01-14 11:23 ` [Qemu-devel] " Daniel P. Berrange
2009-01-15 20:27 ` Anthony Liguori
2009-01-15 20:58 ` Daniel P. Berrange
2009-01-15 21:30 ` Anthony Liguori
2009-01-15 21:48 ` Avi Kivity [this message]
2009-01-15 22:26 ` Anthony Liguori
2009-01-14 11:28 ` Avi Kivity
2009-01-15 20:28 ` Anthony Liguori
2009-01-14 11:29 ` Richard W.M. Jones
2009-01-14 11:31 ` Avi Kivity
2009-01-14 11:36 ` Richard W.M. Jones
2009-01-14 11:45 ` Daniel P. Berrange
2009-01-14 12:37 ` Dor Laor
2009-01-14 14:05 ` Avi Kivity
2009-01-15 20:31 ` Anthony Liguori
2009-01-14 16:56 ` Jamie Lokier
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=496FAF16.6040205@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=dlaor@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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).