From: Rene Rebe <rene@exactcode.com>
To: glaubitz@physik.fu-berlin.de
Cc: kernel@mkarcher.dialup.fu-berlin.de,
linux-kernel@vger.kernel.org, sparclinux@vger.kernel.org,
andreas@gaisler.com, anthony.yznaga@oracle.com
Subject: Re: [PATCH 3/4] sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara
Date: Tue, 02 Sep 2025 18:51:01 +0200 (CEST) [thread overview]
Message-ID: <20250902.185101.101005511917098882.rene@exactcode.com> (raw)
In-Reply-To: <cf4e16f7846a3324521828e71c0676b9c524ebbf.camel@physik.fu-berlin.de>
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> Hi Rene,
>
> On Tue, 2025-09-02 at 18:40 +0200, Rene Rebe wrote:
> > Hi,
> >
> > From: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>
> >
> > > Fixes: 7ae3aaf53f16 ("sparc64: Convert NGcopy_{from,to}_user to accurate exception reporting.")
> > > Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>
> >
> > Tested-by: René Rebe <rene@exactcode.com> # UltraSparc T4 SPARC T4-1 Server
>
> Thanks for the testing! However, this actually needs to be tested on a SPARC T1
> as both T2 and T4 have their own implementation that is being used. Testing on a
> T4 will therefore not invoke this particular code unless you modify the kernel in
> head_64.S to employ the Niagara 1 code on Niagara 4.
Ah right, sorry, IIRC you wrote that :-/
> Do you happen to have a SPARC T1?
Unfortuantely not. A T2 user might have one, but I could also modify
the kernel and use the less optimized T1 code if that helps, ...
René
> Adrian
>
> --
> .''`. John Paul Adrian Glaubitz
> : :' : Debian Developer
> `. `' Physicist
> `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--
René Rebe, ExactCODE GmbH, Berlin, Germany
https://exactcode.com | https://t2linux.com | https://rene.rebe.de
next prev parent reply other threads:[~2025-09-02 16:51 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 [this message]
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
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=20250902.185101.101005511917098882.rene@exactcode.com \
--to=rene@exactcode.com \
--cc=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kernel@mkarcher.dialup.fu-berlin.de \
--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®