public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: Shaopeng Tan <tan.shaopeng@jp.fujitsu.com>,
	Fenghua Yu <fenghua.yu@intel.com>, Shuah Khan <shuah@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v7 4/6] selftests/resctrl: Cleanup properly when an error occurs in CAT test
Date: Tue, 14 Feb 2023 11:41:08 +0200 (EET)	[thread overview]
Message-ID: <7c99dc3c-a4fe-3285-f48f-8d1a562db2fb@linux.intel.com> (raw)
In-Reply-To: <1a933b7c-0318-ce06-9239-197d78c9889d@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Mon, 13 Feb 2023, Reinette Chatre wrote:

> 
> 
> On 2/13/2023 2:00 AM, Ilpo Järvinen wrote:
> > On Mon, 13 Feb 2023, Shaopeng Tan wrote:
> > 
> >> After creating a child process with fork() in CAT test, if an error
> >> occurs when parent process runs cat_val() or check_results(), the child
> > 
> > I'd replace the rest of the paragraph with this:
> > 
> > "returns early. The parent will wait pipe message from child which will 
> > never be sent by the child and the parent cannot proceeed to unmount 
> > resctrlfs."
> 
> Note that the description is about an error within the parent process.
> In the case snipped above it is the parent that exits early, not the child.

Ah, that a good point. Somehow I was too fixed into thinking the child 
exiting because it's what it's come across myself.

-- 
 i.

> This first paragraph describes two scenarios, (a) error in parent, and (b)
> error in child. I think it is good information to keep descriptions of
> both scenarios.
> 
> The proposed addition could be used to expand the description of the scenario
> when an error occurs in the child. In this case please consider changing "wait
> pipe message from child" to "wait for the pipe message from the child", and
> "proceeed" to "proceed".
> 
> Reinette
> 

  reply	other threads:[~2023-02-14  9:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  6:24 [PATCH v7 0/6] Some improvements of resctrl selftest Shaopeng Tan
2023-02-13  6:24 ` [PATCH v7 1/6] selftests/resctrl: Fix set up schemata with 100% allocation on first run in MBM test Shaopeng Tan
2023-02-13  6:24 ` [PATCH v7 2/6] selftests/resctrl: Return MBA check result and make it to output message Shaopeng Tan
2023-02-13  6:24 ` [PATCH v7 3/6] selftests/resctrl: Flush stdout file buffer before executing fork() Shaopeng Tan
2023-02-13  6:24 ` [PATCH v7 4/6] selftests/resctrl: Cleanup properly when an error occurs in CAT test Shaopeng Tan
2023-02-13 10:00   ` Ilpo Järvinen
2023-02-13 19:20     ` Reinette Chatre
2023-02-14  9:41       ` Ilpo Järvinen [this message]
2023-02-13 19:21   ` Reinette Chatre
2023-02-13  6:24 ` [PATCH v7 5/6] selftests/resctrl: Commonize the signal handler register/unregister for all tests Shaopeng Tan
2023-02-13 10:29   ` Ilpo Järvinen
2023-02-13 19:21   ` Reinette Chatre
2023-02-13  6:24 ` [PATCH v7 6/6] selftests/resctrl: Remove duplicate codes that clear each test result file 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=7c99dc3c-a4fe-3285-f48f-8d1a562db2fb@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.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 \
    --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