On Mon, 16 Jan 2023 at 10:33, John Paul Adrian Glaubitz <glaubitz@xxxxxxxxxxxxxxxxxxx> wrote: > > Hi Ard! > > On 1/14/23 00:25, Ard Biesheuvel wrote: > > Thanks for reporting back. I (mis)read the debian ports page [3], > > which mentions Debian 7 as the highest Debian version that supports > > IA64, and so I assumed that support had been dropped from Debian. > > This page talks about officially supported ports. Debian Ports is an > unofficial spin maintained by a number of Debian Developers and external > developers that are volunteering to maintain these ports. > > > However, if only a handful of people want to keep this port alive for > > reasons of nostalgia, it is obviously obsolete, and we should ask > > ourselves whether it is reasonable to expect Linux contributors to > > keep spending time on this. > > You could say this about a lot of hardware, can't you? > Uhm, yes. Linux contributor effort is a scarce resource, and spending it on architectures that nobody actually uses, such as alpha or ia64, means it is not spent on things that are useful to more people. I really do sympathize with the enthusiast/hobbyist PoV - I am also an engineer that likes to tinker. So 'use' can be defined liberally here, and cover running the latest Linux on ancient hardware just for entertainment. However, the question is not how you or I choose to spend (or waste) their time. The question is whether it is reasonable *as a community* to insist that everyone who contributes a cross-architecture change also has to ensure that obsolete architectures such as i64 or alpha are not left behind. The original thread is an interesting example here - removing a cpu_relax() in cmpxchg() that was only there because of IA64's clunky SMT implementation. Perhaps this means that IA64 performance is going to regress substantially for some workloads? Should anyone care? Should we test such changes first? And how should we do that if there is no maintainer and nobody has access to the hardware? The other example is EFI, which i maintain. Should I require from contributors that they build and boot test EFI changes on ia64 if I myself don't even have access to the hardware? It is good to know that things don't seem to be broken today, but if it is going to fall over, it may take a while before anybody notices. What happens then? > > Does the Debian ia64 port have any users? Or is the system that builds > > the packages the only one that consumes them? > > There is the popcon statistics. However, that is opt-on and the numbers are > not really trustworthy. We are getting feedback from time to time from people > using it. > > Is there any problem with the ia64 port at the moment that would justify removal? > I would argue that we should mark it obsolete at the very least, so that it is crystal clear that regressing IA64 (either knowingly or unknowingly) by a generic or cross-architecture change is not a showstopper, even at build time. Then, if someone has the skill set and the time on their hands, as well as access to actual hardware, they can keep it alive if they want to.
