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 0/3] x86: Allow variable-sized event frame
Date: Tue, 18 Mar 2025 00:07:58 -0700 [thread overview]
Message-ID: <20250318070801.903045-1-xin@zytor.com> (raw)
This was initially posted as part of the FRED patch series and turned
down due to its unacceptable quality:
https://lore.kernel.org/lkml/20230410081438.1750-31-xin3.li@intel.com/
Now try another attempt to meet the bar.
A FRED event frame could contain different amount of information for
different event types, e.g., #MCE could push extra bytes of information,
or perhaps even for different instances of the same event type. Thus
the size of an event frame pushed by a FRED CPU is not fixed and the
address of a pt_regs structure that is used to save the user level
context of current task is not at a fixed offset from top of current
task kernel stack.
This patch set adds a new field named 'user_pt_regs' in the thread_info
structure to save the address of user level context pt_regs structure,
thus to eliminate the need of any advance information of event frame
size and allow a FRED CPU to push variable-sized event frame.
With the above change, we can
1) Remove the padding space at top of the init stack because there is
no user level context for init task.
2) Get rid of TOP_OF_KERNEL_STACK_PADDING on x86_64, which was defined
to 0 for IDT to keep the code consistent with 32bit.
Link to v1: https://lore.kernel.org/lkml/20240617084516.1484390-1-xin@zytor.com/
Xin Li (Intel) (3):
x86/fred: Allow variable-sized event frame
x86: Remove the padding space at top of the init stack
x86: Get rid of TOP_OF_KERNEL_STACK_PADDING on x86_64
arch/x86/entry/entry_fred.c | 22 +++++++++++++++++
arch/x86/include/asm/processor.h | 38 +++++++++++++++++++++++-------
arch/x86/include/asm/thread_info.h | 19 +++++----------
arch/x86/kernel/process.c | 21 +++++++++++++++++
arch/x86/kernel/vmlinux.lds.S | 18 ++++++++++++--
include/linux/thread_info.h | 1 +
kernel/fork.c | 6 +++++
7 files changed, 101 insertions(+), 24 deletions(-)
base-commit: 6575d1b4a6ef3336608127c704b612bc5e7b0fdc
--
2.48.1
next 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 Xin Li (Intel) [this message]
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 ` [PATCH v2 3/3] x86: Get rid of TOP_OF_KERNEL_STACK_PADDING on x86_64 Xin Li (Intel)
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-1-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®