[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <871qerj0tk.ffs@tglx>
Date: Thu, 21 Sep 2023 12:08:23 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Nikolay Borisov <nik.borisov@...e.com>, Xin Li <xin3.li@...el.com>,
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
Cc: mingo@...hat.com, bp@...en8.de, 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
Subject: Re: [PATCH v10 28/38] x86/fred: FRED entry/exit and dispatch code
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
> 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&id=1da5c9bc119d3a749b519596b93f9b2667e93c4a
>
> It will make more sense to replace this with ia32_enabled() invocation.
> I guess this could be done as a follow-up patch based on when this is
> merged as the ia32_enbaled changes are going to be merged in 6.7.
The simplest solution is to rebase the series to tip x86/entry and just
do it right away :)
Powered by blists - more mailing lists