From: Peter Zijlstra <peterz@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Pengfei Xu <pengfei.xu@intel.com>,
"Yang, Weijiang" <weijiang.yang@intel.com>,
"Su, Heng" <heng.su@intel.com>
Subject: Re: [PATCH 0/3] x86/kvm, objtool: Fix KVM "missing ENDBR" bug
Date: Fri, 19 Aug 2022 09:50:08 +0200 [thread overview]
Message-ID: <Yv9AsJoDRep8h0vZ@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <64365019-57dc-b449-8178-30428e09adf8@redhat.com>
On Thu, Aug 18, 2022 at 07:25:57PM +0200, Paolo Bonzini wrote:
> On 8/18/22 17:53, Josh Poimboeuf wrote:
> > Fix the "missing ENDBR" KVM bug, along with a couple of preparatory
> > patches.
> >
> > Josh Poimboeuf (3):
> > x86/ibt, objtool: Add IBT_NOSEAL()
> > x86/kvm: Simplify FOP_SETCC()
> > x86/kvm: Fix "missing ENDBR" BUG for fastop functions
> >
> > arch/x86/include/asm/ibt.h | 10 ++++++++++
> > arch/x86/kvm/emulate.c | 26 ++++++--------------------
> > tools/objtool/check.c | 3 ++-
> > 3 files changed, 18 insertions(+), 21 deletions(-)
> >
>
> Queued, thanks!
OK, let me drop them from the queue then ;-)
prev parent reply other threads:[~2022-08-19 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 15:53 [PATCH 0/3] x86/kvm, objtool: Fix KVM "missing ENDBR" bug Josh Poimboeuf
2022-08-18 15:53 ` [PATCH 1/3] x86/ibt, objtool: Add IBT_NOSEAL() Josh Poimboeuf
2022-08-18 21:39 ` [PATCH v1.1] " Josh Poimboeuf
2022-08-19 5:54 ` Pengfei Xu
2022-08-18 15:53 ` [PATCH 2/3] x86/kvm: Simplify FOP_SETCC() Josh Poimboeuf
2022-08-18 15:53 ` [PATCH 3/3] x86/kvm: Fix "missing ENDBR" BUG for fastop functions Josh Poimboeuf
2022-08-18 17:25 ` [PATCH 0/3] x86/kvm, objtool: Fix KVM "missing ENDBR" bug Paolo Bonzini
2022-08-19 7:50 ` Peter Zijlstra [this message]
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=Yv9AsJoDRep8h0vZ@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=heng.su@intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pengfei.xu@intel.com \
--cc=weijiang.yang@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.