All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: L!TF Bulletin #4: The state of the horrors
Date: Fri, 13 Jul 2018 11:56:08 -0400	[thread overview]
Message-ID: <20180713155608.GA11304@char.US.ORACLE.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1807131608360.2171@nanos.tec.linutronix.de>

On Fri, Jul 13, 2018 at 05:08:35PM +0200, speck for Thomas Gleixner wrote:
> Hi!
> 
> The repository has been updated with the following changes since bulletin #3:
> 
>   - Online sibling threads when SMT control is switched from off to on
> 
>   - Expose the VMX mitigation state properly in the l1tf vulnerability file
> 
>   - Fix EPT off handling
> 
>   - Make the kvm L1D flush parameter runtime controllable
> 
>   - Add the 'l1tf' kernel command line option
> 
>   - Add documentation about the whole mess
> 
> The master branch is still based on 4.18-rc1 and merges almost cleanly into
> 4.18-rc4+ with a very trivial conflict. It's not going to be rebased
> because the commit SHA1s are used in the stable branches and are also
> already used in distro backports.
> 
> The stable branches linux-4.14.y, linux-4.16.y and linux-4.17.y have been
> rebased to the latest stable versions. David Woodhouse said he's looking
> into updating the linux-4.9.y stable branch in the next days.
> 
> Git bundle against v4.18-rc1 is attached.
> 
> Thanks everyone involved for patches, testing, review and entertaining
> discussions!

You may also want to backport 

git cherry-pick 84676c1f21e8
git cherry-pick adbe552349f2d

As in the stable trees. The reason being that with 'nosmt' the megasas controller
goes bonky and stops working.

> 
> Thanks,
> 
> 	tglx

  reply	other threads:[~2018-07-13 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 15:08 L!TF Bulletin #4: The state of the horrors Thomas Gleixner
2018-07-13 15:56 ` Konrad Rzeszutek Wilk [this message]
2018-07-14 12:57   ` Thomas Gleixner
2018-07-14 19:08     ` [MODERATED] " Greg KH
2018-07-15  7:32       ` Greg KH
2018-07-18 19:36 ` Andi Kleen
2018-07-18 19:45   ` Thomas Gleixner
2018-07-19  8:46     ` [MODERATED] Re: ***UNCHECKED*** " Alexander Graf
2018-07-23 16:10 ` [MODERATED] " David Woodhouse

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=20180713155608.GA11304@char.US.ORACLE.com \
    --to=konrad.wilk@oracle.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.