From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 1/1 v2] Linux patch #1
Date: Fri, 29 Jun 2018 16:44:35 -0700 [thread overview]
Message-ID: <20180629234435.GD17013@tassilo.jf.intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1806300123570.6203@cbobk.fhfr.pm>
> What's wrong with having a global switch, that could be deployed across
> the whole (for example) datacenter, that says "if the cpu has L1TF issue,
> do whatever it takes to mitigate it, otherwise operate normally"?
Most people who use it would lose a lot of performance for no gain at all.
> "nosmt" doesn't let you do that, as you'd have to know what x86 system
> exactly you're booting on. The conditional one seems like the natural way
> to go.
Right that's the point. L1TF virtualization mitigation should be only done
after properly analyzing the situation, never blindly.
It's like a lot of other security threats, like let's say if your
data is properly encrypted on the wire or how you configure
a firewall. You cannot just get security blindly, but need to make some
decisions to have useful trade offs.
-Andi
next prev parent reply other threads:[~2018-06-29 23:44 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 22:53 [MODERATED] [PATCH 1/1] Linux patch #1 Jiri Kosina
2018-06-28 23:15 ` [MODERATED] " Jiri Kosina
2018-06-28 23:36 ` [MODERATED] [PATCH 1/1 v2] " Jiri Kosina
2018-06-29 8:38 ` [MODERATED] " Borislav Petkov
2018-06-29 15:43 ` Thomas Gleixner
2018-06-29 15:46 ` Thomas Gleixner
2018-06-29 16:48 ` [MODERATED] " Josh Poimboeuf
2018-06-29 16:49 ` Josh Poimboeuf
2018-06-29 19:47 ` Thomas Gleixner
2018-06-29 19:54 ` [MODERATED] " Josh Poimboeuf
2018-06-29 21:26 ` Jiri Kosina
2018-06-29 21:28 ` Jiri Kosina
2018-06-29 22:05 ` Andi Kleen
2018-06-29 22:17 ` Jiri Kosina
2018-06-29 23:21 ` Andi Kleen
2018-06-29 23:33 ` Jiri Kosina
2018-06-29 23:37 ` Jiri Kosina
2018-06-29 23:44 ` Andi Kleen [this message]
2018-06-30 0:02 ` Jiri Kosina
2018-06-30 0:41 ` Andi Kleen
2018-06-30 0:50 ` Jiri Kosina
2018-06-30 8:59 ` Thomas Gleixner
2018-06-30 17:42 ` [MODERATED] " Linus Torvalds
2018-06-30 19:30 ` Jiri Kosina
2018-06-30 19:52 ` Linus Torvalds
2018-06-30 19:58 ` Jiri Kosina
2018-07-02 14:52 ` Konrad Rzeszutek Wilk
2018-07-02 8:06 ` Thomas Gleixner
2018-07-05 20:03 ` [MODERATED] " Jon Masters
2018-07-05 20:16 ` Jiri Kosina
2018-07-05 21:29 ` Jon Masters
2018-07-05 21:39 ` Jiri Kosina
2018-07-05 22:19 ` Thomas Gleixner
2018-07-05 23:49 ` [MODERATED] " Josh Poimboeuf
2018-07-05 20:25 ` Linus Torvalds
2018-07-05 20:50 ` Thomas Gleixner
2018-07-05 21:21 ` [MODERATED] " Jon Masters
2018-07-05 21:24 ` Jon Masters
2018-06-30 14:59 ` Josh Poimboeuf
2018-06-30 23:34 ` Dave Hansen
2018-07-01 0:06 ` Linus Torvalds
2018-06-29 21:46 ` Josh Poimboeuf
2018-06-29 21:49 ` Andi Kleen
2018-06-29 21:56 ` Jiri Kosina
2018-06-29 22:05 ` Thomas Gleixner
2018-06-29 22:43 ` [MODERATED] " Luck, Tony
2018-06-30 9:05 ` Thomas Gleixner
2018-06-30 19:48 ` [MODERATED] [PATCH 1/1 v3] " Jiri Kosina
2018-06-30 21:31 ` [MODERATED] " Josh Poimboeuf
2018-06-30 21:35 ` Linus Torvalds
2018-06-30 21:43 ` Jiri Kosina
2018-06-30 22:22 ` [MODERATED] [PATCH 1/1 v4] " Jiri Kosina
2018-07-02 14:51 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-07-02 15:00 ` Jiri Kosina
2018-07-02 15:14 ` Thomas Gleixner
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=20180629234435.GD17013@tassilo.jf.intel.com \
--to=ak@linux.intel.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 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.