Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Helge Deller <deller@gmx.de>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] Cleanup IA-64 related code?
Date: Tue, 9 Jan 2024 18:20:16 +0100	[thread overview]
Message-ID: <20240109172016.GB1661159@pevik> (raw)
In-Reply-To: <3b638b9e-6269-459d-bcc8-2bad7b538de1@gmx.de>

Hi Helge, Li,

> On 11/20/23 09:11, Li Wang wrote:
> > Hi all,

> > I noticed that the mainline kernel is declaring to dropp support for
> > Itanium IA-64, actually, the commit[1] has been merged in v6.7-rc2.

> > I am now thinking should we do the same action for LTP in the
> > main branch to keep consistent with the mainline kernel?

> Upstream kernel dropped IA-64 for future releases, but it's still being
> used the next few years with existing kernels, machines and distributions,
> so I suggest to not *pro-actively* dropping existing code yet.
> E.g. it's still supported on debian until end of the current debian releases.

> Just my 2c.

I would keep it at least in this upcoming release. I also wonder if anybody
tests IA-64 with new LTP, i.e. how long we should keep it in LTP before
removing.

BTW I removed some IA-64 some years ago during some test rewrite (too long ago
now to search for it). At the time I was not aware that anybody would test IA-64
with LTP.

Kind regards,
Petr

> Helge


> > [1]
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf8e8658100d4eae80ce9b21f7a81cb024dd5057

> > [liwang@liwang-workstation ltp]$$ git grep __ia64__
> > include/lapi/rt_sigaction.h:#if !defined(__ia64__) && !defined(__alpha__)
> > && !defined(__hppa__) && !defined(__mips__)
> > lib/cloner.c:#if defined(__ia64__)
> > lib/cloner.c: *   2. __ia64__ takes bottom of stack and uses clone2
> > lib/cloner.c:#if defined(__ia64__)
> > lib/tst_arch.c:#elif defined(__ia64__)
> > testcases/kernel/mem/hugetlb/hugemmap/hugemmap05.c:#ifdef __ia64__
> > testcases/kernel/mem/hugetlb/hugemmap/hugemmap07.c:#elif defined(__ia64__)
> > testcases/kernel/mem/hugetlb/hugemmap/hugemmap15.c:#if defined(__powerpc__)
> > || defined(__powerpc64__) || defined(__ia64__) || \
> > testcases/kernel/mem/hugetlb/hugemmap/hugemmap15.c:#if defined(__powerpc__)
> > || defined(__powerpc64__) || defined(__ia64__) || \
> > testcases/kernel/mem/shmt/shmt09.c:#ifdef __ia64__
> > testcases/kernel/mem/shmt/shmt09.c:#if defined (__ia64__) ||
> > defined(__mips__) || defined(__hppa__) || defined(__arm__) ||
> > defined(__aarch64__)
> > testcases/kernel/sched/cfs-scheduler/hackbench.c:#ifndef __ia64__
> > testcases/kernel/syscalls/mmap/mmap03.c:#if defined(__ia64__) ||
> > defined(__hppa__) || defined(__mips__)
> > testcases/kernel/syscalls/mmap/mmap15.c:#ifdef __ia64__
> > testcases/kernel/syscalls/ptrace/ptrace.h:#ifdef __ia64__ /* what a pos */
> > testcases/misc/crash/crash02.c:#if defined(__ia64__)
> > testcases/misc/crash/crash02.c:#endif /* __ia64__ */

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-09 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  8:11 [LTP] Cleanup IA-64 related code? Li Wang
2023-11-20 11:13 ` Helge Deller
2024-01-09 17:20   ` Petr Vorel [this message]
2024-01-10  2:16     ` Li Wang

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=20240109172016.GB1661159@pevik \
    --to=petr.vorel@gmail.com \
    --cc=deller@gmx.de \
    --cc=ltp@lists.linux.it \
    /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