All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH 2/4] RFC-MDSv1 0
Date: Tue, 13 Nov 2018 18:32:47 -0800	[thread overview]
Message-ID: <20181114023247.GK6218@tassilo.jf.intel.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1811132143390.19754@cbobk.fhfr.pm>

On Tue, Nov 13, 2018 at 09:47:57PM +0100, speck for Jiri Kosina wrote:
> On Sun, 11 Nov 2018, speck for Andi Kleen wrote:
> 
> > We don't need to do this for guests because the L1TF cache flush will 
> > implicitely do the same flushing, and is automatically selected on MDS 
> > affected systems.
> 
> Just to make sure, as there has been some confusion around this last time 
> this has been discussed -- for the above to be true, ucode update is 
> necessary anyway, right? The L1D flush, as implemented in the current 
> publicly available ucode, doesn't flush the microarchitectural buffers, 
> that is only coming with ucode that will provide enhanced verw semantics, 
> right?

Yes that is correct.

-Andi

  parent reply	other threads:[~2018-11-14  2:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-12  3:41 [MODERATED] [PATCH 0/4] RFC-MDSv1 1 Andi Kleen
2018-11-12  3:41 ` [MODERATED] [PATCH 1/4] RFC-MDSv1 4 Andi Kleen
2018-11-12  3:41 ` [MODERATED] [PATCH 2/4] RFC-MDSv1 0 Andi Kleen
2018-11-13  0:07   ` [MODERATED] " Andrew Cooper
2018-11-13  1:35     ` Andi Kleen
2018-11-13 21:59       ` Andrew Cooper
2018-11-14  4:04         ` Andi Kleen
2018-12-09 18:12           ` Andrew Cooper
2018-11-13 20:47   ` Jiri Kosina
2018-11-13 21:04     ` Luck, Tony
2018-11-14  2:32     ` Andi Kleen [this message]
2018-11-12  3:41 ` [MODERATED] [PATCH 3/4] RFC-MDSv1 3 Andi Kleen
2018-11-12  3:41 ` [MODERATED] [PATCH 4/4] RFC-MDSv1 2 Andi Kleen
2018-11-12 22:36   ` [MODERATED] " Greg KH
2018-11-13  1:37     ` Andi Kleen

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=20181114023247.GK6218@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.