From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v9 1/6] selftests/resctrl: Fix set up schemata with 100% allocation on first run in MBM test
Date: Fri, 14 Apr 2023 15:31:55 +0300 (EEST) [thread overview]
Message-ID: <bb65cce8-54d7-68c5-ef19-3364ec95392a@linux.intel.com> (raw)
In-Reply-To: <20230413072259.2089348-2-tan.shaopeng@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 3831 bytes --]
On Thu, 13 Apr 2023, Shaopeng Tan wrote:
> There is a comment "Set up shemata with 100% allocation on the first run"
s/shemata/schemata/
> in function mbm_setup(), but there is an increment bug and the condition
> "num_of_runs == 0" will never be met and write_schemata() will never be
> called to set schemata to 100%. Even if write_schemata() is called in MBM
> test, since it is not supported for MBM test it does not set the schemata.
> This is currently fine because resctrl_val_parm->mum_resctrlfs is always 1
> and umount/mount will be run in each test to set the schemata to 100%.
>
> To support the usage when MBM test does not unmount/remount resctrl
> filesystem before the test starts, fix to call write_schemata() and
> set schemata properly when the function is called for the first time.
>
> Also, remove static local variable 'num_of_runs' because this is not
> needed as there is resctrl_val_param->num_of_runs which should be used
> instead like in cat_setup().
>
> Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
> Signed-off-by: Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
> ---
> tools/testing/selftests/resctrl/mbm_test.c | 13 +++++++------
> tools/testing/selftests/resctrl/resctrlfs.c | 4 +++-
> 2 files changed, 10 insertions(+), 7 deletions(-)
>
> diff --git a/tools/testing/selftests/resctrl/mbm_test.c b/tools/testing/selftests/resctrl/mbm_test.c
> index c9dfa54af42f..9b591c35310f 100644
> --- a/tools/testing/selftests/resctrl/mbm_test.c
> +++ b/tools/testing/selftests/resctrl/mbm_test.c
> @@ -89,23 +89,24 @@ static int check_results(int span)
> static int mbm_setup(int num, ...)
> {
> struct resctrl_val_param *p;
> - static int num_of_runs;
> va_list param;
> int ret = 0;
>
> - /* Run NUM_OF_RUNS times */
> - if (num_of_runs++ >= NUM_OF_RUNS)
> - return END_OF_TESTS;
> -
> va_start(param, num);
> p = va_arg(param, struct resctrl_val_param *);
> va_end(param);
>
> + /* Run NUM_OF_RUNS times */
> + if (p->num_of_runs >= NUM_OF_RUNS)
> + return -1;
This is not rebased correctly, negative return values mean now errors.
To complete tests "normally", return END_OF_TESTS. Please see commit
fa10366cc6f4 ("selftests/resctrl: Allow ->setup() to return errors") for
future information.
With the forementioned problems fixed:
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
> +
> /* Set up shemata with 100% allocation on the first run. */
> - if (num_of_runs == 0)
> + if (p->num_of_runs == 0)
> ret = write_schemata(p->ctrlgrp, "100", p->cpu_no,
> p->resctrl_val);
>
> + p->num_of_runs++;
> +
> return ret;
> }
>
> diff --git a/tools/testing/selftests/resctrl/resctrlfs.c b/tools/testing/selftests/resctrl/resctrlfs.c
> index cc6cf49e3129..b31b1d9e41d1 100644
> --- a/tools/testing/selftests/resctrl/resctrlfs.c
> +++ b/tools/testing/selftests/resctrl/resctrlfs.c
> @@ -498,6 +498,7 @@ int write_schemata(char *ctrlgrp, char *schemata, int cpu_no, char *resctrl_val)
> FILE *fp;
>
> if (strncmp(resctrl_val, MBA_STR, sizeof(MBA_STR)) &&
> + strncmp(resctrl_val, MBM_STR, sizeof(MBM_STR)) &&
> strncmp(resctrl_val, CAT_STR, sizeof(CAT_STR)) &&
> strncmp(resctrl_val, CMT_STR, sizeof(CMT_STR)))
> return -ENOENT;
> @@ -523,7 +524,8 @@ int write_schemata(char *ctrlgrp, char *schemata, int cpu_no, char *resctrl_val)
> if (!strncmp(resctrl_val, CAT_STR, sizeof(CAT_STR)) ||
> !strncmp(resctrl_val, CMT_STR, sizeof(CMT_STR)))
> sprintf(schema, "%s%d%c%s", "L3:", resource_id, '=', schemata);
> - if (!strncmp(resctrl_val, MBA_STR, sizeof(MBA_STR)))
> + if (!strncmp(resctrl_val, MBA_STR, sizeof(MBA_STR)) ||
> + !strncmp(resctrl_val, MBM_STR, sizeof(MBM_STR)))
> sprintf(schema, "%s%d%c%s", "MB:", resource_id, '=', schemata);
>
> fp = fopen(controlgroup, "w");
>
next prev parent reply other threads:[~2023-04-14 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 7:22 [PATCH v9 0/6] Some improvements of resctrl selftest Shaopeng Tan
2023-04-13 7:22 ` [PATCH v9 1/6] selftests/resctrl: Fix set up schemata with 100% allocation on first run in MBM test Shaopeng Tan
2023-04-14 12:31 ` Ilpo Järvinen [this message]
2023-04-14 15:24 ` Reinette Chatre
2023-04-13 7:22 ` [PATCH v9 2/6] selftests/resctrl: Return MBA check result and make it to output message Shaopeng Tan
2023-04-13 7:22 ` [PATCH v9 3/6] selftests/resctrl: Flush stdout file buffer before executing fork() Shaopeng Tan
2023-04-13 7:22 ` [PATCH v9 4/6] selftests/resctrl: Cleanup properly when an error occurs in CAT test Shaopeng Tan
2023-04-13 7:22 ` [PATCH v9 5/6] selftests/resctrl: Commonize the signal handler register/unregister for all tests Shaopeng Tan
2023-04-13 7:22 ` [PATCH v9 6/6] selftests/resctrl: Remove duplicate codes that clear each test result file Shaopeng Tan
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=bb65cce8-54d7-68c5-ef19-3364ec95392a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shuah@kernel.org \
--cc=tan.shaopeng@jp.fujitsu.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