From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Olof Johansson <olof@lixom.net>
Cc: "R.T.Dickinson" <rtd@a-eon.com>, Matthew Leaman <matthew@a-eon.biz>
Subject: The PA6T is still vulnerable
Date: Wed, 29 Dec 2021 17:06:47 +0100 [thread overview]
Message-ID: <F651905D-FC8B-43D4-A5DC-FFAFEF5AD69F@xenosoft.de> (raw)
Hi All,
The P.A. Semi PA6T is still vulnerable.
Architecture: ppc64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Big Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Model: 1.2 (pvr 0090 0102)
Model name: PA6T, altivec supported
L1d cache: 128 KiB
L1i cache: 128 KiB
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Vulnerable
Vulnerability Mds: Not affected
Vulnerability Meltdown: Vulnerable
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Mitigation; __user pointer sanitization
Vulnerability Spectre v2: Vulnerable
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Could you please check this issue?
Thanks,
Christian
next reply other threads:[~2021-12-29 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 16:06 Christian Zigotzky [this message]
2021-12-30 21:48 ` The PA6T is still vulnerable Olof Johansson
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=F651905D-FC8B-43D4-A5DC-FFAFEF5AD69F@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matthew@a-eon.biz \
--cc=olof@lixom.net \
--cc=rtd@a-eon.com \
/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