From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Luiz Capitulino" <lcapitulino@redhat.com>,
"Peter Krempa" <pkrempa@redhat.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
libvir-list@redhat.com, "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org,
"Viktor Mihajlovski" <mihajlov@linux.vnet.ibm.com>,
"Christian Borntraeger" <borntraeger@de.ibm.com>,
"John Ferlan" <jferlan@redhat.com>,
pbonzini@redhat.com
Subject: Re: [Qemu-devel] [RFC] kvm: x86: export vCPU halted state to sysfs
Date: Fri, 2 Feb 2018 17:23:59 +0000 [thread overview]
Message-ID: <20180202172359.GA2591@work-vm> (raw)
In-Reply-To: <20180202145014.GI26425@localhost.localdomain>
* Eduardo Habkost (ehabkost@redhat.com) wrote:
> (CCing qemu-devel)
>
> On Fri, Feb 02, 2018 at 09:21:59AM -0500, Luiz Capitulino wrote:
> > On Fri, 2 Feb 2018 14:19:38 +0000
> > Daniel P. Berrangé <berrange@redhat.com> wrote:
> > > On Fri, Feb 02, 2018 at 12:15:54PM -0200, Eduardo Habkost wrote:
> [...]
> > > > It would be also interesting to update QEMU QMP documentation to
> > > > clarify the arch-specific semantics of "halted".
> > >
> > > Any also especially clarify the awful performance implications of running
> > > this particular query command. In general I would not expect query-xxx
> > > monitor commands to interrupt all vcpus, so we should clearly warn about
> > > this !
> >
> > Or deprecate it...
>
> We could deprecate the expensive fields on query-cpus, and move
> them to a more expensive query-cpu-state command. I believe most
> users of query-cpus are only interested in qom_path, thread_id,
> and topology info.
Would that data be available without the bql? I ask because if it is
then a small advantage to having a separate command is that the command
could be marked OOB with Peter's new series and never take the lock.
Dave
> Markus, Eric: from the QAPI point of view, is it OK to remove
> fields between QEMU versions, as long as we follow our
> deprecation policy?
>
> --
> Eduardo
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2018-02-02 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180201125441.2f5b4fdd@redhat.com>
[not found] ` <20180201201514.GB660@flask>
[not found] ` <20180201202649.GG26425@localhost.localdomain>
[not found] ` <edc27e9a-9660-eed0-dd03-016fa2e966b7@linux.vnet.ibm.com>
[not found] ` <20180202141554.GH26425@localhost.localdomain>
[not found] ` <20180202141938.GJ15403@redhat.com>
[not found] ` <20180202092159.48d9bd4c@redhat.com>
2018-02-02 14:50 ` [Qemu-devel] [RFC] kvm: x86: export vCPU halted state to sysfs Eduardo Habkost
2018-02-02 14:55 ` Luiz Capitulino
2018-02-02 15:07 ` Daniel P. Berrangé
2018-02-02 15:25 ` Eduardo Habkost
2018-02-02 16:23 ` Eric Blake
2018-02-02 15:19 ` Eric Blake
2018-02-02 17:23 ` Dr. David Alan Gilbert [this message]
2018-02-02 17:38 ` Eduardo Habkost
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=20180202172359.GA2591@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=ehabkost@redhat.com \
--cc=jferlan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@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).