public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: <pmladek@suse.com>, <juri.lelli@redhat.com>, <mingo@redhat.com>,
	<peterz@infradead.org>, <vincent.guittot@linaro.org>,
	<linux-kernel@vger.kernel.org>, <zyhtheonly@gmail.com>,
	<zwp10758@gmail.com>, <zyhtheonly@yeah.net>
Subject: Re: [PATCH v2 2/2] sched: print parent comm in sched_show_task()
Date: Fri, 10 Feb 2023 00:21:53 +0800	[thread overview]
Message-ID: <Y+UdoShroyR3iynv@chenyu5-mobl1> (raw)
In-Reply-To: <20230131080911.GA1601@didi-ThinkCentre-M930t-N000>

On 2023-01-31 at 16:10:26 +0800, Tio Zhang wrote:
> Knowing who the parent is might be useful for debugging.
> For example, we can sometimes resolve kernel hung tasks by stopping
> the person who begins those hung tasks.
> With the parent's name printed in sched_show_task(),
> it might be helpful to let people know which "service" should be operated.
> Also, we move the parent info to a following new line.
> It would better solve the situation when the task
s/would better/would be better/
> is not alive and we could not get information about the parent.
> 
> Signed-off-by: Tio Zhang <tiozhang@didiglobal.com>
>
Looks ok to me,
Tested-by: Chen Yu <yu.c.chen@intel.com> 

thanks,
Chenyu

  parent reply	other threads:[~2023-02-09 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 11:06 [PATCH v2] sched: print parent comm in sched_show_task() Tio Zhang
2023-01-20 13:09 ` Petr Mladek
2023-01-31  8:10   ` [PATCH v2 2/2] " Tio Zhang
2023-02-09  9:45     ` 张元瀚 Tio Zhang
2023-02-09 16:21     ` Chen Yu [this message]
     [not found]       ` <CAEQmJ=igQ8J9Y+_dWE6yaaFXHC965Sw+RxywWNLD=4G=tj0_hw@mail.gmail.com>
     [not found]         ` <CAEQmJ=iEC1G4MVRG=0XLWrCxqX_3E-6X-XbPeg8ti7oFjTBLBQ@mail.gmail.com>
2023-03-27 11:43           ` [RESEND][PATCH " Petr Mladek
2023-03-28  3:44             ` [PATCH v3] " Tio Zhang
2023-03-28  9:40               ` Petr Mladek
2023-06-02  5:44                 ` [PATCH v3 2/2] " Tio Zhang

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=Y+UdoShroyR3iynv@chenyu5-mobl1 \
    --to=yu.c.chen@intel.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=vincent.guittot@linaro.org \
    --cc=zwp10758@gmail.com \
    --cc=zyhtheonly@gmail.com \
    --cc=zyhtheonly@yeah.net \
    /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