From: "Xin Li (Intel)" <xin@zytor.com>
To: linux-kernel@vger.kernel.org
Cc: luto@kernel.org, tglx@linutronix.de, mingo@kernel.org,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, peterz@infradead.org, brgerst@gmail.com
Subject: [PATCH v2 3/3] x86: Get rid of TOP_OF_KERNEL_STACK_PADDING on x86_64
Date: Tue, 18 Mar 2025 00:08:01 -0700 [thread overview]
Message-ID: <20250318070801.903045-4-xin@zytor.com> (raw)
In-Reply-To: <20250318070801.903045-1-xin@zytor.com>
Because task_pt_regs() is now just an alias of thread_info.user_pt_regs,
and no matter whether FRED is enabled or not a user level event frame on
x86_64 is always pushed from top of current task kernel stack, i.e.,
'(unsigned long)task_stack_page(task) + THREAD_SIZE', there is no meaning
to keep TOP_OF_KERNEL_STACK_PADDING on x86_64, thus remove it.
Signed-off-by: Xin Li (Intel) <xin@zytor.com>
---
arch/x86/include/asm/processor.h | 6 ++++--
arch/x86/include/asm/thread_info.h | 10 ----------
arch/x86/kernel/process.c | 3 +--
3 files changed, 5 insertions(+), 14 deletions(-)
diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
index cbb5d2158075..ab1f9cb19b71 100644
--- a/arch/x86/include/asm/processor.h
+++ b/arch/x86/include/asm/processor.h
@@ -656,8 +656,6 @@ extern unsigned long __end_init_stack[];
*/
#define TOP_OF_INIT_STACK ((unsigned long)&__end_init_stack)
-#define task_top_of_stack(task) ((unsigned long)(task_pt_regs(task) + 1))
-
/*
* task_pt_regs() no longer converts a fixed offset from top of a task
* kernel stack to a pt_regs structure pointer, but rather returns
@@ -672,6 +670,9 @@ extern unsigned long __end_init_stack[];
#define task_pt_regs(task) ((task)->thread_info.user_pt_regs)
#ifdef CONFIG_X86_32
+#define task_top_of_stack(task) ((unsigned long)task_stack_page(task) + THREAD_SIZE \
+ - TOP_OF_KERNEL_STACK_PADDING)
+
#define INIT_THREAD { \
.sp0 = TOP_OF_INIT_STACK, \
.sysenter_cs = __KERNEL_CS, \
@@ -679,6 +680,7 @@ extern unsigned long __end_init_stack[];
#else
extern unsigned long __top_init_kernel_stack[];
+#define task_top_of_stack(task) ((unsigned long)task_stack_page(task) + THREAD_SIZE)
#define INIT_THREAD { \
.sp = (unsigned long)&__top_init_kernel_stack, \
diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h
index 4372f171c65f..8e9badd610bc 100644
--- a/arch/x86/include/asm/thread_info.h
+++ b/arch/x86/include/asm/thread_info.h
@@ -30,10 +30,6 @@
*
* In vm86 mode, the hardware frame is much longer still, so add 16
* bytes to make room for the real-mode segments.
- *
- * x86-64 has a fixed-length stack frame, but it depends on whether
- * or not FRED is enabled. Future versions of FRED might make this
- * dynamic, but for now it is always 2 words longer.
*/
#ifdef CONFIG_X86_32
# ifdef CONFIG_VM86
@@ -41,12 +37,6 @@
# else
# define TOP_OF_KERNEL_STACK_PADDING 8
# endif
-#else /* x86-64 */
-# ifdef CONFIG_X86_FRED
-# define TOP_OF_KERNEL_STACK_PADDING (2 * 8)
-# else
-# define TOP_OF_KERNEL_STACK_PADDING 0
-# endif
#endif
/*
diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
index 58c1cd4ca60a..51020caac332 100644
--- a/arch/x86/kernel/process.c
+++ b/arch/x86/kernel/process.c
@@ -124,9 +124,8 @@ int arch_dup_task_struct(struct task_struct *dst, struct task_struct *src)
*/
void arch_init_user_pt_regs(struct task_struct *tsk)
{
- unsigned long top_of_stack = (unsigned long)task_stack_page(tsk) + THREAD_SIZE;
+ unsigned long top_of_stack = task_top_of_stack(tsk);
- top_of_stack -= TOP_OF_KERNEL_STACK_PADDING;
tsk->thread_info.user_pt_regs = (struct pt_regs *)top_of_stack - 1;
}
--
2.48.1
prev parent reply other threads:[~2025-03-18 7:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:07 [PATCH v2 0/3] x86: Allow variable-sized event frame Xin Li (Intel)
2025-03-18 7:07 ` [PATCH v2 1/3] x86/fred: " Xin Li (Intel)
2025-03-18 7:08 ` [PATCH v2 2/3] x86: Remove the padding space at top of the init stack Xin Li (Intel)
2025-03-18 7:08 ` Xin Li (Intel) [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=20250318070801.903045-4-xin@zytor.com \
--to=xin@zytor.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--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®