From: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>
To: x86@kernel.org, Josh Poimboeuf <jpoimboe@kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] CALL_NOSPEC fixes
Date: Fri, 28 Feb 2025 18:35:27 -0800 [thread overview]
Message-ID: <20250228-call-nospec-v3-0-96599fed0f33@linux.intel.com> (raw)
v3:
- Split the CS prefix change into a separate patch. (Ingo)
v2: https://lore.kernel.org/r/20250227-call-nospec-v2-1-895a30dceaac@linux.intel.com
- Fixed the inconsistency in the use of "\" in __CS_PREFIX. (Andrew)
- Fixed the comment to reflect that __CS_PREFIX only emits the prefix and
not the JMP/CALL. (Andrew)
v1: https://lore.kernel.org/r/20250226-call-nospec-v1-1-4dde04a5c7a7@linux.intel.com
Patch 1 simplifies CALL_NOSPEC and mimics the behavior of compiler induced
thunks.
Patch 2 adds a missing CS prefix in CALL_NOSPEC for inline asm.
---
Pawan Gupta (2):
x86/speculation: Simplify and make CALL_NOSPEC consistent
x86/speculation: Add a conditional CS prefix to CALL_NOSPEC
arch/x86/include/asm/nospec-branch.h | 32 +++++++++++++++++++-------------
1 file changed, 19 insertions(+), 13 deletions(-)
---
base-commit: d082ecbc71e9e0bf49883ee4afd435a77a5101b6
change-id: 20250226-call-nospec-b94808f0dc75
Best regards,
--
Pawan
next reply other threads:[~2025-03-01 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-01 2:35 Pawan Gupta [this message]
2025-03-01 2:35 ` [PATCH v3 1/2] x86/speculation: Simplify and make CALL_NOSPEC consistent Pawan Gupta
2025-03-03 11:12 ` [tip: x86/urgent] " tip-bot2 for Pawan Gupta
2025-03-04 10:26 ` [tip: x86/cpu] " tip-bot2 for Pawan Gupta
2025-03-01 2:35 ` [PATCH v3 2/2] x86/speculation: Add a conditional CS prefix to CALL_NOSPEC Pawan Gupta
2025-03-03 11:12 ` [tip: x86/urgent] " tip-bot2 for Pawan Gupta
2025-03-04 10:26 ` [tip: x86/cpu] " tip-bot2 for Pawan Gupta
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=20250228-call-nospec-v3-0-96599fed0f33@linux.intel.com \
--to=pawan.kumar.gupta@linux.intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®