From: Reinette Chatre <reinette.chatre@intel.com>
To: Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>,
Fenghua Yu <fenghua.yu@intel.com>, Shuah Khan <shuah@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v5 5/6] selftests/resctrl: Update README about using kselftest framework to build/run resctrl_tests
Date: Fri, 11 Mar 2022 15:20:14 -0800 [thread overview]
Message-ID: <44e4d46d-c0cb-8010-4ec9-34441e1d2cb0@intel.com> (raw)
In-Reply-To: <20220311072147.3301525-6-tan.shaopeng@jp.fujitsu.com>
Hi Shaopeng Tan,
On 3/10/2022 11:21 PM, Shaopeng Tan wrote:
> resctrl_tests can be built or run using kselftests framework.
> Add description on how to do so in README.
>
> Signed-off-by: Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
> ---
> tools/testing/selftests/resctrl/README | 43 ++++++++++++++++++++------
> 1 file changed, 34 insertions(+), 9 deletions(-)
>
> diff --git a/tools/testing/selftests/resctrl/README b/tools/testing/selftests/resctrl/README
> index 3d2bbd4fa3aa..c74b8246e6c9 100644
> --- a/tools/testing/selftests/resctrl/README
> +++ b/tools/testing/selftests/resctrl/README
> @@ -12,24 +12,49 @@ Allocation test on Intel RDT hardware. More tests will be added in the future.
> And the test suit can be extended to cover AMD QoS and ARM MPAM hardware
> as well.
>
> +resctrl_tests can be run with or without kselftest framework.
Saying "with or without kselftest framework" sounds good. Could you please
keep using that instead of the "use" and "not use" in the new headers?
> +
> +USE KSELFTEST FRAMEWORK
> +=======================
So, here it can be "WITH KSELFTEST FRAMEWORK"
> +
> +* BUILD
> +-------
Please remove the "*" to make it consistent with the "BUILD" later in the file.
> +
> +Build executable file "resctrl_tests" at top level directory of the kernel source.
> + $ make -C tools/testing/selftests TARGETS=resctrl
Please use ":" after the sentence that describes a command that follows. For
example, above would read:
Build executable file "resctrl_tests" from top level directory of the kernel source:
$ make -C tools/testing/selftests TARGETS=resctrl
(also note me changing "at" to "from")
> +
> +* RUN
Please remove the "*" to make it consistent with the "RUN" later in the file.
> +-----
> +
> +Run resctrl_tests as sudo or root since the test needs to mount resctrl file
> +system and change contents in the file system.
> +Using kselftest framework will run all supported tests of resctrl_tests.
"tests of resctrl_tests." -> "tests within resctrl_tests:"?
> +
> + $ sudo make -C tools/testing/selftests TARGETS=resctrl run_tests
> +
> +More details about kselftest framework as follow.
> +Documentation/dev-tools/kselftest.rst
"More details about kselftest framework can be found in Documentation/dev-tools/kselftest.rst."
> +
> +NOT USE KSELFTEST FRAMEWORK
> +===========================
("WITHOUT KSELFTEST FRAMEWORK")
> +
> BUILD
> -----
>
> -Run "make" to build executable file "resctrl_tests".
> +Build executable file "resctrl_tests" at this directory(tools/testing/selftests/resctrl/).
"at this directory" -> "from this directory"
"." -> ":"
> + $ make
>
> RUN
> ---
>
> -To use resctrl_tests, root or sudoer privileges are required. This is because
> -the test needs to mount resctrl file system and change contents in the file
> -system.
> -
> -Executing the test without any parameter will run all supported tests:
> +Run resctrl_tests as sudo or root since the test needs to mount resctrl file
> +system and change contents in the file system.
> +Executing the test without any parameter will run all supported tests.
"." -> ":"
>
> - sudo ./resctrl_tests
> + $ sudo ./resctrl_tests
>
> OVERVIEW OF EXECUTION
> ----------------------
> +=====================
>
> A test case has four stages:
>
> @@ -41,7 +66,7 @@ A test case has four stages:
> - teardown: umount resctrl and clear temporary files.
>
> ARGUMENTS
> ----------
> +=========
>
> Parameter '-h' shows usage information.
>
Reinette
next prev parent reply other threads:[~2022-03-11 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 7:21 [PATCH v5 0/6] selftests/resctrl: Add resctrl_tests into kselftest set Shaopeng Tan
2022-03-11 7:21 ` [PATCH v5 1/6] selftests/resctrl: Kill child process before parent process terminates if SIGTERM is received Shaopeng Tan
2022-03-11 23:12 ` Reinette Chatre
2022-03-11 7:21 ` [PATCH v5 2/6] selftests/resctrl: Change the default limited time to 120 seconds Shaopeng Tan
2022-03-11 23:12 ` Reinette Chatre
2022-03-11 7:21 ` [PATCH v5 3/6] selftests/resctrl: Fix resctrl_tests' return code to work with selftest framework Shaopeng Tan
2022-03-11 23:13 ` Reinette Chatre
2022-03-11 7:21 ` [PATCH v5 4/6] selftests/resctrl: Make resctrl_tests run using kselftest framework Shaopeng Tan
2022-03-11 23:14 ` Reinette Chatre
2022-03-13 15:47 ` Muhammad Usama Anjum
2022-03-11 7:21 ` [PATCH v5 5/6] selftests/resctrl: Update README about using kselftest framework to build/run resctrl_tests Shaopeng Tan
2022-03-11 23:20 ` Reinette Chatre [this message]
2022-03-11 7:21 ` [PATCH v5 6/6] selftests/resctrl: Add missing SPDX license to Makefile 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=44e4d46d-c0cb-8010-4ec9-34441e1d2cb0@intel.com \
--to=reinette.chatre@intel.com \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--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