From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, rkrcmar@redhat.com,
ehabkost@redhat.com
Subject: Re: [RFC] kvm: x86: export vCPU halted state to sysfs
Date: Fri, 2 Feb 2018 12:49:25 +0000 [thread overview]
Message-ID: <20180202124925.GB15403@redhat.com> (raw)
In-Reply-To: <20180201125441.2f5b4fdd@redhat.com>
On Thu, Feb 01, 2018 at 12:54:41PM -0500, Luiz Capitulino wrote:
>
> Libvirt needs to know when a vCPU is halted. To get this information,
> libvirt has started using the query-cpus command from QEMU. However,
> if in kernel irqchip is in use, query-cpus will force all vCPUs
> to user-space since they have to issue the KVM_GET_MP_STATE ioctl.
> This has catastrophic implications to low-latency workloads like
> KVM-RT and zero packet loss with DPDK. To make matters worse, there's
> an OpenStack service called ceilometer that causes libvirt to
> issue query-cpus every few minutes.
>
> The solution proposed in this patch is to export the vCPU
> halted state in the already existing vcpu directory in sysfs.
> This way, libvirt can read the vCPU halted state from sysfs and avoid
> using the query-cpus command. This solution seems to be sufficient
> for libvirt needs, but it has the following cons:
>
> * vcpu information in sysfs lives in a debug directory, so
> libvirt would be basing its API on debug info
Is this part of regular sysfs mount point, or does it require a
debug fs to be mounted separately at /sys/fs/debug ?
> * Currently, only x86 supports the vcpu dir in sysfs, so
> we'd have to expand this to other archs (should be doable)
Yep, that would be fairly important
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-02-02 12:49 UTC|newest]
Thread overview: 44+ 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:55 ` [libvirt] " Luiz Capitulino
2018-02-02 15:07 ` Daniel P. Berrangé
2018-02-02 15:25 ` Eduardo Habkost
2018-02-02 16:23 ` [libvirt] " Eric Blake
2018-02-02 15:19 ` Eric Blake
2018-02-02 17:23 ` [Qemu-devel] " 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
2018-02-02 12:47 ` Daniel P. Berrangé
2018-02-02 13:46 ` Luiz Capitulino
2018-02-02 12:49 ` Daniel P. Berrangé [this message]
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=20180202124925.GB15403@redhat.com \
--to=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox