From: Balbir Singh <sblbir@amazon.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>
Cc: <peterz@infradead.org>, <linux-kernel@vger.kernel.org>,
<keescook@chromium.org>, Balbir Singh <sblbir@amazon.com>
Subject: [PATCH v1 0/3] Fixes to L1D flushing (on top of linux-next and
Date: Wed, 18 Nov 2020 10:49:31 +1100 [thread overview]
Message-ID: <20201117234934.25985-1-sblbir@amazon.com> (raw)
There were concerns with the current interface (checking for the state
of SMT of the core at opt-in time [1]). These patches change the
interface to send a SIGBUS to the task if
a. It opts into L1D flushing
b. Runs on a core with SMT enabled
There are also documentation fixes. I've tested the patches at my end,
but would appreciate a broad review of the change in functionality
and/or any recommended doc updates.
[1] http://lkml.iu.edu/hypermail/linux/kernel/2009.3/09310.html
[2] http://lkml.iu.edu/hypermail/linux/kernel/2009.3/09613.html
NOTE: For testing these patches, specifically the SIGBUS behaviour,
there needs to be contention on the CPU where the task that opts
into L1D flushing is running to see the SIGBUS being sent to it
(the deterministic bit is that if there is scope of data leak
the task will get killed)
Balbir Singh (3):
x86/mm: change l1d flush runtime prctl behaviour
Documentation: Update the new SIGBUS behaviour for tasks
Documentation/l1d_flush: Fix up warning with labels
.../admin-guide/hw-vuln/l1d_flush.rst | 12 +++---
arch/Kconfig | 4 ++
arch/x86/Kconfig | 1 +
arch/x86/mm/tlb.c | 37 +++++++++++--------
include/linux/sched.h | 10 +++++
5 files changed, 42 insertions(+), 22 deletions(-)
--
2.17.1
next reply other threads:[~2020-11-17 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 23:49 Balbir Singh [this message]
2020-11-17 23:49 ` [PATCH v1 1/3] x86/mm: change l1d flush runtime prctl behaviour Balbir Singh
2020-11-17 23:49 ` [PATCH v1 2/3] Documentation: Update the new SIGBUS behaviour for tasks Balbir Singh
2020-11-17 23:49 ` [PATCH v1 3/3] Documentation/l1d_flush: Fix up warning with labels Balbir Singh
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=20201117234934.25985-1-sblbir@amazon.com \
--to=sblbir@amazon.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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