RE: [PATCH v10 28/38] x86/fred: FRED entry/exit and dispatch code

2023-09-21 Thread Li, Xin3
> > Since future kernels will support boottime toggling of whether 32bit > > syscall interface should be enabled or not as per: > > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h= > > x86/entry=1da5c9bc119d3a749b519596b93f9b2667e93c4a > > > > It will make more sense to

Re: [PATCH v10 28/38] x86/fred: FRED entry/exit and dispatch code

2023-09-21 Thread Thomas Gleixner
On Thu, Sep 21 2023 at 12:48, Nikolay Borisov wrote: > On 14.09.23 г. 7:47 ч., Xin Li wrote: >> + >> +/* INT80 */ >> +case IA32_SYSCALL_VECTOR: >> +if (likely(IS_ENABLED(CONFIG_IA32_EMULATION))) { > > Since future kernels will support boottime toggling of whether 32bit >

Re: [PATCH v10 28/38] x86/fred: FRED entry/exit and dispatch code

2023-09-21 Thread Nikolay Borisov
On 14.09.23 г. 7:47 ч., Xin Li wrote: From: "H. Peter Anvin (Intel)" The code to actually handle kernel and event entry/exit using FRED. It is split up into two files thus: - entry_64_fred.S contains the actual entrypoints and exit code, and saves and restores registers. - entry_fred.c