public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kvm@vger.kernel.org, Jim Mattson <jmattson@google.com>,
	dave.hansen@linux.intel.com,  hpa@zytor.com, jpoimboe@kernel.org,
	kai.huang@intel.com,  linux-kernel@vger.kernel.org,
	mingo@redhat.com,  pawan.kumar.gupta@linux.intel.com,
	pbonzini@redhat.com, sandipan.das@amd.com,  tglx@linutronix.de,
	x86@kernel.org
Subject: Re: [PATCH v5 0/4] Distinguish between variants of IBPB
Date: Fri, 1 Nov 2024 09:03:04 -0700	[thread overview]
Message-ID: <ZyT7uDqK29J46a0P@google.com> (raw)
In-Reply-To: <20241101153857.GAZyT2EdLXKs7ZmDFx@fat_crate.local>

On Fri, Nov 01, 2024, Borislav Petkov wrote:
> On Thu, Oct 31, 2024 at 12:51:33PM -0700, Sean Christopherson wrote:
> > [1/4] x86/cpufeatures: Clarify semantics of X86_FEATURE_IBPB
> >       https://github.com/kvm-x86/linux/commit/43801a0dbb38
> > [2/4] x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET
> >       https://github.com/kvm-x86/linux/commit/99d252e3ae3e
> 
> ff898623af2e ("x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET")

Doh.  I think I'll rebase the entire misc branch onto rc5, realistically the only
downside is having to send updates for all of the hashes.

Thanks for catching this!

  reply	other threads:[~2024-11-01 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11 21:43 [PATCH v5 0/4] Distinguish between variants of IBPB Jim Mattson
2024-10-11 21:43 ` [PATCH v5 1/4] x86/cpufeatures: Clarify semantics of X86_FEATURE_IBPB Jim Mattson
2024-10-11 21:43 ` [PATCH v5 2/4] x86/cpufeatures: Define X86_FEATURE_AMD_IBPB_RET Jim Mattson
2024-10-11 21:43 ` [PATCH v5 3/4] KVM: x86: Advertise AMD_IBPB_RET to userspace Jim Mattson
2024-10-11 21:43 ` [PATCH v5 4/4] KVM: x86: AMD's IBPB is not equivalent to Intel's IBPB Jim Mattson
2024-10-14 15:48   ` Tom Lendacky
2024-10-31 19:51 ` [PATCH v5 0/4] Distinguish between variants of IBPB Sean Christopherson
2024-11-01 15:40   ` Borislav Petkov
2024-11-01 16:03     ` Sean Christopherson [this message]
2024-11-01 19:28       ` 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=ZyT7uDqK29J46a0P@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jmattson@google.com \
    --cc=jpoimboe@kernel.org \
    --cc=kai.huang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=pbonzini@redhat.com \
    --cc=sandipan.das@amd.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