Messages in this thread | | | Date | Tue, 28 Nov 2023 11:09:10 +0100 | From | Borislav Petkov <> | 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@intel.com> > Signed-off-by: Thomas Gleixner <tglx@linutronix.de> > Signed-off-by: Xin Li <xin3.li@intel.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
| |