public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Yosry Ahmed <yosry.ahmed@linux.dev>
To: x86@kernel.org, Sean Christopherson <seanjc@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Jim Mattson <jmattson@google.com>,
	"Kaplan, David" <David.Kaplan@amd.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Unify IBRS virtualization
Date: Thu, 13 Mar 2025 21:23:18 +0000	[thread overview]
Message-ID: <Z9NMxr0Ri7VUlJzM@google.com> (raw)
In-Reply-To: <20250221163352.3818347-1-yosry.ahmed@linux.dev>

On Fri, Feb 21, 2025 at 04:33:49PM +0000, Yosry Ahmed wrote:
> To properly virtualize IBRS on Intel, an IBPB is executed on emulated
> VM-exits to provide separate predictor modes for L1 and L2.
> 
> Similar handling is theoretically needed for AMD, unless IbrsSameMode is
> enumerated by the CPU (which should be the case for most/all CPUs
> anyway). For correctness and clarity, this series generalizes the
> handling to apply for both Intel and AMD as needed.
> 
> I am not sure if this series would land through the kvm-x86 tree or the
> tip/x86 tree.

Sean, any thoughts about this (or general feedback about this series)?

> 
> Yosry Ahmed (3):
>   x86/cpufeatures: Define X86_FEATURE_AMD_IBRS_SAME_MODE
>   KVM: x86: Propagate AMD's IbrsSameMode to the guest
>   KVM: x86: Generalize IBRS virtualization on emulated VM-exit
> 
>  arch/x86/include/asm/cpufeatures.h       |  1 +
>  arch/x86/kvm/cpuid.c                     |  1 +
>  arch/x86/kvm/svm/nested.c                |  2 ++
>  arch/x86/kvm/vmx/nested.c                | 11 +----------
>  arch/x86/kvm/x86.h                       | 18 ++++++++++++++++++
>  tools/arch/x86/include/asm/cpufeatures.h |  1 +
>  6 files changed, 24 insertions(+), 10 deletions(-)
> 
> -- 
> 2.48.1.601.g30ceb7b040-goog
> 

  parent reply	other threads:[~2025-03-13 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 16:33 [PATCH 0/3] Unify IBRS virtualization Yosry Ahmed
2025-02-21 16:33 ` [PATCH 1/3] x86/cpufeatures: Define X86_FEATURE_AMD_IBRS_SAME_MODE Yosry Ahmed
2025-02-21 16:33 ` [PATCH 2/3] KVM: x86: Propagate AMD's IbrsSameMode to the guest Yosry Ahmed
2025-02-21 16:33 ` [PATCH 3/3] KVM: x86: Generalize IBRS virtualization on emulated VM-exit Yosry Ahmed
2025-02-21 17:59   ` Jim Mattson
2025-02-21 18:39     ` Yosry Ahmed
2025-02-21 19:02       ` Jim Mattson
2025-02-21 19:25         ` Yosry Ahmed
2025-02-21 19:52           ` Jim Mattson
2025-03-13 21:23 ` Yosry Ahmed [this message]
2025-03-26 19:48   ` [PATCH 0/3] Unify IBRS virtualization Sean Christopherson
2025-03-26 19:52     ` Yosry Ahmed
2025-04-25 22:37 ` 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=Z9NMxr0Ri7VUlJzM@google.com \
    --to=yosry.ahmed@linux.dev \
    --cc=David.Kaplan@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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