* [PATCH v1 1/1] x86/entry/fred: Push __KERNEL_CS directly
@ 2025-08-22 7:16 Xin Li (Intel)
2025-08-22 11:42 ` [tip: x86/cleanups] " tip-bot2 for Xin Li (Intel)
0 siblings, 1 reply; 2+ messages in thread
From: Xin Li (Intel) @ 2025-08-22 7:16 UTC (permalink / raw)
To: linux-kernel; +Cc: luto, tglx, mingo, bp, dave.hansen, x86, hpa, xin
Push __KERNEL_CS directly, rather than moving it into RAX and then
pushing RAX.
Suggested-by: H. Peter Anvin (Intel) <hpa@zytor.com>
Signed-off-by: Xin Li (Intel) <xin@zytor.com>
---
arch/x86/entry/entry_64_fred.S | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/entry/entry_64_fred.S b/arch/x86/entry/entry_64_fred.S
index 907bd233c6c1..3c1511feadf7 100644
--- a/arch/x86/entry/entry_64_fred.S
+++ b/arch/x86/entry/entry_64_fred.S
@@ -97,8 +97,7 @@ SYM_FUNC_START(asm_fred_entry_from_kvm)
push %rdi /* fred_ss handed in by the caller */
push %rbp
pushf
- mov $__KERNEL_CS, %rax
- push %rax
+ push $__KERNEL_CS
/*
* Unlike the IDT event delivery, FRED _always_ pushes an error code
base-commit: 3da01ffe1aeaa0d427ab5235ba735226670a80d9
--
2.50.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* [tip: x86/cleanups] x86/entry/fred: Push __KERNEL_CS directly
2025-08-22 7:16 [PATCH v1 1/1] x86/entry/fred: Push __KERNEL_CS directly Xin Li (Intel)
@ 2025-08-22 11:42 ` tip-bot2 for Xin Li (Intel)
0 siblings, 0 replies; 2+ messages in thread
From: tip-bot2 for Xin Li (Intel) @ 2025-08-22 11:42 UTC (permalink / raw)
To: linux-tip-commits
Cc: H. Peter Anvin (Intel), Xin Li (Intel), Borislav Petkov (AMD),
x86, linux-kernel
The following commit has been merged into the x86/cleanups branch of tip:
Commit-ID: 5be502174bf0f5d0aafaab57fa4512723d6d2973
Gitweb: https://git.kernel.org/tip/5be502174bf0f5d0aafaab57fa4512723d6d2973
Author: Xin Li (Intel) <xin@zytor.com>
AuthorDate: Fri, 22 Aug 2025 00:16:44 -07:00
Committer: Borislav Petkov (AMD) <bp@alien8.de>
CommitterDate: Fri, 22 Aug 2025 13:12:50 +02:00
x86/entry/fred: Push __KERNEL_CS directly
Push __KERNEL_CS directly, rather than moving it into RAX and then
pushing RAX.
No functional changes.
Suggested-by: H. Peter Anvin (Intel) <hpa@zytor.com>
Signed-off-by: Xin Li (Intel) <xin@zytor.com>
Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
Link: https://lore.kernel.org/20250822071644.1405268-1-xin@zytor.com
---
arch/x86/entry/entry_64_fred.S | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/x86/entry/entry_64_fred.S b/arch/x86/entry/entry_64_fred.S
index 29c5c32..cb5ff2b 100644
--- a/arch/x86/entry/entry_64_fred.S
+++ b/arch/x86/entry/entry_64_fred.S
@@ -97,8 +97,7 @@ SYM_FUNC_START(asm_fred_entry_from_kvm)
push %rdi /* fred_ss handed in by the caller */
push %rbp
pushf
- mov $__KERNEL_CS, %rax
- push %rax
+ push $__KERNEL_CS
/*
* Unlike the IDT event delivery, FRED _always_ pushes an error code
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-08-22 11:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-08-22 7:16 [PATCH v1 1/1] x86/entry/fred: Push __KERNEL_CS directly Xin Li (Intel)
2025-08-22 11:42 ` [tip: x86/cleanups] " tip-bot2 for Xin Li (Intel)
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®