From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Shuah Khan <shuah@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 3/3] selftests/resctrl: Move cleanups out of individual tests
Date: Tue, 20 Feb 2024 15:49:16 +0200 (EET) [thread overview]
Message-ID: <f08dafda-c8a5-324a-464c-5b84d779c4ad@linux.intel.com> (raw)
In-Reply-To: <63b9763211c2954f0ef517a817b3bf0c482df8cd.1708434017.git.maciej.wieczor-retman@intel.com>
On Tue, 20 Feb 2024, Maciej Wieczor-Retman wrote:
> Every test calls its cleanup function at the end of it's test function.
> After the cleanup function pointer is added to the test framework this
> can be simplified to executing the callback function at the end of the
> generic test running function.
>
> Make test cleanup functions static and call them from the end of
> run_single_test() from the resctrl_test's cleanup function pointer.
>
> Signed-off-by: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
> ---
> tools/testing/selftests/resctrl/cat_test.c | 4 +---
> tools/testing/selftests/resctrl/cmt_test.c | 3 +--
> tools/testing/selftests/resctrl/mba_test.c | 4 +---
> tools/testing/selftests/resctrl/mbm_test.c | 4 +---
> tools/testing/selftests/resctrl/resctrl.h | 4 ----
> tools/testing/selftests/resctrl/resctrl_tests.c | 2 ++
> 6 files changed, 6 insertions(+), 15 deletions(-)
>
> diff --git a/tools/testing/selftests/resctrl/cat_test.c b/tools/testing/selftests/resctrl/cat_test.c
> index 2d2f69d3e5b7..ad5ebce65c07 100644
> --- a/tools/testing/selftests/resctrl/cat_test.c
> +++ b/tools/testing/selftests/resctrl/cat_test.c
> @@ -128,7 +128,7 @@ static int check_results(struct resctrl_val_param *param, const char *cache_type
> return fail;
> }
>
> -void cat_test_cleanup(void)
> +static void cat_test_cleanup(void)
> {
> remove(RESULT_FILE_NAME);
> }
> @@ -289,8 +289,6 @@ static int cat_run_test(const struct resctrl_test *test, const struct user_param
> ret = check_results(¶m, test->resource,
> cache_total_size, full_cache_mask, start_mask);
> out:
> - cat_test_cleanup();
> -
Any goto out can now become return ret; and the out label be then removed.
--
i.
next prev parent reply other threads:[~2024-02-20 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 13:14 [PATCH 0/3] selftests/resctrl: Simplify test cleanup functions Maciej Wieczor-Retman
2024-02-20 13:14 ` [PATCH 1/3] selftests/resctrl: Add cleanup function to test framework Maciej Wieczor-Retman
2024-02-20 13:14 ` [PATCH 2/3] selftests/resctrl: Simplify cleanup in ctrl-c handler Maciej Wieczor-Retman
2024-02-20 13:45 ` Ilpo Järvinen
2024-02-20 14:08 ` Maciej Wieczor-Retman
2024-02-20 14:21 ` Ilpo Järvinen
2024-02-20 13:14 ` [PATCH 3/3] selftests/resctrl: Move cleanups out of individual tests Maciej Wieczor-Retman
2024-02-20 13:49 ` Ilpo Järvinen [this message]
2024-02-20 14:08 ` Maciej Wieczor-Retman
2024-02-20 13:18 ` [PATCH 0/3] selftests/resctrl: Simplify test cleanup functions Maciej Wieczor-Retman
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=f08dafda-c8a5-324a-464c-5b84d779c4ad@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=maciej.wieczor-retman@intel.com \
--cc=reinette.chatre@intel.com \
--cc=shuah@kernel.org \
/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