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 v8 0/6] Some improvements of resctrl selftest
Date: Wed, 12 Apr 2023 10:30:47 -0700 [thread overview]
Message-ID: <96b6b5ae-078f-fbde-7cd9-d64d766f6727@intel.com> (raw)
In-Reply-To: <20230215083230.3155897-1-tan.shaopeng@jp.fujitsu.com>
Hi Shaopeng,
On 2/15/2023 12:32 AM, Shaopeng Tan wrote:
> Hello,
>
> The aim of this patch series is to improve the resctrl selftest.
> Without these fixes, some unnecessary processing will be executed
> and test results will be confusing.
> There is no behavior change in test themselves.
>
> [patch 1] Make write_schemata() run to set up shemata with 100% allocation
> on first run in MBM test.
> [patch 2] The MBA test result message is always output as "ok",
> make output message to be "not ok" if MBA check result is failed.
> [patch 3] When a child process is created by fork(), the buffer of the
> parent process is also copied. Flush the buffer before
> executing fork().
> [patch 4] An error occurs whether in parents process or child process,
> the parents process always kills child process and runs
> umount_resctrlfs(), and the child process always waits to be
> killed by the parent process.
> [patch 5] If a signal received, to cleanup properly before exiting the
> parent process, commonize the signal handler registered for
> CMT/MBM/MBA tests and reuse it in CAT, also unregister the
> signal handler at the end of each test.
> [patch 6] Before exiting each test CMT/CAT/MBM/MBA, clear test result
> files function cat/cmt/mbm/mba_test_cleanup() are called
> twice. Delete once.
>
> This patch series is based on Linux v6.2-rc7.
>
A later patch series was picked up by kselftest causing a conflict with
this series. Could you please submit a new version that is based on
the "next" branch of
git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git ?
Thank you very much
Reinette
prev parent reply other threads:[~2023-04-12 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 8:32 [PATCH v8 0/6] Some improvements of resctrl selftest Shaopeng Tan
2023-02-15 8:32 ` [PATCH v8 1/6] selftests/resctrl: Fix set up schemata with 100% allocation on first run in MBM test Shaopeng Tan
2023-02-15 8:32 ` [PATCH v8 2/6] selftests/resctrl: Return MBA check result and make it to output message Shaopeng Tan
2023-02-15 8:32 ` [PATCH v8 3/6] selftests/resctrl: Flush stdout file buffer before executing fork() Shaopeng Tan
2023-02-15 8:32 ` [PATCH v8 4/6] selftests/resctrl: Cleanup properly when an error occurs in CAT test Shaopeng Tan
2023-02-15 8:32 ` [PATCH v8 5/6] selftests/resctrl: Commonize the signal handler register/unregister for all tests Shaopeng Tan
2023-02-15 8:32 ` [PATCH v8 6/6] selftests/resctrl: Remove duplicate codes that clear each test result file Shaopeng Tan
2023-03-10 22:25 ` [PATCH v8 0/6] Some improvements of resctrl selftest Reinette Chatre
2023-03-22 20:34 ` Reinette Chatre
2023-04-12 17:30 ` Reinette Chatre [this message]
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=96b6b5ae-078f-fbde-7cd9-d64d766f6727@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