From: David Ahern <dsahern@gmail.com>
To: Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>,
linux-kernel@vger.kernel.org
Cc: ltc-kernel@rdgml.intra.hitachi.co.jp,
masumi.moritani.ju@hitachi.com, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH v2] perf sched: fix wrong conversion of task state
Date: Wed, 27 Jul 2016 10:52:14 -0600 [thread overview]
Message-ID: <cb17fc2e-22aa-633e-05e1-4d0a454049b6@gmail.com> (raw)
In-Reply-To: <1469635660-29303-1-git-send-email-tomoki.sekiyama.qu@hitachi.com>
On 7/27/16 10:07 AM, Tomoki Sekiyama wrote:
> sched_out_state() converts the prev_state u64 bitmask to a char in
> a wrong way, which may cause wrong results of 'perf sched latency'.
> This patch fixes the conversion.
> Also, preempted tasks must be considered that they are in the
> THREAD_WAIT_CPU state.
you reference fixing the order of XZ as well.
>
> Signed-off-by: Tomoki Sekiyama <tomoki.sekiyama.qu@hitachi.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: David Ahern <dsahern@gmail.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> ---
> tools/perf/builtin-sched.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
> index 0dfe8df..8651c36 100644
> --- a/tools/perf/builtin-sched.c
> +++ b/tools/perf/builtin-sched.c
> @@ -70,7 +70,8 @@ struct sched_atom {
> struct task_desc *wakee;
> };
>
> -#define TASK_STATE_TO_CHAR_STR "RSDTtZXxKWP"
> +/* TASK_STATE_MAX means the task is preempted(R+). Use '+' for it here. */
> +#define TASK_STATE_TO_CHAR_STR "RSDTtXZxKWPN+"
As I mentioned in a previous reply you can't add the '+' on the end.
next prev parent reply other threads:[~2016-07-27 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 16:07 Tomoki Sekiyama
2016-07-27 16:52 ` David Ahern [this message]
2016-07-27 23:43 ` Masami Hiramatsu
2016-07-29 4:00 ` Tomoki Sekiyama
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=cb17fc2e-22aa-633e-05e1-4d0a454049b6@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltc-kernel@rdgml.intra.hitachi.co.jp \
--cc=masumi.moritani.ju@hitachi.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=tomoki.sekiyama.qu@hitachi.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
Powered by JetHome