linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Ian Rogers <irogers@google.com>,
	linux-perf-users@vger.kernel.org, Will Deacon <will@kernel.org>,
	Waiman Long <longman@redhat.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Davidlohr Bueso <dave@stgolabs.net>
Subject: Re: [PATCH 1/5] perf lock: Change to synthesize task events
Date: Fri, 3 Jun 2022 21:28:47 +0200	[thread overview]
Message-ID: <Yppg7yCks8JWEjK9@kernel.org> (raw)
In-Reply-To: <20220601065846.456965-2-namhyung@kernel.org>

Em Tue, May 31, 2022 at 11:58:42PM -0700, Namhyung Kim escreveu:
> With -t/--threads option, it needs to display task names so synthesize
> task related events at the beginning.

Cherry picked this one.
 
> Fixes: 7c3bcbdf449f ("perf lock: Add -t/--thread option for report")
> Acked-by: Ian Rogers <irogers@google.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> ---
>  tools/perf/builtin-lock.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> index b1200b7340a6..23a33ac15e68 100644
> --- a/tools/perf/builtin-lock.c
> +++ b/tools/perf/builtin-lock.c
> @@ -1083,7 +1083,7 @@ static int __cmd_report(bool display_info)
>  static int __cmd_record(int argc, const char **argv)
>  {
>  	const char *record_args[] = {
> -		"record", "-R", "-m", "1024", "-c", "1", "--synth", "no",
> +		"record", "-R", "-m", "1024", "-c", "1", "--synth", "task",
>  	};
>  	unsigned int rec_argc, i, j, ret;
>  	const char **rec_argv;
> 
> base-commit: 9dde6cadb92b5670b23b97ec53091df0530ec38b
> -- 
> 2.36.1.255.ge46751e96f-goog

-- 

- Arnaldo

  reply	other threads:[~2022-06-03 19:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01  6:58 [PATCHSET 0/5] perf lock: New lock contention tracepoints support (v1) Namhyung Kim
2022-06-01  6:58 ` [PATCH 1/5] perf lock: Change to synthesize task events Namhyung Kim
2022-06-03 19:28   ` Arnaldo Carvalho de Melo [this message]
2022-06-01  6:58 ` [PATCH 2/5] perf lock: Add lock contention tracepoints record support Namhyung Kim
2022-06-02  6:21   ` Ian Rogers
2022-06-02 20:06     ` Namhyung Kim
2022-06-01  6:58 ` [PATCH 3/5] perf lock: Handle lock contention tracepoints Namhyung Kim
2022-06-02  6:23   ` Ian Rogers
2022-06-01  6:58 ` [PATCH 4/5] perf record: Allow to specify max stack depth of fp callchain Namhyung Kim
2022-06-02  6:29   ` Ian Rogers
2022-06-02 20:09     ` Namhyung Kim
2022-06-01  6:58 ` [PATCH 5/5] perf lock: Look up callchain for the contended locks Namhyung Kim
2022-06-02  6:31   ` Ian Rogers

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=Yppg7yCks8JWEjK9@kernel.org \
    --to=acme@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=will@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).