qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: agraf@suse.de, ehabkost@redhat.com, armbru@redhat.com,
	cohuck@redhat.com, david@redhat.com, dgilbert@redhat.com,
	borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
	pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCHv3 2/4] qmp: add query-cpus-fast
Date: Thu, 15 Feb 2018 15:59:47 +0100	[thread overview]
Message-ID: <55d9d665-df3d-80d1-2aab-a914493febc8@linux.vnet.ibm.com> (raw)
In-Reply-To: <cded2e23-fa97-0a11-c30c-9c6b79088fcf@redhat.com>

On 15.02.2018 15:53, Eric Blake wrote:
> On 02/15/2018 08:40 AM, Viktor Mihajlovski wrote:
>> On 15.02.2018 15:19, Eric Blake wrote:
>>> On 02/15/2018 04:20 AM, Viktor Mihajlovski wrote:
>>>> From: Luiz Capitulino <lcapitulino@redhat.com>
>>>>
>>>> The query-cpus command has an extremely serious side effect:
>>>> it always interrupts all running vCPUs so that they can run
>>>> ioctl calls. This can cause a huge performance degradation for
>>>> some workloads. And most of the information retrieved by the
>>>> ioctl calls are not even used by query-cpus.
>>>>
>>>> This commit introduces a replacement for query-cpus called
> 
>>> You know, we have no back-compat guarantees on HMP.  We could make 'info
>>> cpu' just ALWAYS call query-cpus-fast, with no HMP counterpart for the
>>> slower query-cpus, and without needing a deprecation period.  But I'll
>>> leave that up to David if that makes more sense.
>> Ditching info cpus_fast would make me happy as well, because it would
>> cause less headache on the libvirt side of things.
> 
> Why is libvirt using HMP in the first place?  Libvirt should always be
> using the QMP command, when one exists.
> Which it does, but there's still a lot of fallback code including HMP
"info cpus". In real life this should of course never be used, because
the QMP is always there.

-- 
Regards,
 Viktor Mihajlovski

  reply	other threads:[~2018-02-15 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 10:20 [Qemu-devel] [PATCHv3 0/4] ] add query-cpu-fast and related s390 changes Viktor Mihajlovski
2018-02-15 10:20 ` [Qemu-devel] [PATCHv3 1/4] qmp: expose s390-specific CPU info Viktor Mihajlovski
2018-02-15 10:20 ` [Qemu-devel] [PATCHv3 2/4] qmp: add query-cpus-fast Viktor Mihajlovski
2018-02-15 14:19   ` Eric Blake
2018-02-15 14:40     ` Viktor Mihajlovski
2018-02-15 14:53       ` Eric Blake
2018-02-15 14:59         ` Viktor Mihajlovski [this message]
2018-02-15 10:20 ` [Qemu-devel] [PATCHv3 3/4] qmp: add architecture specific cpu data for query-cpus-fast Viktor Mihajlovski
2018-02-15 10:20 ` [Qemu-devel] [PATCHv3 4/4] qemu-doc: deprecate query-cpus and info cpus Viktor Mihajlovski
2018-02-15 14:23   ` 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=55d9d665-df3d-80d1-2aab-a914493febc8@linux.vnet.ibm.com \
    --to=mihajlov@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=armbru@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=ehabkost@redhat.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).