LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michael Ellerman <mpe@ellerman.id.au>,
	linuxppc-dev@lists.ozlabs.org, Olof Johansson <olof@lixom.net>
Subject: Spectre+Meltdown
Date: Sun, 7 Jan 2018 14:04:40 +0100	[thread overview]
Message-ID: <86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de> (raw)
In-Reply-To: <874lnzz5y3.fsf@concordia.ellerman.id.au>

Hello Michael,

Thanks for your reply. We are using P.A. Semi and Freescale CPUs.

@Olof
Do you have some infos for us?

Thanks,
Christian


On 06/01/18 10:34, Michael Ellerman wrote:
> Christian Zigotzky <chzigotzky@xenosoft.de> writes:
>
>> Hi All,
>>
>> Do we have some information regarding Spectre+Meltdown for our users?
>>
>> It could be that we have some security issues in our PowerPC CPUs.
> There's a statement from IBM here:
>
>    https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/
>
>
> I think you're mostly using pasemi CPUs right? I don't have any
> information on them, and obviously it's going to be hard to find anyone
> who might know. You might be best finding a proof of concept somewhere
> and actually testing it.
>
> cheers
>

  reply	other threads:[~2018-01-07 13:04 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   ` Christian Zigotzky [this message]
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             ` Spectre+Meltdown Michal Suchánek
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=86eade29-a56d-2aab-050e-366f4d43ab2f@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --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