mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xin Li <xin@zytor.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, luto@kernel.org,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	jmill@asu.edu, andrew.cooper3@citrix.com
Subject: Re: [PATCH v1 1/1] x86/fred: Remove ENDBR64 from FRED entry points
Date: Tue, 15 Jul 2025 08:34:51 -0700	[thread overview]
Message-ID: <025501f2-5122-44c2-ae20-0cce86e8c426@zytor.com> (raw)
In-Reply-To: <20250715084034.GO1613200@noisy.programming.kicks-ass.net>

On 7/15/2025 1:40 AM, Peter Zijlstra wrote:
> On Mon, Jul 14, 2025 at 11:50:57PM -0700, Xin Li wrote:
>> On 7/14/2025 11:44 PM, Xin Li (Intel) wrote:
>>> The FRED specification v9.0 states that there is no need for FRED
>>> event handlers to begin with ENDBR64, because in the presence of
>>> supervisor indirect branch tracking, FRED event delivery does not
>>> enter the WAIT_FOR_ENDBRANCH state.
>>>
>>> As a result, remove ENDBR64 from FRED entry points.
>>>
>>> Then add ANNOTATE_NOENDBR to indicate that FRED entry points will
>>> never be used for indirect calls to suppress an objtool warning.
>>>
>>> This change implies that any indirect CALL/JMP to FRED entry points
>>> causes #CP in the presence of supervisor indirect branch tracking.
>>>
>>> Credit goes to Jennifer Miller<jmill@asu.edu> and other contributors
>>> from Arizona State University whose work led to this change.
>>>
>>> Link:https://lore.kernel.org/linux-hardening/Z60NwR4w%2F28Z7XUa@ubun/
>>> Reviewed-by: H. Peter Anvin (Intel)<hpa@zytor.com>
>>> Signed-off-by: Xin Li (Intel)<xin@zytor.com>
>>> Cc: Jennifer Miller<jmill@asu.edu>
>>> Cc: Peter Zijlstra<peterz@infradead.org>
>>> Cc: Andrew Cooper<andrew.cooper3@citrix.com>
>>> Cc: H. Peter Anvin<hpa@zytor.com>
>> Sorry, forgot to put CC stable.
> Fixes: 14619d912b65 ("x86/fred: FRED entry/exit and dispatch code")
> 
> Right?

You bet!

Will send v2 to address it soon.

  reply	other threads:[~2025-07-15 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15  6:44 Xin Li (Intel)
2025-07-15  6:50 ` Xin Li
2025-07-15  8:40   ` Peter Zijlstra
2025-07-15 15:34     ` Xin Li [this message]
2025-07-15 15:49 ` Andrew Cooper
2025-07-15 16:10   ` Xin Li

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=025501f2-5122-44c2-ae20-0cce86e8c426@zytor.com \
    --to=xin@zytor.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jmill@asu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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

all inboxes | Powered by JetHome®