From: Carsten Haitzler <carsten.haitzler@foss.arm.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: linux-kernel@vger.kernel.org, coresight@lists.linaro.org,
suzuki.poulose@arm.com, mathieu.poirier@linaro.org,
mike.leach@linaro.org, linux-perf-users@vger.kernel.org,
acme@kernel.org
Subject: Re: [PATCH v5 01/14] perf test: Refactor shell tests allowing subdirs
Date: Wed, 10 Aug 2022 09:38:45 +0100 [thread overview]
Message-ID: <7b3bdad2-906b-98ea-239f-e76703a0f7a4@foss.arm.com> (raw)
In-Reply-To: <20220806083712.GA124146@leoy-ThinkPad-X240s>
On 8/6/22 09:37, Leo Yan wrote:
> On Thu, Jul 28, 2022 at 03:52:43PM +0100, carsten.haitzler@foss.arm.com wrote:
>
> [...]
>
>> +int list_script_max_width(void)
>> +{
>> + list_script_files(); /* Ensure we have scanned all scriptd */
>
> s/scriptd/scripts/
oops. fixed. v6 will come with that.
>> + return files_max_width;
>> +}
>
> [...]
>
>> struct shell_test {
>> const char *dir;
>> const char *file;
>> @@ -385,33 +302,17 @@ static int shell_test__run(struct test_suite *test, int subdir __maybe_unused)
>> static int run_shell_tests(int argc, const char *argv[], int i, int width,
>> struct intlist *skiplist)
>> {
>> - struct dirent **entlist;
>> - struct dirent *ent;
>> - int n_dirs, e;
>> - char path_dir[PATH_MAX];
>> - struct shell_test st = {
>> - .dir = shell_tests__dir(path_dir, sizeof(path_dir)),
>> - };
>> -
>> - if (st.dir == NULL)
>> - return -1;
>> + struct shell_test st;
>> + const struct script_file *files, *file;
>>
>> - n_dirs = scandir(st.dir, &entlist, NULL, alphasort);
>> - if (n_dirs == -1) {
>> - pr_err("failed to open shell test directory: %s\n",
>> - st.dir);
>> - return -1;
>> - }
>> -
>> - for_each_shell_test(entlist, n_dirs, st.dir, ent) {
>> + files = list_script_files();
>> + if (!files)
>> + return 0;
>> + for (file = files; file->dir; file++) {
>> int curr = i++;
>> - char desc[256];
>> struct test_case test_cases[] = {
>> {
>> - .desc = shell_test__description(desc,
>> - sizeof(desc),
>> - st.dir,
>> - ent->d_name),
>> + .desc = file->desc,
>> .run_case = shell_test__run,
>> },
>> { .name = NULL, }
>> @@ -421,12 +322,13 @@ static int run_shell_tests(int argc, const char *argv[], int i, int width,
>> .test_cases = test_cases,
>> .priv = &st,
>> };
>> + st.dir = file->dir;
>>
>> if (test_suite.desc == NULL ||
>> !perf_test__matches(test_suite.desc, curr, argc, argv))
>> continue;
>>
>> - st.file = ent->d_name;
>> + st.file = file->file;
>
> I am just wandering if we can remove "st" in this function, finally I
> found you are right, the "st" (struct shell_test) will be used in the
> function shell_test__run(), so let's keep as it is.
>
>> pr_info("%3d: %-*s:", i, width, test_suite.desc);
>>
>> if (intlist__find(skiplist, i)) {
>> @@ -436,10 +338,6 @@ static int run_shell_tests(int argc, const char *argv[], int i, int width,
>>
>> test_and_print(&test_suite, 0);
>> }
>> -
>> - for (e = 0; e < n_dirs; e++)
>> - zfree(&entlist[e]);
>> - free(entlist);
>> return 0;
>> }
>>
>> @@ -448,7 +346,7 @@ static int __cmd_test(int argc, const char *argv[], struct intlist *skiplist)
>> struct test_suite *t;
>> unsigned int j, k;
>> int i = 0;
>> - int width = shell_tests__max_desc_width();
>> + int width = list_script_max_width();
>>
>> for_each_test(j, k, t) {
>> int len = strlen(test_description(t, -1));
>> @@ -529,36 +427,22 @@ static int __cmd_test(int argc, const char *argv[], struct intlist *skiplist)
>>
>> static int perf_test__list_shell(int argc, const char **argv, int i)
>> {
>> - struct dirent **entlist;
>> - struct dirent *ent;
>> - int n_dirs, e;
>> - char path_dir[PATH_MAX];
>> - const char *path = shell_tests__dir(path_dir, sizeof(path_dir));
>> -
>> - if (path == NULL)
>> - return -1;
>> + const struct script_file *files, *file;
>>
>> - n_dirs = scandir(path, &entlist, NULL, alphasort);
>> - if (n_dirs == -1)
>> - return -1;
>> -
>> - for_each_shell_test(entlist, n_dirs, path, ent) {
>> + files = list_script_files();
>> + if (!files)
>> + return 0;
>> + for (file = files; file->dir; file++) {
>> int curr = i++;
>> - char bf[256];
>> struct test_suite t = {
>> - .desc = shell_test__description(bf, sizeof(bf), path, ent->d_name),
>> + .desc = file->desc
>> };
>>
>> if (!perf_test__matches(t.desc, curr, argc, argv))
>> continue;
>>
>> pr_info("%3d: %s\n", i, t.desc);
>> -
>> }
>> -
>> - for (e = 0; e < n_dirs; e++)
>> - zfree(&entlist[e]);
>> - free(entlist);
>> return 0;
>> }
>
> Except a minor typo, the patch looks good to me, it's a good
> refactoring and enhancement for shell script testing.
>
> I reviewed the change one by one line, at least I cannot find any logic
> error.
>
> With typo fixing:
>
> Reviewed-by: Leo Yan <leo.yan@linaro.org>
>
> I'd leave this patch for maintainers to review it. Just a caveat, given
> it's a big patch, as Carsten replied it's good that take the patch as a
> total new code for searching shell scripts, this would be easier for
> understanding the change.
>
> Thanks,
> Leo
next prev parent reply other threads:[~2022-08-10 8:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 14:52 [PATCH v5 00/14] A patch series improving data quality of perf test for CoreSight carsten.haitzler
2022-07-28 14:52 ` [PATCH v5 01/14] perf test: Refactor shell tests allowing subdirs carsten.haitzler
2022-08-06 8:37 ` Leo Yan
2022-08-10 8:38 ` Carsten Haitzler [this message]
2022-07-28 14:52 ` [PATCH v5 02/14] perf test: Add CoreSight shell lib shared code for future tests carsten.haitzler
2022-08-06 9:40 ` Leo Yan
2022-08-10 8:40 ` Carsten Haitzler
2022-07-28 14:52 ` [PATCH v5 03/14] perf test: Add build infra for perf test tools for CoreSight tests carsten.haitzler
2022-08-07 3:59 ` Leo Yan
2022-08-10 17:37 ` Carsten Haitzler
2022-07-28 14:52 ` [PATCH v5 04/14] perf test: Add asm pureloop test tool carsten.haitzler
2022-08-07 4:03 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 05/14] perf test: Add asm pureloop test shell script carsten.haitzler
2022-08-07 4:35 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 06/14] perf test: Add git ignore for perf data generated by the CoreSight tests carsten.haitzler
2022-08-07 4:35 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 07/14] perf test: Add memcpy thread test tool carsten.haitzler
2022-08-07 4:49 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 08/14] perf test: Add memcpy thread test shell script carsten.haitzler
2022-08-07 4:12 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 09/14] perf test: Add thread loop test tool carsten.haitzler
2022-08-07 5:13 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 10/14] perf test: Add thread loop test shell scripts carsten.haitzler
2022-08-07 5:17 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 11/14] perf test: Add unroll thread test tool carsten.haitzler
2022-08-07 5:25 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 12/14] perf test: Add unroll thread test shell script carsten.haitzler
2022-08-07 5:44 ` Leo Yan
2022-08-10 17:55 ` Carsten Haitzler
2022-07-28 14:52 ` [PATCH v5 13/14] perf test: Add git ignore for tmp and output files of CoreSight tests carsten.haitzler
2022-08-07 5:48 ` Leo Yan
2022-07-28 14:52 ` [PATCH v5 14/14] perf test: Add relevant documentation about CoreSight testing carsten.haitzler
2022-08-07 7:03 ` Leo Yan
2022-08-10 17:59 ` Carsten Haitzler
2022-08-11 13:03 ` Mike Leach
2022-08-11 16:10 ` [PATCH v5 00/14] A patch series improving data quality of perf test for CoreSight Mike Leach
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=7b3bdad2-906b-98ea-239f-e76703a0f7a4@foss.arm.com \
--to=carsten.haitzler@foss.arm.com \
--cc=acme@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
/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).