From: Andrew Cooper <andrew.cooper3@citrix.com>
To: speck@linutronix.de
Subject: [MODERATED] SRBDS on IvyBridge
Date: Tue, 9 Jun 2020 21:12:44 +0100 [thread overview]
Message-ID: <a94b11dd-2e45-f67f-33fe-2cb3900c63b5@citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
Hello,
It has recently become clear that IvyBridge isn't getting microcode to
address this issue.
This has caused me to start taking remediation actions for Xen. It
occurs to me that the same will work for Linux.
For the virt case, hiding the RDRAND CPUID bit will work around the
problem, by not allowing unwitting software to use RDRAND when it might
be snooped upon.
IvyBridge CPUs also support CPUID Faulting (tracked by
X86_FEATURE_CPUID_FAULT), which means the same technique could be
applied to native userspace software. There is already a PRCTL
(ARCH_SET_CPUID) to do this, which could be extended.
~Andrew
reply other threads:[~2020-06-09 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a94b11dd-2e45-f67f-33fe-2cb3900c63b5@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=speck@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;
as well as URLs for NNTP newsgroup(s).