From: Sedat Dilek <sedat.dilek@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
"Luck, Tony" <tony.luck@intel.com>,
"Torvalds, Linus" <torvalds@linux-foundation.org>,
Mateusz Guzik <mjguzik@gmail.com>,
linux-arch <linux-arch@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
Jan Glauber <jan.glauber@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: ia64 removal (was: Re: lockref scalability on x86-64 vs cpu_relax)
Date: Sat, 14 Jan 2023 12:24:13 +0100 [thread overview]
Message-ID: <CA+icZUXEz7ZxmkV5bw5O2ORjF4bwDXBMyj3Wk_HST98gMPt97g@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXEtTuaNFiKWn3cJngR0J2vr0G07HR6+5PBodtr1b7vNxg@mail.gmail.com>
On Sat, Jan 14, 2023 at 12:43 AM Ard Biesheuvel <ardb@kernel.org> wrote:
>
> On Fri, 13 Jan 2023 at 22:06, John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> >
> > Hello Ard!
> >
> > > Can I take that as an ack on [0]? The EFI subsystem has evolved
> > > substantially over the years, and there is really no way to do any
> > > IA64 testing beyond build testing, so from that perspective, dropping
> > > it entirely would be welcomed.
> >
> > ia64 is regularly tested in Debian and Gentoo [1][2].
> >
> > Debian's ia64 porterbox yttrium runs a recent kernel without issues:
> >
> > root@yttrium:~# uname -a
> > Linux yttrium 5.19.0-2-mckinley #1 SMP Debian 5.19.11-1 (2022-09-24) ia64 GNU/Linux
> > root@yttrium:~#
> >
> > root@yttrium:~# journalctl -b|head -n10
> > Nov 14 14:46:10 yttrium kernel: Linux version 5.19.0-2-mckinley (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP Debian 5.19.11-1 (2022-09-24)
> > Nov 14 14:46:10 yttrium kernel: efi: EFI v2.10 by HP
> > Nov 14 14:46:10 yttrium kernel: efi: SALsystab=0xdfdd63a18 ESI=0xdfdd63f18 ACPI 2.0=0x3d3c4014 HCDP=0xdffff8798 SMBIOS=0x3d368000
> > Nov 14 14:46:10 yttrium kernel: PCDP: v3 at 0xdffff8798
> > Nov 14 14:46:10 yttrium kernel: earlycon: uart8250 at I/O port 0x4000 (options '115200n8')
> > Nov 14 14:46:10 yttrium kernel: printk: bootconsole [uart8250] enabled
> > Nov 14 14:46:10 yttrium kernel: ACPI: Early table checksum verification disabled
> > Nov 14 14:46:10 yttrium kernel: ACPI: RSDP 0x000000003D3C4014 000024 (v02 HP )
> > Nov 14 14:46:10 yttrium kernel: ACPI: XSDT 0x000000003D3C4580 000124 (v01 HP RX2800-2 00000001 01000013)
> > Nov 14 14:46:10 yttrium kernel: ACPI: FACP 0x000000003D3BE000 0000F4 (v03 HP RX2800-2 00000001 HP 00000001)
> > root@yttrium:~#
> >
> > Same applies to the buildds:
> >
> > root@lifshitz:~# uname -a
> > Linux lifshitz 6.0.0-4-mckinley #1 SMP Debian 6.0.8-1 (2022-11-11) ia64 GNU/Linux
> > root@lifshitz:~#
> >
> > root@lenz:~# uname -a
> > Linux lenz 6.0.0-4-mckinley #1 SMP Debian 6.0.8-1 (2022-11-11) ia64 GNU/Linux
> > root@lenz:~#
> >
> > EFI works fine as well using the latest version of GRUB2.
> >
> > Thanks,
> > Adrian
> >
> > > [1] https://cdimage.debian.org/cdimage/ports/snapshots/
> > > [2] https://mirror.yandex.ru/gentoo-distfiles//releases/ia64/autobuilds/
>
> 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.
>
> 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.
>
> Does the Debian ia64 port have any users? Or is the system that builds
> the packages the only one that consumes them?
>
>
> [3] https://www.debian.org/ports/ia64/
I have no IA64 hardware or be a user of it or have any strong feelings
to keep this arch in the Linux-kernel.
But I am a Debianist (Debian/unstable AMD64 user).
Best is to ask the Debian release-team or (if there exist) maintainers
or responsibles for the IA64 port - which is an ***unofficial*** port.
What I found... on <cdimage.debian.org>:
https://cdimage.debian.org/cdimage/ > Ports
https://cdimage.debian.org/cdimage/ports/current/
https://cdimage.debian.org/cdimage/ports/current-debian-installer/ia64/debian-installer-images_20211020_ia64.tar.gz
^^ Last modified: 2021-10-20 22:52
https://cdimage.debian.org/cdimage/ports/current/debian-11.0.0-ia64-NETINST-1.iso
^^ Last modofied: 2022-03-28 14:18
With a net-install image you should be able to setup and explore the
IA64 Debian cosmos.
Example #1: binutils packages
Checking available binutils package for Debian/unstable IA64 (version:
2.39.90.20230110-1):
https://packages.debian.org/sid/binutils <--- Clearly states IA64 as
"unofficial port"
https://packages.debian.org/sid/ia64/binutils/filelist
Example #2: linux-image packages
Cannot say what this means...
https://packages.debian.org/search?arch=amd64&keywords=linux-image
(AMD64 - matches)
https://packages.debian.org/search?arch=ia64&keywords=linux-image
(IA64 - no matches)
https://packages.debian.org/search?arch=ia64&keywords=linux (IA64 -
matches - but no linux-image which ships normally a bootable
Linux-kernel)
As stated I have no expertise in Debian whatever release for IA64 arch.
Hope that helps.
-Sedat-
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-14 11:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGudoHHx0Nqg6DE70zAVA75eV-HXfWyhVMWZ-aSeOofkA_=WdA@mail.gmail.com>
2023-01-13 0:13 ` lockref scalability on x86-64 vs cpu_relax Linus Torvalds
2023-01-13 0:30 ` Luck, Tony
2023-01-13 0:45 ` Linus Torvalds
2023-01-13 7:55 ` ia64 removal (was: Re: lockref scalability on x86-64 vs cpu_relax) Ard Biesheuvel
2023-01-13 16:17 ` Luck, Tony
2023-01-13 20:49 ` Jessica Clarke
2023-01-13 21:03 ` Luck, Tony
2023-01-13 21:04 ` Jessica Clarke
2023-01-13 21:05 ` John Paul Adrian Glaubitz
2023-01-13 23:25 ` Ard Biesheuvel
2023-01-14 11:24 ` Sedat Dilek [this message]
2023-01-14 11:28 ` Sedat Dilek
2023-01-15 0:27 ` Matthew Wilcox
2023-01-15 12:04 ` Sedat Dilek
2023-01-16 9:42 ` John Paul Adrian Glaubitz
2023-01-16 9:41 ` John Paul Adrian Glaubitz
2023-01-16 13:28 ` Matthew Wilcox
2023-01-16 9:40 ` John Paul Adrian Glaubitz
2023-01-16 9:37 ` John Paul Adrian Glaubitz
2023-01-16 9:32 ` John Paul Adrian Glaubitz
2023-01-16 10:09 ` Ard Biesheuvel
2023-01-13 1:12 ` lockref scalability on x86-64 vs cpu_relax Mateusz Guzik
2023-01-13 4:08 ` Linus Torvalds
2023-01-13 9:46 ` Will Deacon
2023-01-13 3:20 ` Nicholas Piggin
2023-01-13 4:15 ` Linus Torvalds
2023-01-13 5:36 ` Nicholas Piggin
[not found] ` <1966767.1673878095@warthog.procyon.org.uk>
2023-01-16 15:09 ` Memory transaction instructions Matthew Wilcox
2023-01-16 16:59 ` Linus Torvalds
2023-01-18 9:05 ` David Howells
2023-01-19 1:41 ` Nicholas Piggin
2023-01-13 10:23 ` lockref scalability on x86-64 vs cpu_relax Peter Zijlstra
2023-01-13 18:44 ` [PATCH] lockref: stop doing cpu_relax in the cmpxchg loop Mateusz Guzik
2023-01-13 21:47 ` Luck, Tony
2023-01-13 23:31 ` Linus Torvalds
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=CA+icZUXEz7ZxmkV5bw5O2ORjF4bwDXBMyj3Wk_HST98gMPt97g@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jan.glauber@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mjguzik@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=will@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).