public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: Joey Gouly <joey.gouly@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kselftest@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v1 1/4] kselftest/arm64: Handle more kselftest result codes in MTE helpers
Date: Thu, 10 Mar 2022 12:40:40 -0700	[thread overview]
Message-ID: <dec7d25c-1cd4-1651-274f-19f2ff5c231c@linuxfoundation.org> (raw)
In-Reply-To: <20220310144335.2097457-2-broonie@kernel.org>

On 3/10/22 7:43 AM, Mark Brown wrote:
> The MTE selftests have a helper evaluate_test() which translates a return
> code into a call to ksft_test_result_*(). Currently this only handles pass
> and fail, silently ignoring any other code. Update the helper to support
> skipped tests and log any unknown return codes as an error so we get at
> least some diagnostic if anything goes wrong.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
>   .../testing/selftests/arm64/mte/mte_common_util.h | 15 +++++++++++++--
>   1 file changed, 13 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/arm64/mte/mte_common_util.h b/tools/testing/selftests/arm64/mte/mte_common_util.h
> index 195a7d1879e6..2d3e71724e55 100644
> --- a/tools/testing/selftests/arm64/mte/mte_common_util.h
> +++ b/tools/testing/selftests/arm64/mte/mte_common_util.h
> @@ -75,10 +75,21 @@ unsigned int mte_get_pstate_tco(void);
>   /* Test framework static inline functions/macros */
>   static inline void evaluate_test(int err, const char *msg)
>   {
> -	if (err == KSFT_PASS)
> +	switch (err) {
> +	case KSFT_PASS:
>   		ksft_test_result_pass(msg);
> -	else if (err == KSFT_FAIL)
> +		break;
> +	case KSFT_FAIL:
>   		ksft_test_result_fail(msg);
> +		break;
> +	case KSFT_SKIP:
> +		ksft_test_result_skip(msg);
> +		break;
> +	default:
> +		ksft_test_result_error("Unknown return code %d from %s",
> +				       err, msg);
> +		break;
> +	}
>   }
>   
>   static inline int check_allocated_memory(void *ptr, size_t size,
> 

Nice. Thank you for doing this.

Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>

thanks,
-- Shuah

  reply	other threads:[~2022-03-10 19:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 14:43 [PATCH v1 0/4] kselftest/arm64: Miscelaneous MTE test updates Mark Brown
2022-03-10 14:43 ` [PATCH v1 1/4] kselftest/arm64: Handle more kselftest result codes in MTE helpers Mark Brown
2022-03-10 19:40   ` Shuah Khan [this message]
2022-03-10 14:43 ` [PATCH v1 2/4] kselftest/arm64: Log unexpected asynchronous MTE faults Mark Brown
2022-03-10 20:04   ` Shuah Khan
2022-03-10 14:43 ` [PATCH v1 3/4] kselftest/arm64: Refactor parameter checking in mte_switch_mode() Mark Brown
2022-03-10 20:05   ` Shuah Khan
2022-03-10 14:43 ` [PATCH v1 4/4] kselftest/arm64: Add simple test for MTE prctl Mark Brown
2022-03-10 15:33   ` Joey Gouly
2022-03-10 15:37     ` Mark Brown
2022-03-10 20:07   ` Shuah Khan

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=dec7d25c-1cd4-1651-274f-19f2ff5c231c@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=will@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