From: Xin Li <xin@zytor.com>
To: linux-kernel@vger.kernel.org
Cc: luto@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, peterz@infradead.org, brgerst@gmail.com
Subject: Re: [PATCH v1 0/3] x86: Allow variable-sized event frame
Date: Mon, 26 Aug 2024 10:32:31 -0700 [thread overview]
Message-ID: <469a7dc3-b4de-4d2b-9068-381a250273d3@zytor.com> (raw)
In-Reply-To: <20240617084516.1484390-1-xin@zytor.com>
On 6/17/2024 1:45 AM, Xin Li (Intel) wrote:
> 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/
>
> And this is another attempt to meet the bar.
>
I'm expecting to get some review comments on this patch set :-)
>
> 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.
>
>
> 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/switch_to.h | 2 +-
> 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 +++++
> 8 files changed, 102 insertions(+), 25 deletions(-)
>
>
> base-commit: 49b33979e3bf0a5424420d14f026de12f34e8b1e
next prev parent reply other threads:[~2024-08-26 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 8:45 Xin Li (Intel)
2024-06-17 8:45 ` [PATCH v1 1/3] x86/fred: " Xin Li (Intel)
2024-06-17 8:45 ` [PATCH v1 2/3] x86: Remove the padding space at top of the init stack Xin Li (Intel)
2024-06-17 8:45 ` [PATCH v1 3/3] x86: Get rid of TOP_OF_KERNEL_STACK_PADDING on x86_64 Xin Li (Intel)
2024-08-26 17:32 ` Xin Li [this message]
2024-12-04 17:59 ` [PATCH v1 0/3] x86: Allow variable-sized event frame 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=469a7dc3-b4de-4d2b-9068-381a250273d3@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@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®