From: Andi Kleen <ak@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
linux-kernel@vger.kernel.org, bp@alien8.de, luto@kernel.org,
hpa@zytor.com, dave.hansen@intel.com, tony.luck@intel.com,
ravi.v.shankar@intel.com, markus.t.metzger@intel.com
Subject: Re: [PATCH v9 00/17] Enable FSGSBASE instructions
Date: Fri, 15 Nov 2019 11:12:00 -0800 [thread overview]
Message-ID: <20191115191200.GD22747@tassilo.jf.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1911151926380.28787@nanos.tec.linutronix.de>
On Fri, Nov 15, 2019 at 07:29:17PM +0100, Thomas Gleixner wrote:
> On Fri, 4 Oct 2019, Chang S. Bae wrote:
> >
> > Updates from v8 [10]:
> > * Internalized the interrupt check in the helper functions (Andy L.)
> > * Simplified GS base helper functions (Tony L.)
> > * Changed the patch order to put the paranoid path changes before the
> > context switch changes (Tony L.)
> > * Fixed typos (Randy D.) and massaged a few sentences in the documentation
> > * Massaged the FSGSBASE enablement message
>
> That still lacks what Andy requested quite some time ago in the V8 thread:
>
> https://lore.kernel.org/lkml/034aaf3a-a93d-ec03-0bbd-068e1905b774@kernel.org/
>
> "I also think that, before this series can have my ack, it needs an
> actual gdb maintainer to chime in, publicly, and state that they have
> thought about and tested the ABI changes and that gdb still works on
> patched kernels with and without FSGSBASE enabled. I realize that there
> were all kinds of discussions, but they were all quite theoretical, and
> I think that the actual patches need to be considered by people who
> understand the concerns. Specific test cases would be nice, too."
>
> What's the state of this?
Adding Markus.
-Andi
next prev parent reply other threads:[~2019-11-15 19:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 18:15 [PATCH v9 00/17] Enable FSGSBASE instructions Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 01/17] x86/ptrace: Prevent ptrace from clearing the FS/GS selector Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 02/17] selftests/x86/fsgsbase: Test GS selector on ptracer-induced GS base write Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 03/17] x86/cpu: Add 'unsafe_fsgsbase' to enable CR4.FSGSBASE Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 04/17] x86/entry/64: Clean up paranoid exit Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 05/17] x86/entry/64: Switch CR3 before SWAPGS in paranoid entry Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 06/17] x86/entry/64: Introduce the FIND_PERCPU_BASE macro Chang S. Bae
2019-10-04 18:15 ` [PATCH v9 07/17] x86/entry/64: Handle FSGSBASE enabled paranoid entry/exit Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 08/17] x86/entry/64: Document GSBASE handling in the paranoid path Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 09/17] x86/fsgsbase/64: Add intrinsics for FSGSBASE instructions Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 10/17] x86/fsgsbase/64: Enable FSGSBASE instructions in helper functions Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 11/17] x86/fsgsbase/64: Use FSGSBASE in switch_to() if available Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 12/17] x86/fsgsbase/64: Use FSGSBASE instructions on thread copy and ptrace Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 13/17] x86/speculation/swapgs: Check FSGSBASE in enabling SWAPGS mitigation Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 14/17] selftests/x86/fsgsbase: Test ptracer-induced GS base write with FSGSBASE Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 15/17] x86/fsgsbase/64: Enable FSGSBASE on 64bit by default and add a chicken bit Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 16/17] x86/elf: Enumerate kernel FSGSBASE capability in AT_HWCAP2 Chang S. Bae
2019-10-04 18:16 ` [PATCH v9 17/17] Documentation/x86/64: Add documentation for GS/FS addressing mode Chang S. Bae
2019-10-04 22:54 ` Randy Dunlap
2019-11-15 18:29 ` [PATCH v9 00/17] Enable FSGSBASE instructions Thomas Gleixner
2019-11-15 19:12 ` Andi Kleen [this message]
2019-11-29 14:56 ` Metzger, Markus T
2019-11-29 16:51 ` Andy Lutomirski
2019-12-02 8:23 ` Metzger, Markus T
2019-12-04 20:20 ` Andy Lutomirski
2019-12-10 8:27 ` Metzger, Markus T
2020-02-24 18:02 ` Bae, Chang Seok
2020-04-13 20:03 ` Sasha Levin
2020-04-14 0:32 ` Andi Kleen
2020-04-17 13:30 ` Sasha Levin
2020-04-17 15:52 ` Andy Lutomirski
2020-04-20 14:13 ` Andi Kleen
2020-04-20 17:14 ` Thomas Gleixner
2020-04-21 16:06 ` Sasha Levin
2020-04-21 16:49 ` Andy Lutomirski
2020-04-21 20:02 ` Andi Kleen
2020-04-21 17:15 ` Bae, Chang Seok
2020-04-21 19:56 ` Andi Kleen
2020-04-21 20:21 ` Andy Lutomirski
2020-04-21 20:51 ` Sasha Levin
2020-04-22 23:00 ` Andy Lutomirski
2020-04-23 4:08 ` Sasha Levin
2020-04-25 22:39 ` Thomas Gleixner
2020-04-26 2:52 ` Sasha Levin
2020-04-26 10:04 ` Thomas Gleixner
2020-04-14 15:47 ` Bae, Chang Seok
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=20191115191200.GD22747@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.