mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "tan.shaopeng@fujitsu.com" <tan.shaopeng@fujitsu.com>
To: 'Fenghua Yu' <fenghua.yu@intel.com>
Cc: Reinette Chatre <reinette.chatre@intel.com>,
	Shuah Khan <shuah@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>
Subject: RE: [PATCH v4 5/6] selftests/resctrl: Update README about using kselftest framework to build/run resctrl_tests
Date: Mon, 7 Mar 2022 08:07:54 +0000	[thread overview]
Message-ID: <TYAPR01MB63300F931E2003DCE16276338B089@TYAPR01MB6330.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <YiJ4YM49fFANO9C2@otcwcpicx3.sc.intel.com>

Hi Fenghua,

> On Fri, Mar 04, 2022 at 07:38:33PM +0900, Shaopeng Tan wrote:
> > In this patch series, I make restrl_tests build/run using kselftest
> > framework, but some users do not known how to build/run resctrl_tests
> > using kseltest framework.
> 
> Please don't use "I" or "we" in commit messages. Also the grammar seems not
> right here.
> 
> >
> > Add manual of how to make resctrl_tests build/run using kselftest
> > framework into README.
> 
> Maybe change the commit message to this:
> 
> resctrl_tests can be built or run using kselftests framework. Add description on
> how to do so in README.

Thanks for your advice. I will use it for commit log in next version.

> >
> > Signed-off-by: Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>
> > ---
> >  tools/testing/selftests/resctrl/README | 31
> > +++++++++++++++++++++++++-
> >  1 file changed, 30 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/selftests/resctrl/README
> > b/tools/testing/selftests/resctrl/README
> > index 3d2bbd4fa3aa..268cf3f95bd5 100644
> > --- a/tools/testing/selftests/resctrl/README
> > +++ b/tools/testing/selftests/resctrl/README
> > @@ -12,9 +12,37 @@ 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.
> > +
> > +USE KSELFTEST FRAMEWORK
> > +-----------------------
> > +
> > +BUILD
> > +-----
> 
> The "---" under titles are all same. This cannot tell readers clearly topic
> hierarchies.
> 
> How about this?
> +USE KSELFTEST FRAMEWORK
> +-----------------------
> +
> +* BUILD
> +
> 
> > +
> > +Execute the following command in top level directory of the kernel source.
> > +
> > +Build resctrl:
> > + $ make -C tools/testing/selftests TARGETS=resctrl
> > +
> > +RUN
> > +---
> 
> How about this?
> +* RUN
> +
> > +
> > +Run resctrl:
> > + $ make -C tools/testing/selftests TARGETS=resctrl run_tests
> 
> Run this as sudo or root.
> + $ sudo make -C tools/testing/selftests TARGETS=resctrl run_tests

Thanks, I will take your above advice in next version.

> > +
> > +Using kselftest framework, the ./resctrl_tests will be run without any
> parameters.
> > +
> > +More details about kselftest framework as follow.
> > +Documentation/dev-tools/kselftest.rst
> > +
> > +NOT USE KSELFTEST FRAMEWORK
> > +---------------------------
> > +
> >  BUILD
> >  -----
> >
> > +Execute the following command in this
> directory(tools/testing/selftests/resctrl/).
> >  Run "make" to build executable file "resctrl_tests".
> >
> >  RUN
> > @@ -24,7 +52,8 @@ 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:
> > +Executing the test without any parameter will run all supported tests.
> > +It takes about 68 seconds on a Intel(R) Xeon(R) Gold 6254 CPU @ 3.10GHz.
> 
> resctrl will add more tests in the future. Running time may be longer in the
> future. I would suggest to remove the "It takes about 68 seconds..." line.

I added this sentence based on Shuah Khan's feedback, but I didn't consider extending this test.
I will delete this sentence in next version.

> >  	sudo ./resctrl_tests
> >
> > --
> > 2.27.0
> >

Best regards,
Tan Shaopeng

  reply	other threads:[~2022-03-07  8:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 10:38 [PATCH v4 0/6] selftests/resctrl: Add resctrl_tests into kselftest set Shaopeng Tan
2022-03-04 10:38 ` [PATCH v4 1/6] selftests/resctrl: Kill child process before parent process terminates if SIGTERM is received Shaopeng Tan
2022-03-04 10:38 ` [PATCH v4 2/6] selftests/resctrl: Change the default limited time to 120 seconds Shaopeng Tan
2022-03-04 20:45   ` Fenghua Yu
2022-03-04 10:38 ` [PATCH v4 3/6] selftests/resctrl: Fix resctrl_tests' return code to work with selftest framework Shaopeng Tan
2022-03-04 10:38 ` [PATCH v4 4/6] selftests/resctrl: Make resctrl_tests run using kselftest framework Shaopeng Tan
2022-03-04 10:38 ` [PATCH v4 5/6] selftests/resctrl: Update README about using kselftest framework to build/run resctrl_tests Shaopeng Tan
2022-03-04 20:37   ` Fenghua Yu
2022-03-07  8:07     ` tan.shaopeng [this message]
2022-03-04 10:38 ` [PATCH v4 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=TYAPR01MB63300F931E2003DCE16276338B089@TYAPR01MB6330.jpnprd01.prod.outlook.com \
    --to=tan.shaopeng@fujitsu.com \
    --cc=fenghua.yu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®