[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvJNe2rzXfcogFFX@zn.tnic>
Date: Tue, 9 Aug 2022 14:05:15 +0200
From: Borislav Petkov <bp@...en8.de>
To: ira.weiny@...el.com
Cc: Rik van Riel <riel@...riel.com>,
Dave Hansen <dave.hansen@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
linux-kernel@...r.kernel.org, kernel-team@...com
Subject: Re: [RFC PATCH 2/5] entry: Add calls for save/restore auxiliary
pt_regs
On Fri, Aug 05, 2022 at 10:30:06AM -0700, ira.weiny@...el.com wrote:
> From: Ira Weiny <ira.weiny@...el.com>
>
> Some architectures have auxiliary pt_regs space available to store
> information on the stack during exceptions. This information is easier
> to obtain and store within C code rather than in arch specific assembly.
There are others?
Because I would've done this whole thing in arch/x86/ only...
> diff --git a/kernel/entry/common.c b/kernel/entry/common.c
> index 8c0f334c4b75..a70a0f314aee 100644
> --- a/kernel/entry/common.c
> +++ b/kernel/entry/common.c
> @@ -317,7 +317,7 @@ noinstr irqentry_state_t irqentry_enter(struct pt_regs *regs)
>
> if (user_mode(regs)) {
> irqentry_enter_from_user_mode(regs);
> - return ret;
> + goto aux_save;
Why do you have to goto and do the instrumentation sandwitch around it
at the goto label?
Why not simply do
if (user_mode(regs)) {
irqentry_enter_from_user_mode(regs);
arch_save_aux_pt_regs(regs);
return ret;
and so on?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists