From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, agraf@suse.de, ehabkost@redhat.com,
armbru@redhat.com, cohuck@redhat.com, david@redhat.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCHv4 2/4] qmp: add query-cpus-fast
Date: Fri, 16 Feb 2018 15:38:00 +0000 [thread overview]
Message-ID: <20180216153759.GB2308@work-vm> (raw)
In-Reply-To: <1389c7ab-a95b-9f5f-3bc1-434e521b946c@redhat.com>
* Eric Blake (eblake@redhat.com) wrote:
> On 02/16/2018 08:49 AM, Viktor Mihajlovski wrote:
>
> > >
> > > The HMP changes are non-trivial compared to v3, so I might have dropped
> > > all R-b and Acked-by to ensure they are looked at again.
> > >
> > > In fact,...
> > >
>
> > > > -
> > > > - if (cpu->value->CPU == monitor_get_cpu_index()) {
> > > > - active = '*';
> > > > - }
> > >
> > > The old code was doing multiple things - it was telling you the current
> > > HMP cpu (HMP has 'cpu' with no QMP counterpart, but if you are using
> > > HMP, knowing which cpu is the active target for future HMP commands that
> > > depend on the active target, this bit of information is important),
>
> > >
> > Thanks for the patience. I'll respin with the r/a-b's on patch 2/4
> > removed, but want to verify first that I can get the active cpu without
> > triggering cpu_synchronize_state via monitor_get_cpu_index...
>
> What does it matter? HMP is not the time-critical interface like QMP, so
> even if it has to synchronize things, you're no worse off than you were
> before when using HMP.
I guess it's not obvious that mon_get_cpu_index has that side effect;
although I can see why it's there since it guarantees correctness of all
the HMP data with one call; a comment might be nice to point it out.
But yes, I agree the performance cost there doesn't worry me for HMP.
Dave
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-02-16 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 12:04 [Qemu-devel] [PATCHv4 0/4] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 1/4] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-16 13:55 ` Eric Blake
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 2/4] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-16 14:03 ` Eric Blake
2018-02-16 14:49 ` Viktor Mihajlovski
2018-02-16 15:07 ` Eric Blake
2018-02-16 15:38 ` Dr. David Alan Gilbert [this message]
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 3/4] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-16 14:05 ` Eric Blake
2018-02-16 12:04 ` [Qemu-devel] [PATCHv4 4/4] qemu-doc: deprecate query-cpus Viktor Mihajlovski
2018-02-16 14:05 ` Eric Blake
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=20180216153759.GB2308@work-vm \
--to=dgilbert@redhat.com \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).