[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <D5C8ABB5-5185-43EC-8C3E-106DBBEBF389@zytor.com>
Date: Fri, 20 Jun 2025 20:35:45 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Dave Hansen <dave.hansen@...el.com>,
Andrew Cooper <andrew.cooper3@...rix.com>
CC: acme@...hat.com, aik@....com, akpm@...ux-foundation.org,
alexander.shishkin@...ux.intel.com, ardb@...nel.org, ast@...nel.org,
bp@...en8.de, brijesh.singh@....com, changbin.du@...wei.com,
christophe.leroy@...roup.eu, corbet@....net,
daniel.sneddon@...ux.intel.com, dave.hansen@...ux.intel.com,
ebiggers@...gle.com, geert+renesas@...der.be, houtao1@...wei.com,
jgg@...pe.ca, jgross@...e.com, jpoimboe@...nel.org,
kai.huang@...el.com, kees@...nel.org, kirill.shutemov@...ux.intel.com,
leitao@...ian.org, linux-doc@...r.kernel.org,
linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux@...musvillemoes.dk, luto@...nel.org,
mcgrof@...nel.org, mhiramat@...nel.org, michael.roth@....com,
mingo@...nel.org, mingo@...hat.com, namhyung@...nel.org,
paulmck@...nel.org, pawan.kumar.gupta@...ux.intel.com,
peterz@...radead.org, rick.p.edgecombe@...el.com, rppt@...nel.org,
sandipan.das@....com, shijie@...amperecomputing.com,
sohil.mehta@...el.com, tglx@...utronix.de, tj@...nel.org,
tony.luck@...el.com, vegard.nossum@...cle.com, x86@...nel.org,
xin3.li@...el.com, xiongwei.song@...driver.com, ytcoode@...il.com
Subject: Re: [PATCHv6 07/16] x86/vsyscall: Reorganize the #PF emulation code
On June 20, 2025 4:21:38 PM PDT, Dave Hansen <dave.hansen@...el.com> wrote:
>On 6/20/25 16:08, Andrew Cooper wrote:
>>> But, the resulting code is wonky. It needs to do something more like this:
>>>
>>> if ((error_code & (X86_PF_WRITE | X86_PF_USER)) != X86_PF_USER)
>>> return false;
>>>
>>> if (error_code & X86_PF_INSTR))
>>> return __emulate_vsyscall(regs, address);
>> To do this, LASS needs a proper interlink against NX || SMEP.
>>
>> If neither NX nor SMEP are active, the CPU does not report X86_PF_INSTR,
>> meaning that fetches are reported as plain reads.
>Interesting point.
>
>I think the easiest way to do this is just make a cpuid_deps[] entry for
>LASS and NX. If there's a CPU where LASS is available but where NX isn't
>available, we have much bigger problems on our hands.
Indeed. There is exactly zero reason to support this case.
Powered by blists - more mailing lists