From: Yosry Ahmed <yosry@kernel.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Venkatesh Srinivas <venkateshs@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yosry Ahmed <yosry@kernel.org>
Subject: [PATCH v2 0/3] KVM: SVM: Advertise TCE to userspace
Date: Sat, 7 Mar 2026 01:16:16 +0000 [thread overview]
Message-ID: <20260307011619.2324234-1-yosry@kernel.org> (raw)
Advertise TCE to userspace, allowing guests to set EFER.TCE, potentially
gaining some performance. Patchees 1 & 2 are prep work suggested by
Sean.
v1: https://lore.kernel.org/kvm/20260306002327.1225504-1-yosry@kernel.org/
Venkatesh Srinivas (1):
KVM: SVM: Advertise Translation Cache Extensions to userspace
Yosry Ahmed (2):
KVM: x86: Move some EFER bits enablement to common code
KVM: x86: Use kvm_cpu_cap_has() for EFER bits enablement checks
arch/x86/kvm/cpuid.c | 1 +
arch/x86/kvm/svm/svm.c | 7 -------
arch/x86/kvm/vmx/vmx.c | 4 ----
arch/x86/kvm/x86.c | 20 ++++++++++++++++++++
4 files changed, 21 insertions(+), 11 deletions(-)
base-commit: 5128b972fb2801ad9aca54d990a75611ab5283a9
--
2.53.0.473.g4a7958ca14-goog
next reply other threads:[~2026-03-07 1:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 1:16 Yosry Ahmed [this message]
2026-03-07 1:16 ` [PATCH v2 1/3] KVM: x86: Move some EFER bits enablement to common code Yosry Ahmed
2026-03-07 1:16 ` [PATCH v2 2/3] KVM: x86: Use kvm_cpu_cap_has() for EFER bits enablement checks Yosry Ahmed
2026-03-07 1:16 ` [PATCH v2 3/3] KVM: SVM: Advertise Translation Cache Extensions to userspace Yosry Ahmed
2026-03-07 1:54 ` Andrew Cooper
2026-03-09 13:53 ` Yosry Ahmed
2026-03-09 15:06 ` Sean Christopherson
2026-03-09 15:10 ` Yosry Ahmed
2026-03-09 22:53 ` Venkatesh Srinivas
2026-04-03 15:13 ` [PATCH v2 0/3] KVM: SVM: Advertise TCE " Sean Christopherson
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=20260307011619.2324234-1-yosry@kernel.org \
--to=yosry@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=venkateshs@google.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