From: Cyril Hrubis <chrubis@suse.cz>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v5 1/3] lib: adding .supported_archs field in tst_test structure
Date: Thu, 18 Nov 2021 12:42:29 +0100 [thread overview]
Message-ID: <YZY8JQlE2EEVEIKX@yuki> (raw)
In-Reply-To: <87mtm2amkd.fsf@suse.de>
Hi!
> > These are not valid arch names AFAICT. There is no mapping from these to
> > x86 in the tst_arch table above.
> >
> > Perhaps we could replace them all with x86?
> >
> > Yes, that is also the unsure part I was concerned about in patch v4.
> > Because x86 is also an invalid arch (it is just a conventional name),
> > if we use it in the arch_type_list we have to recognize it as a valid arch
> > name in test case as well. I'm not sure that will be accepted by other
> > people.
>
> The folder in the kernel tree is arch/x86.
The x86 is basically a wildcard where the x could be substitued with any
of {3,4,5,6,7}. Also I think that 786 was last 32bit intel arch ever
released.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-11-18 11:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 7:07 [LTP] [PATCH v5 1/3] lib: adding .supported_archs field in tst_test structure Li Wang
2021-11-17 7:07 ` [LTP] [PATCH v5 2/3] testcase: make use of .supported_archs Li Wang
2021-11-17 7:07 ` [LTP] [PATCH v5 3/3] max_map_count: replace ifdefs by tst_arch Li Wang
2021-11-17 10:33 ` Richard Palethorpe
2021-11-17 13:28 ` Li Wang
2021-11-17 13:58 ` Richard Palethorpe
2021-11-17 9:58 ` [LTP] [PATCH v5 1/3] lib: adding .supported_archs field in tst_test structure Richard Palethorpe
2021-11-17 13:51 ` Li Wang
2021-11-17 14:01 ` Richard Palethorpe
2021-11-18 11:42 ` Cyril Hrubis [this message]
2021-11-17 13:59 ` Joerg Vehlow
2021-11-17 14:25 ` Richard Palethorpe
2021-11-18 5:50 ` Li Wang
2021-11-18 12:07 ` Cyril Hrubis
2021-11-22 2:21 ` Li Wang
2021-11-22 13:27 ` Richard Palethorpe
2021-11-22 14:21 ` Cyril Hrubis
2021-11-23 4:13 ` 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=YZY8JQlE2EEVEIKX@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.de \
/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