From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "René Rebe" <rene@exactco.de>
Cc: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
Andreas Larsson <andreas@gaisler.com>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
Anthony Yznaga <anthony.yznaga@oracle.com>
Subject: Re: [PATCH v4 2/5] sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III
Date: Sun, 07 Sep 2025 19:57:37 +0200 [thread overview]
Message-ID: <35a07d38d6d59b79d28543bb4a862f14af1fa713.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <E6D1F756-419D-448A-AF35-387FDA16AC00@exactco.de>
Hi Rene,
On Sun, 2025-09-07 at 19:32 +0200, René Rebe wrote:
> It is probably a good time to mention that there are likely some other major
> TLB (or so) bug on U3. For example, I could never boot any Linux kernel
> (probably ever) with 8GB installed in my Sun Blade 1000 - it would NULL ptr
> deref very early:
Have a look at arch/sparc/kernel/head_64.S:
/* Patch copy/page operations to cheetah optimized versions. */
call cheetah_patch_copyops
nop
call cheetah_patch_copy_page
nop
call cheetah_patch_cachetlbops
nop
These patch in UltraSPARC-III-optimized versions of copy_{to,from}_user
and copy_page and TLB operations. Replacing these calls with "nop" might
tell us whether any of those is broken.
I have already replaced cheetah_patch_copyops with generic_patch_copyops
and was able to verify that the recently discovered OOPS is not related
to copy_{to,from}_user, so Michael's UltraSPARC III may still be correct
and complete.
I am testing the other two now as I think that these are good candidates.
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-07 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 22:03 [PATCH v4 0/5] Fix accurate exception reporting in SPARC assembly Michael Karcher
2025-09-04 22:03 ` [PATCH v4 1/5] sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC Michael Karcher
2025-09-04 22:03 ` [PATCH v4 2/5] sparc: fix accurate exception reporting in copy_{from_to}_user for UltraSPARC III Michael Karcher
2025-09-07 17:02 ` John Paul Adrian Glaubitz
2025-09-07 17:32 ` René Rebe
2025-09-07 17:57 ` John Paul Adrian Glaubitz [this message]
2025-09-07 17:49 ` John Paul Adrian Glaubitz
2025-09-07 18:33 ` John Paul Adrian Glaubitz
2025-09-07 21:31 ` John Paul Adrian Glaubitz
2025-09-08 6:30 ` John Paul Adrian Glaubitz
2025-09-08 6:47 ` John Paul Adrian Glaubitz
2025-09-08 6:53 ` John Paul Adrian Glaubitz
2025-09-08 22:47 ` Anthony Yznaga
2025-09-09 5:54 ` John Paul Adrian Glaubitz
2025-09-04 22:03 ` [PATCH v4 3/5] sparc: fix accurate exception reporting in copy_{from_to}_user for Niagara Michael Karcher
2025-09-04 22:03 ` [PATCH v4 4/5] sparc: fix accurate exception reporting in copy_to_user for Niagara 4 Michael Karcher
2025-09-04 22:03 ` [PATCH v4 5/5] sparc: fix accurate exception reporting in copy_{from,to}_user for M7 Michael Karcher
2025-09-19 18:03 ` [PATCH v4 0/5] Fix accurate exception reporting in SPARC assembly Andreas Larsson
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=35a07d38d6d59b79d28543bb4a862f14af1fa713.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=rene@exactco.de \
--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®