From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
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 v2 1/1] sparc: fix accurate exception reporting in copy_{from,to}_user for M7
Date: Mon, 01 Sep 2025 16:18:14 +0200 [thread overview]
Message-ID: <ydd4itm45p5.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4c92d08cff24c04023bff8555ecf3bbd2eb0e944.camel@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Mon, 01 Sep 2025 09:05:58 +0200")
Hi Adrian,
> On Mon, 2025-09-01 at 09:00 +0200, Rainer Orth wrote:
>> > in the past, you reported stability issues with the Linux kernel when running
>> > inside an LDOM on SPARC M7/M8. Could you verify whether the patch above fixes
>> > these problems or whether at least they don't introduce regressions?
>>
>> thanks for the heads-up. Indeed the hangs persist even when the system
>> is idle. However, I've never built a Linux kernel before and have way
>> too much on the plate to try now. Besides, I don't have a reproducer
>> for the issue, so even with a patch I'd have to wait for an extended
>> period of time to see if the issue is gone, so I'll just wait until the
>> patch lands in the Debian/sparc64 repo and see if it helps.
>
> Would it work if I built a kernel for you plus installation instructions
> and a quick explanation how to test it?
I wouldn't mind trying, but as I said it's difficult to say when I can
claim success given the lack of a reproducer. All I can report reliably
is failure ;-)
> FWIW, we consider the patch already acceptable when it doesn't introduce
> any regressions.
>
> I did some testing on a SPARC S7 yesterday, but the problem is that the
> support for SPARC S7 in the Linux kernel is incomplete at the moment and
> I had to add it quickly myself which did actually work but I really would
> like to verify it on M7 or M8 again to at least not cause regressions.
The only system that I can test on is S7 (a Netra S7-2 actually). While
I also have a T8-1, that's reserved for cfarm work.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2025-09-01 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 12:18 sparc: Another fix for accurate exception reporting in copy_{from,to}_user Michael Karcher
2025-08-28 12:18 ` [PATCH 1/1] sparc: fix accurate exception reporting in copy_{from_to}_user for M7 Michael Karcher
2025-08-28 12:36 ` John Paul Adrian Glaubitz
2025-08-28 13:04 ` [PATCH v2 1/1] sparc: fix accurate exception reporting in copy_{from,to}_user " Michael Karcher
2025-08-31 23:43 ` John Paul Adrian Glaubitz
2025-09-01 7:00 ` Rainer Orth
2025-09-01 7:05 ` John Paul Adrian Glaubitz
2025-09-01 14:18 ` Rainer Orth [this message]
2025-09-01 19:15 ` John Paul Adrian Glaubitz
2025-09-04 14:19 ` [PATCH 1/1] sparc: fix accurate exception reporting in copy_{from_to}_user " 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=ydd4itm45p5.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--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®