From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Ken Link <iissmart@numberzero.org>, Magnus Lindholm <linmag7@gmail.com>
Cc: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
Andreas Larsson <andreas@gaisler.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>
Subject: Re: [PATCH 3/4] sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara
Date: Fri, 05 Sep 2025 08:36:26 +0200 [thread overview]
Message-ID: <332d8b631eec7fbf0234ab699e49f19ee059510d.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAPZdOsbQYRV=6D1Y62BZw2QH24tx0-+26n0yyG_YutvrocygiQ@mail.gmail.com>
Hi Ken,
On Thu, 2025-09-04 at 22:31 -0500, Ken Link wrote:
> I can provide additional test coverage on a T1000, using Adrian's patched kernel package from:
> https://people.debian.org/~glaubitz/sparc64/linux-image-6.12.3-sparc64-smp_6.12.3-1+sparc64_sparc64.deb
>
> $ uname -a
> Linux t1000a 6.12.3-sparc64-smp #1 SMP Debian 6.12.3-1+sparc64 (2025-08-28) sparc64 GNU/Linux
> $ lsb_release -a
>
> No LSB modules are available.
> Distributor ID: Debian
> Description: Debian GNU/Linux bookworm/sid
> Release: unstable
> Codename: sid
> $ sudo dmesg | grep T1000
> [ 0.979644] PLATFORM: banner-name [Sun Fire(TM) T1000]
> [ 0.980069] PLATFORM: name [SUNW,Sun-Fire-T1000]
> $ lscpu
> Architecture: sparc64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Big Endian
> CPU(s): 24
> On-line CPU(s) list: 0-23
> Model name: UltraSparc T1 (Niagara)
> Thread(s) per core: 4
> Core(s) per socket: 6
> Socket(s): 1
> Flags: sun4v
> Caches (sum of all):
> L1d: 192 KiB (24 instances)
> L1i: 384 KiB (24 instances)
> L2: 72 MiB (24 instances)
>
> Tested-by: Ken Link <iissmart@numberzero.org>
Thanks for the testing. I think Michael will add this as well.
For clarification to Michael, this is a "Sun Fire T1000".
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2025-09-05 6:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 16:03 Fix accurate exception reporting in SPARC assembly Michael Karcher
2025-08-26 16:03 ` [PATCH 1/4] sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC Michael Karcher
2025-08-29 10:53 ` John Paul Adrian Glaubitz
2025-09-02 16:33 ` Rene Rebe
2025-09-03 22:05 ` Jonathan Pallant
2025-08-26 16:03 ` [PATCH 2/4] sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III Michael Karcher
2025-08-27 6:34 ` John Paul Adrian Glaubitz
2025-08-28 15:53 ` John Paul Adrian Glaubitz
2025-08-30 1:57 ` Anthony Yznaga
2025-08-30 8:35 ` Michael Karcher
2025-09-04 14:05 ` Andreas Larsson
2025-09-04 14:14 ` Michael Karcher
2025-09-02 16:38 ` Rene Rebe
2025-08-26 16:03 ` [PATCH 3/4] sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara Michael Karcher
2025-08-29 21:44 ` John Paul Adrian Glaubitz
2025-09-02 16:40 ` Rene Rebe
2025-09-02 16:47 ` John Paul Adrian Glaubitz
2025-09-02 16:51 ` Rene Rebe
2025-09-02 16:53 ` John Paul Adrian Glaubitz
2025-09-02 17:04 ` Rene Rebe
2025-09-02 17:11 ` John Paul Adrian Glaubitz
2025-09-02 21:51 ` René Rebe
2025-09-05 8:04 ` Andreas Larsson
2025-09-05 9:02 ` John Paul Adrian Glaubitz
2025-09-04 18:36 ` Magnus Lindholm
2025-09-05 3:36 ` Ken Link
[not found] ` <CAPZdOsbQYRV=6D1Y62BZw2QH24tx0-+26n0yyG_YutvrocygiQ@mail.gmail.com>
2025-09-05 6:36 ` John Paul Adrian Glaubitz [this message]
2025-09-08 4:32 ` Ethan Hawke
2025-08-26 16:03 ` [PATCH 4/4] sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara 4 Michael Karcher
2025-08-27 6:37 ` John Paul Adrian Glaubitz
2025-08-28 20:21 ` John Paul Adrian Glaubitz
2025-08-29 13:24 ` Michael Karcher
2025-09-04 13:49 ` Fix accurate exception reporting in SPARC assembly Andreas Larsson
2025-09-04 17:21 ` John Paul Adrian Glaubitz
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=332d8b631eec7fbf0234ab699e49f19ee059510d.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--cc=iissmart@numberzero.org \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--cc=linmag7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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
all inboxes | Powered by JetHome®