From: "Chen, Yian" <yian.chen@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
Andy Lutomirski <luto@kernel.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ravi Shankar <ravi.v.shankar@intel.com>,
"Tony Luck" <tony.luck@intel.com>,
Paul Lai <paul.c.lai@intel.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [PATCH 5/7] x86/cpu: Enable LASS (Linear Address Space Separation)
Date: Thu, 12 Jan 2023 09:56:22 -0800 [thread overview]
Message-ID: <4c1a3a82-b443-ecd7-dc38-ac0574db0b50@intel.com> (raw)
In-Reply-To: <2b523ed5-a809-1354-1050-a4cc415a102c@intel.com>
On 1/11/2023 2:22 PM, Sohil Mehta wrote:
>> +static __always_inline void setup_lass(struct cpuinfo_x86 *c)
>> +{
>> + if (cpu_feature_enabled(X86_FEATURE_LASS)) {
>> + cr4_set_bits(X86_CR4_LASS);
>> + } else {
>> + /*
>> + * only clear the feature and cr4 bits when hardware
>> + * supports LASS, in case it was enabled in a previous
>> + * boot (e.g., via kexec)
>> + */
>> + if (cpu_has(c, X86_FEATURE_LASS)) {
>> + cr4_clear_bits(X86_CR4_LASS);
>> + clear_cpu_cap(c, X86_FEATURE_LASS);
>> + }
>> + }
>> +}
>
> I am quite confused by the "else" code flow. Can you please help
> understand how this code path would be exercised?
>
The "else" branch is to disable LASS for every cpu. Addition to clear
the CR4 bit, it would be better to clear cpu feature id for consistent
result in every CPU as well, otherwise, we could see the feature id is
cleared in the boot-cpu only, for example, if user enables vsyscall.
> Also, why don't other features such as SMAP or SMEP need this type of
> handling?
It seems there is no need to have such if-else for SMAP/SMEP since the
X86_SMAP/SMEP was gone from arch/x86/Kconfig.
I see something on similar lines for UMIP.
>
> Also, how does the CR4 pinning code in the following patch play into
> this?
I did not test if pinning code works as commented: "/* These bits
should not change their value after CPU init is finished. */"
Could it flag a warning when cr4_clear_bits() is called above?
I did not observed a warning for cr4_clear_bits(), this should be okay
since it is called during init.
>
>> +
>> /* These bits should not change their value after CPU init is
>> finished. */
>> static const unsigned long cr4_pinned_mask =
>> X86_CR4_SMEP | X86_CR4_SMAP | X86_CR4_UMIP |
>> @@ -1848,6 +1865,7 @@ static void identify_cpu(struct cpuinfo_x86 *c)
>> setup_smep(c);
>> setup_smap(c);
>> setup_umip(c);
>> + setup_lass(c);
next prev parent reply other threads:[~2023-01-12 18:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 5:51 [PATCH 0/7] Enable LASS (Linear Address space Separation) Yian Chen
2023-01-10 5:51 ` [PATCH 1/7] x86/cpu: Enumerate LASS CPUID and CR4 bits Yian Chen
2023-01-10 20:14 ` Sohil Mehta
2023-01-11 0:13 ` Dave Hansen
2023-01-11 23:23 ` Chen, Yian
2023-01-12 0:06 ` Luck, Tony
2023-01-12 0:15 ` Chen, Yian
2023-01-11 19:21 ` Chen, Yian
2023-01-10 5:51 ` [PATCH 2/7] x86: Add CONFIG option X86_LASS Yian Chen
2023-01-10 21:05 ` Sohil Mehta
2023-01-12 0:13 ` Chen, Yian
2023-01-10 5:52 ` [PATCH 3/7] x86/cpu: Disable kernel LASS when patching kernel alternatives Yian Chen
2023-01-10 21:04 ` Peter Zijlstra
2023-01-11 1:01 ` Chen, Yian
2023-01-11 9:10 ` Peter Zijlstra
2023-01-10 22:41 ` Sohil Mehta
2023-01-12 0:27 ` Chen, Yian
2023-01-12 0:37 ` Dave Hansen
2023-01-12 18:36 ` Chen, Yian
2023-01-12 18:48 ` Dave Hansen
2023-02-01 2:25 ` Sohil Mehta
2023-02-01 18:20 ` Dave Hansen
2023-02-01 2:10 ` Sohil Mehta
2023-01-10 5:52 ` [PATCH 4/7] x86/vsyscall: Setup vsyscall to compromise LASS protection Yian Chen
2023-01-11 0:34 ` Sohil Mehta
2023-01-12 1:43 ` Chen, Yian
2023-01-12 2:49 ` Sohil Mehta
2023-01-21 4:09 ` Andy Lutomirski
2023-01-10 5:52 ` [PATCH 5/7] x86/cpu: Enable LASS (Linear Address Space Separation) Yian Chen
2023-01-11 22:22 ` Sohil Mehta
2023-01-12 17:56 ` Chen, Yian [this message]
2023-01-12 18:17 ` Dave Hansen
2023-01-13 1:17 ` Sohil Mehta
2023-01-13 19:39 ` Sohil Mehta
2023-01-10 5:52 ` [PATCH 6/7] x86/cpu: Set LASS as pinning sensitive CR4 bit Yian Chen
2023-01-10 5:52 ` [PATCH 7/7] x86/kvm: Expose LASS feature to VM guest Yian Chen
2023-02-07 3:21 ` Wang, Lei
2023-02-09 17:18 ` Sean Christopherson
2023-01-10 19:48 ` [PATCH 0/7] Enable LASS (Linear Address space Separation) Sohil Mehta
2023-01-10 22:57 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c1a3a82-b443-ecd7-dc38-ac0574db0b50@intel.com \
--to=yian.chen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=paul.c.lai@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=sohil.mehta@intel.com \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome