From: Shuah Khan <skhan@linuxfoundation.org>
To: Kalpana Shetty <kalpana.shetty@amd.com>,
akpm@linux-foundation.org, shuah@kernel.org, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH V3] selftests/vm: Add protection_keys tests to run_vmtests
Date: Fri, 17 Jun 2022 13:31:52 -0600 [thread overview]
Message-ID: <f73fd7c9-cb9c-1e89-4e22-e6931172eb91@linuxfoundation.org> (raw)
In-Reply-To: <20220617111019.476-1-kalpana.shetty@amd.com>
On 6/17/22 5:10 AM, Kalpana Shetty wrote:
> Adding "protected_keys" tests to "run_vmtests.sh" would help out to run all VM related tests
> from a single shell script.
>
> Signed-off-by: Kalpana Shetty <kalpana.shetty@amd.com>
> ---
> Changes in V3:
> Shuah Khan's review comments incorporated, added protection_keys binary check.
>
> tools/testing/selftests/vm/run_vmtests.sh | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/tools/testing/selftests/vm/run_vmtests.sh b/tools/testing/selftests/vm/run_vmtests.sh
> index 41fce8bea929..b19c6b1b84c4 100755
> --- a/tools/testing/selftests/vm/run_vmtests.sh
> +++ b/tools/testing/selftests/vm/run_vmtests.sh
> @@ -179,4 +179,15 @@ run_test ./ksm_tests -N -m 1
> # KSM test with 2 NUMA nodes and merge_across_nodes = 0
> run_test ./ksm_tests -N -m 0
>
> +# protection_keys tests
> +if ./protection_keys_32 &> /dev/null
> +then
> + run_test ./protection_keys_32
> +fi
> +
> +if ./protection_keys_64 &> /dev/null
> +then
> + run_test ./protection_keys_64
> +fi
> +
> exit $exitcode
>
Why not use file test operators. -x works for this case.
There is no need to run attempt to run the test.
thanks,
-- Shuah
next prev parent reply other threads:[~2022-06-17 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 11:10 Kalpana Shetty
2022-06-17 19:31 ` Shuah Khan [this message]
2022-06-17 20:31 ` Shetty, Kalpana
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=f73fd7c9-cb9c-1e89-4e22-e6931172eb91@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=kalpana.shetty@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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