From: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
To: kvm@vger.kernel.org
Cc: seanjc@google.com, pbonzini@redhat.com,
linux-kernel@vger.kernel.org, suravee.suthikulpanit@amd.com,
vashegde@amd.com, mlevitsk@redhat.com, joao.m.martins@oracle.com,
boris.ostrovsky@oracle.com, mark.kanda@oracle.com,
alejandro.j.jimenez@oracle.com
Subject: [PATCH 0/4] Export APICv-related state via binary stats interface
Date: Mon, 29 Apr 2024 15:57:34 +0000 [thread overview]
Message-ID: <20240429155738.990025-1-alejandro.j.jimenez@oracle.com> (raw)
After discussion in the RFC thread[0], the following items were identified as
desirable to expose via the stats interface:
- APICv status: (apicv_enabled, boolean, per-vCPU)
- Guest using SynIC's AutoEOI: (synic_auto_eoi_used, boolean, per-VM)
- KVM PIT in reinject mode inhibits AVIC: (pit_reinject_mode, boolean, per-VM)
- APICv unaccelerated injections causing a vmexit (i.e. AVIC_INCOMPLETE_IPI,
AVIC_UNACCELERATED_ACCESS, APIC_WRITE): (apicv_unaccelerated_inj, counter,
per-vCPU)
Example retrieving the newly introduced stats for guest running on AMD Genoa
host, with AVIC enabled:
(QEMU) query-stats target=vcpu vcpus=['/machine/unattached/device[0]'] providers=[{'provider':'kvm','names':['apicv_unaccelerated_inj','apicv_active']}]
{
"return": [
{
"provider": "kvm",
"qom-path": "/machine/unattached/device[0]",
"stats": [
{
"name": "apicv_unaccelerated_inj",
"value": 2561
},
{
"name": "apicv_active",
"value": true
}
]
}
]
}
(QEMU) query-stats target=vm providers=[{'provider':'kvm','names':['pit_reinject_mode','synic_auto_eoi_used']}]
{
"return": [
{
"provider": "kvm",
"stats": [
{
"name": "pit_reinject_mode",
"value": false
},
{
"name": "synic_auto_eoi_used",
"value": false
}
]
}
]
}
Changes were also sanity tested on Intel Sapphire Rapids platform, with/without
IPI virtualization.
Regards,
Alejandro
[0] https://lore.kernel.org/all/20240215160136.1256084-1-alejandro.j.jimenez@oracle.com/
Alejandro Jimenez (4):
KVM: x86: Expose per-vCPU APICv status
KVM: x86: Add a VM stat exposing when SynIC AutoEOI is in use
KVM: x86: Add a VM stat exposing when KVM PIT is set to reinject mode
KVM: x86: Add vCPU stat for APICv interrupt injections causing #VMEXIT
arch/x86/include/asm/kvm_host.h | 4 ++++
arch/x86/kvm/hyperv.c | 2 ++
arch/x86/kvm/i8254.c | 2 ++
arch/x86/kvm/lapic.c | 1 +
arch/x86/kvm/svm/avic.c | 7 +++++++
arch/x86/kvm/vmx/vmx.c | 2 ++
arch/x86/kvm/x86.c | 7 ++++++-
7 files changed, 24 insertions(+), 1 deletion(-)
base-commit: 7b076c6a308ec5bce9fc96e2935443ed228b9148
--
2.39.3
next reply other threads:[~2024-04-29 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 15:57 Alejandro Jimenez [this message]
2024-04-29 15:57 ` [PATCH 1/4] KVM: x86: Expose per-vCPU APICv status Alejandro Jimenez
2024-04-29 15:57 ` [PATCH 2/4] KVM: x86: Add a VM stat exposing when SynIC AutoEOI is in use Alejandro Jimenez
2024-04-29 15:57 ` [PATCH 3/4] KVM: x86: Add a VM stat exposing when KVM PIT is set to reinject mode Alejandro Jimenez
2024-04-29 15:57 ` [PATCH 4/4] KVM: x86: Add vCPU stat for APICv interrupt injections causing #VMEXIT Alejandro Jimenez
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=20240429155738.990025-1-alejandro.j.jimenez@oracle.com \
--to=alejandro.j.jimenez@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.kanda@oracle.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vashegde@amd.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 read-only IMAP folder(s) and NNTP newsgroup(s).