[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231128100910.GSZWW8RnyhX0YQjwDm@fat_crate.local>
Date: Tue, 28 Nov 2023 11:09:10 +0100
From: Borislav Petkov <bp@...en8.de>
To: Xin Li <xin3.li@...el.com>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-edac@...r.kernel.org, linux-hyperv@...r.kernel.org,
kvm@...r.kernel.org, xen-devel@...ts.xenproject.org,
tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, luto@...nel.org,
pbonzini@...hat.com, seanjc@...gle.com, peterz@...radead.org,
jgross@...e.com, ravi.v.shankar@...el.com, mhiramat@...nel.org,
andrew.cooper3@...rix.com, jiangshanlai@...il.com,
nik.borisov@...e.com
Subject: Re: [PATCH v12 24/37] x86/idtentry: Incorporate
definitions/declarations of the FRED entries
On Mon, Oct 02, 2023 at 11:24:45PM -0700, Xin Li wrote:
> FRED and IDT can share most of the definitions and declarations so
> that in the majority of cases the actual handler implementation is the
> same.
>
> The differences are the exceptions where FRED stores exception related
> information on the stack and the sysvec implementations as FRED can
> handle irqentry/exit() in the dispatcher instead of having it in each
> handler.
>
> Also add stub defines for vectors which are not used due to Kconfig
> decisions to spare the ifdeffery in the actual FRED dispatch code.
>
> Tested-by: Shan Kang <shan.kang@...el.com>
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
> Signed-off-by: Xin Li <xin3.li@...el.com>
This makes me wonder too who the author is. The commit message text
sounds like tglx. :)
> @@ -137,6 +141,17 @@ static __always_inline void __##func(struct pt_regs *regs, \
> #define DEFINE_IDTENTRY_RAW(func) \
> __visible noinstr void func(struct pt_regs *regs)
>
> +/**
> + * DEFINE_FREDENTRY_RAW - Emit code for raw FRED entry points
LOL, "FREDENTRY"
...
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists