From: Steven Rostedt <rostedt@goodmis.org>
To: Ze Gao <zegao2021@gmail.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ian Rogers <irogers@google.com>, Ingo Molnar <mingo@redhat.com>,
Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, Ze Gao <zegao@tencent.com>
Subject: Re: [RFC PATCH v6 5/5] perf sched: prefer to use prev_state_char introduced in sched_switch
Date: Thu, 3 Aug 2023 05:34:05 -0400 [thread overview]
Message-ID: <20230803053405.4d91015d@gandalf.local.home> (raw)
In-Reply-To: <20230803083352.1585-6-zegao@tencent.com>
On Thu, 3 Aug 2023 04:33:52 -0400
Ze Gao <zegao2021@gmail.com> wrote:
> Since the sched_switch tracepoint introduces a new variable to
> report sched-out task state in symbolic char, we prefer to use
> it to spare from knowing internal implementations in kernel.
The above needs to be rewritten to be more comprehensive.
Feel free to reply to this thread with new versions of the change log and
such. No need to send a new patch series to fix this before you know that
the new version is acceptable or not.
Replying to a current patch series is fine, but sending out a new one
causes the spam as it's much easier to ignore a thread than to ignore a new
thread with a new series.
Thanks,
-- Steve
>
> Also we keep the old parsing logic intact but sync the state char
> array with the latest kernel.
>
> Signed-off-by: Ze Gao <zegao@tencent.com>
> ---
> tools/perf/builtin-sched.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
> index 5042874ba204..6f99a36206c9 100644
> --- a/tools/perf/builtin-sched.c
> +++ b/tools/perf/builtin-sched.c
> @@ -837,7 +837,7 @@ replay_wakeup_event(struct perf_sched *sched,
>
> static inline char task_state_char(int state)
> {
> - static const char state_to_char[] = "RSDTtXZPI";
> + static const char state_to_char[] = "RSDTtXZPIp";
> unsigned int bit = state ? ffs(state) : 0;
>
> return bit < sizeof(state_to_char) - 1 ? state_to_char[bit] : '?';
> @@ -846,9 +846,20 @@ static inline char task_state_char(int state)
> static inline char get_task_prev_state(struct evsel *evsel,
> struct perf_sample *sample)
> {
> - const int prev_state = evsel__intval(evsel, sample, "prev_state");
> + char prev_state_char;
> + int prev_state;
>
> - return task_state_char(prev_state);
> + /* prefer to use prev_state_char */
> + if (evsel__field(evsel, "prev_state_char"))
> + prev_state_char = (char) evsel__intval(evsel,
> + sample, "prev_state_char");
> + else {
> + prev_state = (int) evsel__intval(evsel,
> + sample, "prev_state");
> + prev_state_char = task_state_char(prev_state);
> + }
> +
> + return prev_state_char;
> }
>
> static int replay_switch_event(struct perf_sched *sched,
> @@ -2145,7 +2156,7 @@ static void timehist_update_runtime_stats(struct thread_runtime *r,
> else if (r->last_time) {
> u64 dt_wait = tprev - r->last_time;
>
> - if (r->last_state == 'R')
> + if (r->last_state == 'R' || r->last_state == 'p')
> r->dt_preempt = dt_wait;
> else if (r->last_state == 'D')
> r->dt_iowait = dt_wait;
next prev parent reply other threads:[~2023-08-03 9:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:33 [RFC PATCH v6 0/5] fix task state report from sched tracepoint Ze Gao
2023-08-03 8:33 ` [RFC PATCH v6 1/5] perf sched: sync state char array with the kernel Ze Gao
2023-08-03 9:09 ` Steven Rostedt
2023-08-03 10:29 ` Ze Gao
2023-08-03 12:25 ` Ze Gao
2023-08-03 12:39 ` Ze Gao
2023-08-03 15:10 ` Steven Rostedt
2023-08-04 2:21 ` Ze Gao
2023-08-04 2:38 ` Ze Gao
2023-08-04 3:19 ` Ze Gao
2023-08-04 3:41 ` Steven Rostedt
2023-08-10 5:50 ` Ze Gao
2023-08-10 6:07 ` [PATCH] perf sched: parse task state from tracepoint print format Ze Gao
2023-08-11 17:28 ` Steven Rostedt
2023-08-14 2:28 ` Ze Gao
2023-08-03 8:33 ` [RFC PATCH v6 2/5] perf sched: reorganize sched-out task state report code Ze Gao
2023-08-03 9:10 ` Steven Rostedt
2023-08-03 12:37 ` Ze Gao
2023-08-03 8:33 ` [RFC PATCH v6 3/5] sched, tracing: reorganize fields of switch event struct Ze Gao
2023-08-03 8:53 ` Peter Zijlstra
2023-08-03 11:06 ` Ze Gao
2023-08-03 9:18 ` Steven Rostedt
2023-08-03 9:51 ` Peter Zijlstra
2023-08-03 14:45 ` Steven Rostedt
2023-08-03 12:54 ` Ze Gao
2023-08-03 12:57 ` Ze Gao
2023-08-23 2:52 ` kernel test robot
2023-08-03 8:33 ` [RFC PATCH v6 4/5] sched, tracing: add to report task state in symbolic chars Ze Gao
2023-08-03 8:59 ` Peter Zijlstra
2023-08-03 13:09 ` Ze Gao
2023-08-03 9:29 ` Steven Rostedt
2023-08-03 10:55 ` Ze Gao
2023-08-03 8:33 ` [RFC PATCH v6 5/5] perf sched: prefer to use prev_state_char introduced in sched_switch Ze Gao
2023-08-03 9:34 ` Steven Rostedt [this message]
2023-08-03 11:01 ` Ze Gao
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=20230803053405.4d91015d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=zegao2021@gmail.com \
--cc=zegao@tencent.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
all inboxes | Powered by JetHome®