From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: 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>,
Sohil Mehta <sohil.mehta@intel.com>,
Paul Lai <paul.c.lai@intel.com>
Cc: alexander.shishkin@linux.intel.com
Subject: Re: [PATCH v2 00/12] Enable Linear Address Space Separation support
Date: Tue, 30 May 2023 16:07:48 +0300 [thread overview]
Message-ID: <875y8aynkr.fsf@ubik.fi.intel.com> (raw)
In-Reply-To: <20230530114247.21821-1-alexander.shishkin@linux.intel.com>
Alexander Shishkin <alexander.shishkin@linux.intel.com> writes:
> Changes from v1[1]:
> - Emulate vsyscall violations in execute mode in the #GP fault handler
> - Use inline memcpy and memset while patching alternatives
> - Remove CONFIG_X86_LASS
> - Make LASS depend on SMAP
> - Dropped the minimal KVM enabling patch
Also, I've unfortunately overlooked adding my SoBs to the patches. This
is a mistake, I'll fix it in the next round.
Regards,
--
Alex
prev parent reply other threads:[~2023-05-30 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 11:42 [PATCH v2 00/12] Enable Linear Address Space Separation support Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 01/12] x86/cpu: Enumerate the LASS feature bits Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 02/12] x86/asm: Introduce inline memcpy and memset Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 03/12] x86/alternatives: Disable LASS when patching kernel alternatives Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 04/12] x86/cpu: Enable LASS during CPU initialization Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 05/12] x86/cpu: Remove redundant comment during feature setup Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 06/12] x86/vsyscall: Reorganize the #PF emulation code Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 07/12] x86/traps: Consolidate user fixups in exc_general_protection() Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 08/12] x86/vsyscall: Add vsyscall emulation for #GP Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 09/12] x86/vsyscall: Disable LASS if vsyscall mode is set to EMULATE Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 10/12] x86/vsyscall: Document the fact that vsyscall=emulate disables LASS Alexander Shishkin
2023-05-30 11:42 ` [PATCH v2 11/12] x86/cpu: Set LASS CR4 bit as pinning sensitive Alexander Shishkin
2023-05-30 11:42 ` [RFC v2 12/12] x86/efi: Disable LASS enforcement when switching to EFI MM Alexander Shishkin
2023-05-30 13:07 ` Alexander Shishkin [this message]
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=875y8aynkr.fsf@ubik.fi.intel.com \
--to=alexander.shishkin@linux.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=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