From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Arnd Bergmann <arnd@kernel.org>,
linux-alpha@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Richard Henderson <richard.henderson@linaro.org>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Matt Turner <mattst88@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Marc Zyngier <maz@kernel.org>,
linux-kernel@vger.kernel.org, Michael Cree <mcree@orcon.net.nz>,
Frank Scheiner <frank.scheiner@web.de>
Subject: Re: [PATCH 00/14] alpha: cleanups for 6.10
Date: Tue, 2 Jul 2024 00:48:36 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.2406302009050.43454@angie.orcam.me.uk> (raw)
In-Reply-To: <CAHk-=wha2rH2UcTvHUYK+dNnP6UCDRkYM0atvw_GTP5Sz3OZrQ@mail.gmail.com>
On Mon, 3 Jun 2024, Linus Torvalds wrote:
> > Anyway, back to my point. A feasible solution non-intrusive for Linux
> > and low-overhead for GCC has been found. I can expedite implementation
> > and I'll see if I can regression-test it too, but I may have to rely on
> > other people to complete it after all, as I haven't been prepared for this
> > effort in the light of certain issues I have recently suffered from in my
> > lab.
>
> Yeah, if compiler support makes us not have to care, then I don't
> think the difference between pre-BWX and BWX is going to matter much
> for the kernel.
>
> The real pain with alpha has been that it's special enough that it
> affects non-alpha code, and BWX was one big piece of that.
Understood, that's burden beyond justification for an obsolete legacy
platform.
> That said, some of the EV4 misfeatures end up being a huge pain inside
> the alpha code either because of the horrible hoops that the IO
> accessors have to jump through, or because of the broken ASID's.
>
> So even with enw compiler support, maybe it's worth trying to
> re-introduce any support for older cpu's incrementally.
Ack.
> For example, the ASID hw issue is _claimed_ to have been fixed in
> PALcode, and maybe the games we played for ev4-era cpus aren't
> actually needed any more?
Actually my system seems to be an odd relic that has very old PALcode:
[...]
X3.7-10895, built on Sep 15 1994 at 10:19:05
>>>sh conf
SRM Console X3.7-10895 VMS PALcode X5.48-60, OSF PALcode X1.35-42
[...]
-- which is dated well before the system's release date. It has been
heavily patched with extra components retrofitted on the PCB as if an
early hardware revision and the part number labelled on the PCB it's an
AlphaStation 250 and yet it came packaged as AlphaServer 300 (the only
documented difference between the PCBs of the two systems is the maximum
amount of DRAM supported), with a vast mismatch between the dates given on
the PCB and the case. I don't know what's the story behind it, maybe it
once was a DEC engineering machine.
And for instance its SRM cannot netboot over BOOTP/TFTP, it can only
use MOP. Not an issue for me, and I feel a bit uneasy about upgrading the
firmware, I'd rather I didn't brick the machine. I guess we shall see
whether it matters and if so, then what can be done about it.
I used an AlphaServer 300 before that was purchased brand new and I can't
recall any such patching on the PCB, and I reckon SRM was more modern too.
Indeed having checked old logs I found:
[...]
version X6.2-165 Nov 4 1996 10:06:10
>>>sh conf
Firmware
SRM Console: X6.2-165
ARC Console: 4.49
PALcode: VMS PALcode V5.56-2, OSF PALcode X1.46-2
[...]
> And the various odd IO platforms should only be re-introduced when
> there are people who actually have access to the relevant hardware and
> will test.
Absolutely, what's the point of keeping something we have no way to
verify? I'll begin with what I'm interested in myself and will gather
input from people willing to verify stuff with other hardware they may
have.
Anyway, it's been a hectic month for me and I have my Alpha machine in
the remote lab fully ready for this effort now, with a number of issues
fixed, most importantly rather tricky GCC PR rtl-optimization/115565,
<https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115565> which prevented the
userland from being used as installed.
With that in place the system was able to complete GCC 15 verification,
so now it should be able to do pretty much anything. I ran some glibc
upstream master testing too.
With that ticked off I do hope to work on the GCC part throughout July,
and then the kernel bits will follow.
Maciej
next prev parent reply other threads:[~2024-07-01 23:48 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 8:11 [PATCH 00/14] alpha: cleanups for 6.10 Arnd Bergmann
2024-05-03 8:11 ` [PATCH 01/14] alpha: sort scr_mem{cpy,move}w() out Arnd Bergmann
2024-05-03 8:11 ` [PATCH 02/14] alpha: fix modversions for strcpy() et.al Arnd Bergmann
2024-05-03 8:11 ` [PATCH 03/14] alpha: add clone3() support Arnd Bergmann
2024-05-03 8:11 ` [PATCH 04/14] alpha: don't make functions public without a reason Arnd Bergmann
2024-05-03 8:11 ` [PATCH 05/14] alpha: sys_sio: fix misspelled ifdefs Arnd Bergmann
2024-05-03 8:11 ` [PATCH 06/14] alpha: missing includes Arnd Bergmann
2024-05-03 8:11 ` [PATCH 07/14] alpha: core_lca: take the unused functions out Arnd Bergmann
2024-05-03 8:11 ` [PATCH 08/14] alpha: jensen, t2 - make __EXTERN_INLINE same as for the rest Arnd Bergmann
2024-05-03 8:11 ` [PATCH 09/14] alpha: trim the unused stuff from asm-offsets.c Arnd Bergmann
2024-05-03 8:11 ` [PATCH 10/14] alpha: remove DECpc AXP150 (Jensen) support Arnd Bergmann
2024-05-03 16:07 ` Linus Torvalds
2024-05-03 17:00 ` Al Viro
2024-05-03 20:07 ` Arnd Bergmann
2024-05-03 8:11 ` [PATCH 11/14] alpha: sable: remove early machine support Arnd Bergmann
2024-05-03 8:11 ` [PATCH 12/14] alpha: remove LCA and APECS based machines Arnd Bergmann
2024-05-03 8:11 ` [PATCH 13/14] alpha: cabriolet: remove EV5 CPU support Arnd Bergmann
2024-05-03 8:11 ` [PATCH 14/14] alpha: drop pre-EV56 support Arnd Bergmann
2024-05-04 15:00 ` Richard Henderson
2024-05-06 10:06 ` Arnd Bergmann
2024-06-03 6:02 ` Jiri Slaby
2024-06-04 13:58 ` Greg KH
2024-05-03 16:06 ` [PATCH 00/14] alpha: cleanups for 6.10 Matt Turner
2024-05-03 20:15 ` Arnd Bergmann
2024-05-06 9:16 ` Michael Cree
2024-05-06 10:11 ` Arnd Bergmann
2024-05-03 16:53 ` John Paul Adrian Glaubitz
2024-05-03 17:19 ` Paul E. McKenney
2024-05-27 23:49 ` Maciej W. Rozycki
2024-05-28 14:43 ` Paul E. McKenney
2024-05-29 18:50 ` Maciej W. Rozycki
2024-05-29 22:09 ` Paul E. McKenney
2024-05-30 22:59 ` Maciej W. Rozycki
2024-05-31 3:56 ` Maciej W. Rozycki
2024-05-31 19:33 ` Paul E. McKenney
2024-06-03 16:22 ` Maciej W. Rozycki
2024-06-03 17:08 ` Paul E. McKenney
2024-07-01 23:50 ` Maciej W. Rozycki
2024-05-30 1:08 ` Linus Torvalds
2024-05-30 22:57 ` Maciej W. Rozycki
2024-05-31 0:10 ` Linus Torvalds
2024-06-03 11:09 ` Maciej W. Rozycki
2024-06-03 11:36 ` John Paul Adrian Glaubitz
2024-06-03 16:57 ` Linus Torvalds
2024-07-01 23:48 ` Maciej W. Rozycki [this message]
2024-05-31 15:48 ` Arnd Bergmann
2024-05-31 16:32 ` Linus Torvalds
2024-05-31 16:54 ` Arnd Bergmann
2024-06-01 13:51 ` David Laight
2024-07-01 23:48 ` Maciej W. Rozycki
2024-07-02 1:13 ` Linus Torvalds
2024-07-03 0:12 ` Maciej W. Rozycki
2024-07-03 0:50 ` Linus Torvalds
2024-07-04 22:21 ` Maciej W. Rozycki
2024-06-03 11:33 ` Maciej W. Rozycki
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=alpine.DEB.2.21.2406302009050.43454@angie.orcam.me.uk \
--to=macro@orcam.me.uk \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=frank.scheiner@web.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=maz@kernel.org \
--cc=mcree@orcon.net.nz \
--cc=paulmck@kernel.org \
--cc=richard.henderson@linaro.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).