From: satheesh rajendran <sathnaga@linux.vnet.ibm.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
satheesh rajendran <sathnaga@linux.vnet.ibm.com>,
mihajlov@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH] hmp.c: Revert hmp_info_cpus output format
Date: Tue, 27 Mar 2018 19:09:08 +0530 [thread overview]
Message-ID: <20180327133908.GB31240@localhost.localdomain> (raw)
In-Reply-To: <20180327132011.GO4005@redhat.com>
On Tue, Mar 27, 2018 at 02:20:11PM +0100, Daniel P. Berrangé wrote:
> Re-adding qemu-devel address - please don't drop the mailing list from
> CC's when replying to messages on the list.
Sorry, Missed intially, had resent it but was too late :-(.
>
> On Tue, Mar 27, 2018 at 06:46:19PM +0530, satheesh rajendran wrote:
> > On Tue, Mar 27, 2018 at 01:40:00PM +0100, Daniel P. Berrangé wrote:
> > > On Tue, Mar 27, 2018 at 06:08:00PM +0530, sathnaga@linux.vnet.ibm.com wrote:
> > > > From: Satheesh Rajendran <sathnaga@linux.vnet.ibm.com>
> > > >
> > > > This commit 137b5cb6ab565cb3781d5337591e155932b4230e
> > > > refactors info cpus output and changes output format from
> > > > 'thread_id' to 'thread-id', this would break parsing
> > > > of output in above layers like libvirt, test framework etc.
> > >
> > > Libvirt doesn't use HMP, only QMP, so this shouldn't have broken libvirt
> > > afaik. HMP is not intended to be a stable API so these kind of changes
> > > should be expected.
> >
> > Am sure avocado test framework uses this output for parsing to extract threadid
>
> If avocado is relying on the HMP then it should be updated to use QMP,
> as HMP is not a stable API for automation.
>
Sure, Thanks, will change it.
> > and in libvirt atleast I checked below code uses it, I hope keeping the
> > format same as previous won't affect anything?
> >
> > in src/qemu/qemu_monitor_text.c
> > int
> > qemuMonitorTextQueryCPUs(qemuMonitorPtr mon,
> > struct qemuMonitorQueryCpusEntry **entries,
> > size_t *nentries)
> > ...
>
> This libvirt code is only executed when managing QEMU versions < 0.15,
> so not affected.
>
Okies :-)
Regards,
-Satheesh
> Regards,
> Daniel
> --
> |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o- https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
>
next prev parent reply other threads:[~2018-03-27 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 12:38 [Qemu-devel] [PATCH] hmp.c: Revert hmp_info_cpus output format sathnaga
2018-03-27 12:40 ` Daniel P. Berrangé
[not found] ` <20180327131619.GA27591@localhost.localdomain>
2018-03-27 13:20 ` Daniel P. Berrangé
2018-03-27 13:39 ` satheesh rajendran [this message]
2018-03-27 13:24 ` satheesh rajendran
2018-03-27 13:59 ` [Qemu-devel] [PATCH for-2.12] " Eric Blake
2018-03-27 14:25 ` Cornelia Huck
2018-03-27 15:32 ` Viktor Mihajlovski
2018-03-27 14:03 ` [Qemu-devel] [PATCH] " Eric Blake
2018-03-27 14:04 ` Dr. David Alan Gilbert
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=20180327133908.GB31240@localhost.localdomain \
--to=sathnaga@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--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 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).