From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Olof Johansson <olof@lixom.net>,
Darren Stevens <darren@stevens-zone.net>,
Trevor Dickinson <rtd2@xtra.co.nz>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: PASEMI: Wrong lscpu info since the RC1 of kernel 6.0
Date: Thu, 29 Sep 2022 06:31:14 +0200 [thread overview]
Message-ID: <D358C452-0B3D-4FA0-9A14-C756D79507F9@xenosoft.de> (raw)
In-Reply-To: <5D6A3537-CF85-499C-97AF-ACF241DFF597@xenosoft.de>
Just for info:
The values have been fine again since the RC7 of kernel 6.0.
— Christian
> On 7. Sep 2022, at 06:25, Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
>
> Hi All,
>
> I use the Nemo board with a PASemi PA6T CPU and some values of lscpu are wrong since the RC1 of kernel 6.0.
>
> ┌──(mintppc㉿mintppc)-[~]
> └─$ lscpu
> 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: 2
> Core(s) per socket: 1
> Socket(s): 1
> Model: 1.2 (pvr 0090 0102)
> Model name: PA6T, altivec supported
> L1d cache: 64 KiB
> L1i cache: 64 KiB
> Vulnerability Itlb multihit: Not affected
> Vulnerability L1tf: Vulnerable
> Vulnerability Mds: Not affected
> Vulnerability Meltdown: Vulnerable
> Vulnerability Mmio stale data: Not affected
> Vulnerability Retbleed: Not affected
> 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
>
> —-
>
> One core with 2 threads is wrong. Two cores are correct. Each core has one thread.
>
> Have you modified the detection of the CPU?
>
> Thanks,
> Christian
prev parent reply other threads:[~2022-09-29 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 4:25 PASEMI: Wrong lscpu info since the RC1 of kernel 6.0 Christian Zigotzky
2022-09-29 4:31 ` Christian Zigotzky [this message]
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=D358C452-0B3D-4FA0-9A14-C756D79507F9@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=olof@lixom.net \
--cc=rtd2@xtra.co.nz \
/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;
as well as URLs for NNTP newsgroup(s).