From: Petr Vorel <pvorel@suse.cz>
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] clone10: add support archs
Date: Thu, 22 Jan 2026 13:31:54 +0100 [thread overview]
Message-ID: <20260122123154.GC64562@pevik> (raw)
In-Reply-To: <CAASaF6w3S2STiyS9LvOsK_uVEvRoO6uq=XNMG-cMNheC0k1RHg@mail.gmail.com>
Hi Li, Jan,
> On Thu, Jan 22, 2026 at 11:26 AM Li Wang via ltp <ltp@lists.linux.it> wrote:
> > Signed-off-by: Li Wang <liwang@redhat.com>
> > ---
> > testcases/kernel/syscalls/clone/clone10.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> > diff --git a/testcases/kernel/syscalls/clone/clone10.c b/testcases/kernel/syscalls/clone/clone10.c
> > index a52ac3568..9ffb49c37 100644
> > --- a/testcases/kernel/syscalls/clone/clone10.c
> > +++ b/testcases/kernel/syscalls/clone/clone10.c
> > @@ -91,4 +91,10 @@ static struct tst_test test = {
> > .cleanup = cleanup,
> > .needs_checkpoints = 1,
> > .test_all = verify_tls,
> > + .supported_archs = (const char *const []) {
> > + "x86_64",
> > + "aarch64",
> > + "s390x",
> > + NULL
> > + }
> > };
> Acked-by: Jan Stancek <jstancek@redhat.com>
LGTM. Indeed only these 3 archs don't TCONF.
Acked-by: Petr Vorel <pvorel@suse.cz>
Out of curiosity, where is the support defined in kernel?
"if (clone_flags & CLONE_SETTLS)" is in many archs:
$ git grep CLONE_SETTLS
...
arch/loongarch/kernel/process.c:220: if (clone_flags & CLONE_SETTLS)
arch/m68k/kernel/process.c:179: if (clone_flags & CLONE_SETTLS)
arch/microblaze/kernel/process.c:110: if (clone_flags & CLONE_SETTLS)
arch/mips/kernel/process.c:171: if (clone_flags & CLONE_SETTLS)
arch/nios2/kernel/process.c:143: if (clone_flags & CLONE_SETTLS)
arch/openrisc/kernel/process.c:199: * For CLONE_SETTLS set "tp" (r10) to the TLS pointer.
arch/openrisc/kernel/process.c:201: if (clone_flags & CLONE_SETTLS)
arch/parisc/kernel/process.c:251: if (clone_flags & CLONE_SETTLS)
arch/powerpc/kernel/process.c:1819: if (clone_flags & CLONE_SETTLS) {
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-01-22 12:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:26 [LTP] [PATCH] clone10: add support archs Li Wang via ltp
2026-01-22 10:41 ` Jan Stancek via ltp
2026-01-22 12:28 ` Wei Gao via ltp
2026-01-22 12:31 ` Petr Vorel [this message]
2026-01-22 12:47 ` Li Wang via ltp
2026-01-22 13:06 ` Petr Vorel
2026-01-22 14:16 ` Li Wang via ltp
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=20260122123154.GC64562@pevik \
--to=pvorel@suse.cz \
--cc=jstancek@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.