From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
"Dominik Karol Piątkowski" <dominik.karol.piatkowski@intel.com>,
igt-dev@lists.freedesktop.org,
"Isabella Basso" <isabbasso@riseup.net>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t v2 04/17] lib/kunit: Optimize calls to igt_success/skip/fail()
Date: Mon, 11 Sep 2023 10:49:36 +0200 [thread overview]
Message-ID: <20230911104936.435fa279@maurocar-mobl2> (raw)
In-Reply-To: <20230908123233.137134-23-janusz.krzysztofik@linux.intel.com>
On Fri, 8 Sep 2023 14:32:38 +0200
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> wrote:
> Calling igt_success() explicitly at the end of subtest body is not needed.
> Other calls to igt_success() can be usually avoided by inverting test
> result checks. Optimize the code that now calls igt_success().
>
> Moreover, using more advanced variants of igt_skip() and igt_fail() where
> applicable makes the code more compact. Go for it.
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
> ---
> lib/igt_kmod.c | 14 +++-----------
> 1 file changed, 3 insertions(+), 11 deletions(-)
>
> diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c
> index 34ddec3fad..1d1cd51170 100644
> --- a/lib/igt_kmod.c
> +++ b/lib/igt_kmod.c
> @@ -814,12 +814,8 @@ static void __igt_kunit(const char *module_name, const char *opts)
> if (READ_ONCE(results->head) != NULL) {
> pthread_mutex_lock(&results->mutex);
>
> - igt_dynamic(results->head->test_name) {
> - if (READ_ONCE(results->head->passed))
> - igt_success();
> - else
> - igt_fail(IGT_EXIT_FAILURE);
> - }
> + igt_dynamic(results->head->test_name)
> + igt_assert(READ_ONCE(results->head->passed));
>
> temp = results->head;
> results->head = results->head->next;
> @@ -834,8 +830,7 @@ unload:
>
> igt_ktest_fini(&tst);
>
> - if (skip)
> - igt_skip("Skipping test, as probing KUnit module returned %d", skip);
> + igt_skip_on_f(skip, "Skipping test, as probing KUnit module failed\n");
>
> if (fail)
> igt_fail(IGT_EXIT_ABORT);
> @@ -844,9 +839,6 @@ unload:
>
> if (ret != 0)
> igt_fail(IGT_EXIT_ABORT);
> -
> - if (ret == 0)
> - igt_success();
> }
>
> void igt_kunit(const char *module_name, const char *name, const char *opts)
next prev parent reply other threads:[~2023-09-11 8:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 12:32 [Intel-gfx] [PATCH i-g-t v2 00/17] Fix IGT Kunit implementation issues Janusz Krzysztofik
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 01/17] lib/kunit: Drop unused file stream Janusz Krzysztofik
2023-09-15 10:36 ` [Intel-gfx] [igt-dev] " Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 02/17] lib/kunit: Stop loading kunit module explicitly Janusz Krzysztofik
2023-09-15 10:36 ` [Intel-gfx] [igt-dev] " Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 03/17] lib/kunit: Fix struct kmod_module kunit_kmod not freed Janusz Krzysztofik
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 04/17] lib/kunit: Optimize calls to igt_success/skip/fail() Janusz Krzysztofik
2023-09-11 8:49 ` Mauro Carvalho Chehab [this message]
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 05/17] lib/kunit: Fix illegal igt_fail() calls inside subtest body Janusz Krzysztofik
2023-09-11 8:52 ` Mauro Carvalho Chehab
2023-09-11 9:28 ` Janusz Krzysztofik
2023-09-11 11:57 ` Mauro Carvalho Chehab
2023-09-13 13:03 ` Janusz Krzysztofik
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 06/17] lib/ktap: Make sure we fail on premature cancel Janusz Krzysztofik
2023-09-11 8:55 ` Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 07/17] lib/ktap: Don't ignore interrupt signals Janusz Krzysztofik
2023-09-11 9:01 ` Mauro Carvalho Chehab
2023-09-13 14:04 ` Janusz Krzysztofik
2023-09-15 12:25 ` Mauro Carvalho Chehab
2023-09-15 13:06 ` Janusz Krzysztofik
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 08/17] lib/kunit: Cancel KTP parser on module load failure Janusz Krzysztofik
2023-09-11 9:02 ` Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 09/17] lib/ktap: Drop is_running flag Janusz Krzysztofik
2023-09-11 9:03 ` Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 10/17] lib/ktap: Read /dev/kmsg in blocking mode Janusz Krzysztofik
2023-09-15 10:42 ` Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 11/17] lib/kunit: Fail / skip on kernel taint Janusz Krzysztofik
2023-09-15 10:43 ` Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 12/17] lib/ktap: Use IGT linked lists for storing KTAP results Janusz Krzysztofik
2023-09-15 10:44 ` Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 13/17] lib/ktap: Reimplement KTAP parser Janusz Krzysztofik
2023-09-15 11:45 ` [Intel-gfx] [igt-dev] " Mauro Carvalho Chehab
2023-09-15 12:28 ` [Intel-gfx] " Mauro Carvalho Chehab
2023-09-15 13:09 ` Janusz Krzysztofik
2023-09-15 13:35 ` Janusz Krzysztofik
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 14/17] lib/kunit: Load test modules in background Janusz Krzysztofik
2023-09-15 12:11 ` [Intel-gfx] [igt-dev] " Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 15/17] lib/kunit: Parse KTAP report from the main process thread Janusz Krzysztofik
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 16/17] lib/kunit: Strip "_test" or "_kunit" suffix from subtest names Janusz Krzysztofik
2023-09-15 11:42 ` [Intel-gfx] [igt-dev] " Mauro Carvalho Chehab
2023-09-08 12:32 ` [Intel-gfx] [PATCH i-g-t v2 17/17] lib/kunit: Omit suite name prefix if the same as subtest name Janusz Krzysztofik
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=20230911104936.435fa279@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=dominik.karol.piatkowski@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=isabbasso@riseup.net \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=mchehab@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