From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org, Andreas Larsson <andreas@gaisler.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>
Subject: Re: [PATCH 1/4] sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC
Date: Fri, 29 Aug 2025 12:53:33 +0200 [thread overview]
Message-ID: <05acb1676ddc1881e2b9b3fa82f1335c42c2f47e.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20250826160312.2070-2-kernel@mkarcher.dialup.fu-berlin.de>
Hello,
On Tue, 2025-08-26 at 18:03 +0200, Michael Karcher wrote:
> Fixes: cb736fdbb208 ("sparc64: Convert U1copy_{from,to}_user to accurate exception reporting.")
> Signed-off-by: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>
> ---
> arch/sparc/lib/U1memcpy.S | 19 ++++++++++---------
> 1 file changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/arch/sparc/lib/U1memcpy.S b/arch/sparc/lib/U1memcpy.S
> index 635398ec7540..154fbd35400c 100644
> --- a/arch/sparc/lib/U1memcpy.S
> +++ b/arch/sparc/lib/U1memcpy.S
> @@ -164,17 +164,18 @@ ENTRY(U1_gs_40_fp)
> retl
> add %o0, %o2, %o0
> ENDPROC(U1_gs_40_fp)
> -ENTRY(U1_g3_0_fp)
> - VISExitHalf
> - retl
> - add %g3, %o2, %o0
> -ENDPROC(U1_g3_0_fp)
> ENTRY(U1_g3_8_fp)
> VISExitHalf
> add %g3, 8, %g3
> retl
> add %g3, %o2, %o0
> ENDPROC(U1_g3_8_fp)
> +ENTRY(U1_g3_16_fp)
> + VISExitHalf
> + add %g3, 16, %g3
> + retl
> + add %g3, %o2, %o0
> +ENDPROC(U1_g3_16_fp)
> ENTRY(U1_o2_0_fp)
> VISExitHalf
> retl
> @@ -547,18 +548,18 @@ FUNC_NAME: /* %o0=dst, %o1=src, %o2=len */
> 62: FINISH_VISCHUNK(o0, f44, f46)
> 63: UNEVEN_VISCHUNK_LAST(o0, f46, f0)
>
> -93: EX_LD_FP(LOAD(ldd, %o1, %f2), U1_g3_0_fp)
> +93: EX_LD_FP(LOAD(ldd, %o1, %f2), U1_g3_8_fp)
> add %o1, 8, %o1
> subcc %g3, 8, %g3
> faligndata %f0, %f2, %f8
> - EX_ST_FP(STORE(std, %f8, %o0), U1_g3_8_fp)
> + EX_ST_FP(STORE(std, %f8, %o0), U1_g3_16_fp)
> bl,pn %xcc, 95f
> add %o0, 8, %o0
> - EX_LD_FP(LOAD(ldd, %o1, %f0), U1_g3_0_fp)
> + EX_LD_FP(LOAD(ldd, %o1, %f0), U1_g3_8_fp)
> add %o1, 8, %o1
> subcc %g3, 8, %g3
> faligndata %f2, %f0, %f8
> - EX_ST_FP(STORE(std, %f8, %o0), U1_g3_8_fp)
> + EX_ST_FP(STORE(std, %f8, %o0), U1_g3_16_fp)
> bge,pt %xcc, 93b
> add %o0, 8, %o0
>
Verified to work on QEMU which emulates an UltraSPARC II:
root@debian:~# cat /proc/cpuinfo
cpu : TI UltraSparc IIi (Sabre)
fpu : UltraSparc IIi integrated FPU
pmu : ultra12
prom : OBP 3.10.24 1999/01/01 01:01
type : sun4u
ncpus probed : 1
ncpus active : 1
D$ parity tl1 : 0
I$ parity tl1 : 0
cpucaps : flush,stbar,swap,muldiv,v9,mul32,div32,v8plus,vis
Cpu0ClkTck : 0000000005f5e100
MMU Type : Spitfire
MMU PGSZs : 8K,64K,512K,4MB
State:
CPU0: online
root@debian:~#
While there were no obvious problems on UltraSPARC before, these may show after several
days of uptime, similar to Niagara 4. I remember though that there were user reports of
unstable kernels on real UltraSPARC I and II machines.
Tested-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
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-08-29 10:53 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 [this message]
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
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=05acb1676ddc1881e2b9b3fa82f1335c42c2f47e.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=andreas@gaisler.com \
--cc=anthony.yznaga@oracle.com \
--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®