Historical speck list archives
 help / color / mirror / Atom feed
From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 0/1] SMTCTL 0
Date: Tue, 12 Jun 2018 14:06:24 -0400	[thread overview]
Message-ID: <10f6d9f9-2654-8d93-475c-d6bb484c0bdf@redhat.com> (raw)
In-Reply-To: <20180607205525.4515061108@crypto-ml.lab.linutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Hi Andi, all,

First a note that we're going with the kernel approach for the reasons
that Thomas and Jiri already described. We need it to be that easy.

On 06/07/2018 04:54 PM, speck for Andi Kleen wrote:

> - Encourages the right use model of only switching SMT state
> when it is actually needed and based on a conscious decision, 
> not unnecessarily or globally.

On this point. We're going to be having some further dialogue with the
other distros and vendors involved about best practice. Our rules say we
must always default to "secure" but the problem in this case is that
it's workload dependent. If you're running OpenStack, and you didn't do
it right (most people) then you probably put different HT threads into
different VMs so we can't just rip them out from underneath you. So we
need to be a bit more cleaver about how we handle customer guidance.

Essentially I've said to Intel (and to others) "we won't throw you under
the bus if you don't throw us under the bus", which needs dialogue.

Jon.

-- 
Computer Architect | Sent from my Fedora powered laptop


           reply	other threads:[~2018-06-12 18:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20180607205525.4515061108@crypto-ml.lab.linutronix.de>]

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=10f6d9f9-2654-8d93-475c-d6bb484c0bdf@redhat.com \
    --to=jcm@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).