From: Luiz Capitulino <lcapitulino@redhat.com>
To: Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
kvm@vger.kernel.org, pbonzini@redhat.com, berrange@redhat.com,
"Peter Krempa" <pkrempa@redhat.com>,
"John Ferlan" <jferlan@redhat.com>,
libvir-list@redhat.com,
"Christian Borntraeger" <borntraeger@de.ibm.com>
Subject: Re: [RFC] kvm: x86: export vCPU halted state to sysfs
Date: Tue, 6 Feb 2018 09:05:19 -0500 [thread overview]
Message-ID: <20180206090519.2ba4b13e@redhat.com> (raw)
In-Reply-To: <22fe0322-02f2-7569-e82d-27722f642258@linux.vnet.ibm.com>
On Tue, 6 Feb 2018 11:29:46 +0100
Viktor Mihajlovski <mihajlov@linux.vnet.ibm.com> wrote:
> On 01.02.2018 21:26, Eduardo Habkost wrote:
> > On Thu, Feb 01, 2018 at 09:15:15PM +0100, Radim Krčmář wrote:
> >> 2018-02-01 12:54-0500, Luiz Capitulino:
> >>>
> >>> Libvirt needs to know when a vCPU is halted. To get this information,
> >>
> >> I don't see why upper level management should care about that, a single
> >> bit about halted state that can be incorrect at the time it is processed
> >> seems of very limited use.
> >
> > I don't see why, either.
> >
> > I'm CCing libvir-list and the people involved in the code that
> > added halt state to libvirt domain statistics.
> >
> I've posted a libvirt patch to disable query-cpus in the domain stats
> collection for all architectures other than s390. This should alleviate
> the problem until we have a better method to obtain arch-specific cpu state.
This is cool, thanks a lot.
Btw, I'll follow up this week with a replacement for qemu-cpus in QEMU.
Then we can discuss again the best long term strategy for this issue.
next prev parent reply other threads:[~2018-02-06 14:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 17:54 [RFC] kvm: x86: export vCPU halted state to sysfs Luiz Capitulino
2018-02-01 20:15 ` Radim Krčmář
2018-02-01 20:26 ` Eduardo Habkost
2018-02-02 13:53 ` Viktor Mihajlovski
2018-02-02 14:14 ` Luiz Capitulino
2018-02-02 14:15 ` Eduardo Habkost
2018-02-02 14:19 ` Daniel P. Berrangé
2018-02-02 14:21 ` Luiz Capitulino
2018-02-02 14:50 ` Eduardo Habkost
2018-02-02 14:50 ` [Qemu-devel] " Eduardo Habkost
2018-02-02 14:55 ` [libvirt] " Luiz Capitulino
2018-02-02 14:55 ` [Qemu-devel] " Luiz Capitulino
2018-02-02 15:07 ` Daniel P. Berrangé
2018-02-02 15:07 ` [Qemu-devel] " Daniel P. Berrangé
2018-02-02 15:25 ` Eduardo Habkost
2018-02-02 15:25 ` [Qemu-devel] " Eduardo Habkost
2018-02-02 16:23 ` [libvirt] " Eric Blake
2018-02-02 16:23 ` [Qemu-devel] " Eric Blake
2018-02-02 15:19 ` [libvirt] " Eric Blake
2018-02-02 15:19 ` [Qemu-devel] " Eric Blake
2018-02-02 17:23 ` Dr. David Alan Gilbert
2018-02-02 17:38 ` Eduardo Habkost
2018-02-02 15:08 ` Viktor Mihajlovski
2018-02-02 15:22 ` [libvirt] " Luiz Capitulino
2018-02-02 15:51 ` Viktor Mihajlovski
2018-02-02 15:54 ` Daniel P. Berrangé
2018-02-02 16:01 ` Luiz Capitulino
2018-02-02 16:07 ` Luiz Capitulino
2018-02-02 16:19 ` Viktor Mihajlovski
2018-02-02 17:42 ` [libvirt] " Eduardo Habkost
2018-02-02 18:50 ` Luiz Capitulino
2018-02-02 20:09 ` Eduardo Habkost
2018-02-02 20:19 ` [libvirt] " Luiz Capitulino
2018-02-02 20:41 ` Eduardo Habkost
2018-02-02 21:49 ` Luiz Capitulino
2018-02-02 21:54 ` Luiz Capitulino
2018-02-05 13:43 ` Viktor Mihajlovski
2018-02-05 13:47 ` Daniel P. Berrangé
2018-02-05 15:37 ` Luiz Capitulino
2018-02-05 16:10 ` Viktor Mihajlovski
2018-02-05 16:36 ` Luiz Capitulino
2018-02-05 22:50 ` Eduardo Habkost
2018-02-06 2:04 ` Luiz Capitulino
2018-02-02 15:55 ` [libvirt] " Luiz Capitulino
2018-02-06 10:29 ` Viktor Mihajlovski
2018-02-06 14:05 ` Luiz Capitulino [this message]
2018-02-02 12:47 ` Daniel P. Berrangé
2018-02-02 13:46 ` Luiz Capitulino
2018-02-02 12:49 ` Daniel P. Berrangé
2018-02-02 13:49 ` Luiz Capitulino
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=20180206090519.2ba4b13e@redhat.com \
--to=lcapitulino@redhat.com \
--cc=berrange@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=ehabkost@redhat.com \
--cc=jferlan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=mihajlov@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.