LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Suchánek" <msuchanek@suse.de>
To: Li Yang <leoyang.li@nxp.com>
Cc: Olof Johansson <olof@lixom.net>,
	Michal Suchanek <hramrach@gmail.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Christian Zigotzky <chzigotzky@xenosoft.de>
Subject: Re: Spectre+Meltdown
Date: Fri, 23 Nov 2018 19:59:55 +0100	[thread overview]
Message-ID: <20181123195955.1bdcdd80@kitsune.suse.cz> (raw)
In-Reply-To: <CADRPPNRtexannDrv8WtD2f3sQr9nwkN2PPgvh6m2r4d6BvqitQ@mail.gmail.com>

On Wed, 10 Jan 2018 18:09:45 -0600
Li Yang <leoyang.li@nxp.com> wrote:

Hello,

> On Mon, Jan 8, 2018 at 2:17 AM, Christian Zigotzky
> <chzigotzky@xenosoft.de> wrote:
> > Hi All,
> >
> > Thanks a lot for your replies.
> >
> > @NXP developers: Could you please tell us some information?  
> 
> We have done some investigation but it is not ready to be published
> yet.  You can get more information from your support channel right
> now.

With this summary paper https://arxiv.org/abs/1811.05441 it should be
possible to take the manual for your favourite CPU and see which
exploitable optimizations it does have, and how are these exploits
mitigated.

Thanks

Michal


  reply	other threads:[~2018-11-23 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 15:09 Spectre+Meltdown Christian Zigotzky
2018-01-04 21:27 ` Spectre+Meltdown Michal Suchánek
2018-01-06  9:34 ` Spectre+Meltdown Michael Ellerman
2018-01-07 13:04   ` Spectre+Meltdown Christian Zigotzky
2018-01-07 18:54     ` Spectre+Meltdown Olof Johansson
2018-01-08  1:14       ` Spectre+Meltdown Michal Suchanek
2018-01-08  8:17         ` Spectre+Meltdown Christian Zigotzky
2018-01-11  0:09           ` Spectre+Meltdown Li Yang
2018-11-23 18:59             ` Michal Suchánek [this message]
2018-11-24  9:14               ` Spectre+Meltdown Christian Zigotzky

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=20181123195955.1bdcdd80@kitsune.suse.cz \
    --to=msuchanek@suse.de \
    --cc=chzigotzky@xenosoft.de \
    --cc=hramrach@gmail.com \
    --cc=leoyang.li@nxp.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=olof@lixom.net \
    /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