mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>,
	Andreas Larsson <andreas@gaisler.com>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Anthony Yznaga" <anthony.yznaga@oracle.com>,
	"René Rebe" <rene@exactcode.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 23:31:41 +0200	[thread overview]
Message-ID: <c3e1173f99e6222ab09093e1a197d6366bcf2b95.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <e791dbb534aac79805389a4b754901c24991de89.camel@physik.fu-berlin.de>

Hi,

On Sun, 2025-09-07 at 20:33 +0200, John Paul Adrian Glaubitz wrote:
> I assume that cheetah_patch_cachetlbops has to be invoked on UltraSPARC III
> since there is other code depending on it. On the other hand, the TLB code
> on UltraSPARC III was heavily overhauled in 2016 [1] which was also followed
> by a bug fix [2].
> 
> Chances are there are still bugs in the code introduced in [1].
> 
> > [1] https://github.com/torvalds/linux/commit/a74ad5e660a9ee1d071665e7e8ad822784a2dc7f
> > [2] https://github.com/torvalds/linux/commit/d3c976c14ad8af421134c428b0a89ff8dd3bd8f8

I have reverted both commits. The machine boots until it tries to start
systemd when it locks up. So, I guess if there is a bug in the TLB code
it needs to be diagnosed differently.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2025-09-07 21:31 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
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 [this message]
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=c3e1173f99e6222ab09093e1a197d6366bcf2b95.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@exactcode.com \
    --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®