sparclinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Rene Rebe <rene@exactcode.com>
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 19:11:33 +0200	[thread overview]
Message-ID: <bcc8c498ccd773919c5dfe8026e4f25139151827.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <20250902.190459.1097165280513668946.rene@exactcode.com>

On Tue, 2025-09-02 at 19:04 +0200, Rene Rebe wrote:
> someone in our Discord probably has one in the basement or attic, but
> the chances of them turning just that system on the next days or weeks
> is probably rather slim.
> 
> I guess testing all the "popular" systems: vintage collected
> workstations and affortable more modern higher performance T4 servers
> is all we got for the near future for this patches.

I just realized that QEMU can emulate a Niagara CPU, so we can test there:

https://www.qemu.org/docs/master/system/target-sparc64.html

Maybe you can test independently on QEMU as well using your kernel, then
your Tested-by will become valid.

Adrian

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

  reply	other threads:[~2025-09-02 17:11 UTC|newest]

Thread overview: 23+ 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-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-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 [this message]
2025-09-02 21:51           ` René Rebe
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

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=bcc8c498ccd773919c5dfe8026e4f25139151827.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;
as well as URLs for NNTP newsgroup(s).