From: Luiz Capitulino <lcapitulino@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com, eblake@redhat.com,
ehabkost@redhat.com, mihajlov@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 2/2] qmp: document query-cpus performance issue
Date: Thu, 8 Feb 2018 09:00:00 -0500 [thread overview]
Message-ID: <20180208090000.3bfc5cd6@redhat.com> (raw)
In-Reply-To: <20180208092928.GN20703@redhat.com>
On Thu, 8 Feb 2018 09:29:28 +0000
Daniel P. Berrangé <berrange@redhat.com> wrote:
> On Wed, Feb 07, 2018 at 12:50:14PM -0500, Luiz Capitulino wrote:
> > Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> > ---
> > qapi-schema.json | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/qapi-schema.json b/qapi-schema.json
> > index 82d6f12b53..0665a14dba 100644
> > --- a/qapi-schema.json
> > +++ b/qapi-schema.json
> > @@ -526,6 +526,10 @@
> > #
> > # Returns a list of information about each virtual CPU.
> > #
> > +# WARNING: This command incurs a performance penalty for latency
> > +# sensitive workloads and hence it's not recommended to
> > +# to be used in production. Use query-cpus-fast instead
>
> I suggest being more explicit about exactly what the problem is, so people
> understand implications if they choose to still use it. ie
I'll add your text.
>
> This command causes vCPU threads to exit to userspace, which causes
> an small interruption guest CPU execution. This will have a negative
> impact on realtime guests and other latency sensitive guest workloads.
> It is recommended to use query-cpus-fast instead of this command to
> avoid the vCPU interruption.
>
> Regards,
> Daniel
prev parent reply other threads:[~2018-02-08 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 17:50 [Qemu-devel] [PATCH 0/2] qmp: add query-cpus-fast Luiz Capitulino
2018-02-07 17:50 ` [Qemu-devel] [PATCH 1/2] " Luiz Capitulino
2018-02-07 18:49 ` Eric Blake
2018-02-08 7:41 ` Viktor Mihajlovski
2018-02-08 10:13 ` Viktor Mihajlovski
2018-02-08 13:59 ` Luiz Capitulino
2018-02-08 19:59 ` Eduardo Habkost
2018-02-08 20:59 ` Eric Blake
2018-02-08 21:41 ` Eduardo Habkost
2018-02-09 8:13 ` Viktor Mihajlovski
2018-02-07 17:50 ` [Qemu-devel] [PATCH 2/2] qmp: document query-cpus performance issue Luiz Capitulino
2018-02-07 18:50 ` Eric Blake
2018-02-07 19:14 ` Luiz Capitulino
2018-02-08 9:29 ` Daniel P. Berrangé
2018-02-08 14:00 ` Luiz Capitulino [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=20180208090000.3bfc5cd6@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=ehabkost@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).