LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Michal Suchanek <hramrach@gmail.com>, Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Spectre+Meltdown
Date: Mon, 8 Jan 2018 09:17:05 +0100	[thread overview]
Message-ID: <32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de> (raw)
In-Reply-To: <CAOMqctS0d9i5F1si3mDq_M1ZZM1MncXRBFKGeZ4y30J4H_1RDg@mail.gmail.com>

Hi All,

Thanks a lot for your replies.

@NXP developers: Could you please tell us some information?

Thanks,
Christian


On 08 January 2018 at 02:14AM, Michal Suchanek wrote:
> On 7 January 2018 at 19:54, Olof Johansson <olof@lixom.net> wrote:
>> On Sun, Jan 7, 2018 at 5:04 AM, Christian Zigotzky
>> <chzigotzky@xenosoft.de> wrote:
>>> Hello Michael,
>>>
>>> Thanks for your reply. We are using P.A. Semi and Freescale CPUs.
>>>
>>> @Olof
>>> Do you have some infos for us?
>> I'm low on spare time to experiment and explore what might be exposed
>> or not, and I no longer have any proprietary microarchitecture
>> documentation of the core.
>>
>> I suggest reaching out to your supplier of the silicon for commercial
>> support and information, or just going with what I'm sure will be
>> architecturally generic solutions to the problem when IBM has them
>> ready.
> The solution for IBM POWER involves patching the firmware as well as
> Linux. Without knowledge of the architecture specifics it is not
> possible to tell if other cores are affected and if the measures
> implemented by IBM can be used. In fact they probably rely on
> 64s-specific instructions and are in part implemented in 64s-specific
> assembly files.
>
> So this will not work without support for the specific core either by
> the vendor or somebody who has knowledge of the architecture details.
>
> Thanks
>
> Michal
>

  reply	other threads:[~2018-01-08  8:17 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         ` Christian Zigotzky [this message]
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=32e12e24-750d-eb98-0753-f5feca309082@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=hramrach@gmail.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