public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephane Eranian <eranian@google.com>,
	Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 2/2] perf evlist: Support pipe mode display
Date: Mon, 14 Dec 2020 00:00:35 +0100	[thread overview]
Message-ID: <20201213230035.GC502638@krava> (raw)
In-Reply-To: <20201210061302.88213-2-namhyung@kernel.org>

On Thu, Dec 10, 2020 at 03:13:02PM +0900, Namhyung Kim wrote:
> Likewise, perf evlist command should print event attributes by reading
> PERF_RECORD_HEADER_ATTR records.
> 
> Before:
>   $ perf record -o- true | ./perf evlist -i-
>   (prints nothing)
> 
> After:
>   $ perf record -o- true | ./perf evlist -i-
>   cycles:pppH
> 
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>

Acked-by: Jiri Olsa <jolsa@redhat.com>

thanks,
jirka

> ---
>  tools/perf/builtin-evlist.c | 18 +++++++++++++++++-
>  1 file changed, 17 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/perf/builtin-evlist.c b/tools/perf/builtin-evlist.c
> index 98e992801251..4617b32c9c97 100644
> --- a/tools/perf/builtin-evlist.c
> +++ b/tools/perf/builtin-evlist.c
> @@ -17,6 +17,14 @@
>  #include "util/data.h"
>  #include "util/debug.h"
>  #include <linux/err.h>
> +#include "util/tool.h"
> +
> +static int process_header_feature(struct perf_session *session __maybe_unused,
> +				  union perf_event *event __maybe_unused)
> +{
> +	session_done = 1;
> +	return 0;
> +}
>  
>  static int __cmd_evlist(const char *file_name, struct perf_attr_details *details)
>  {
> @@ -27,12 +35,20 @@ static int __cmd_evlist(const char *file_name, struct perf_attr_details *details
>  		.mode      = PERF_DATA_MODE_READ,
>  		.force     = details->force,
>  	};
> +	struct perf_tool tool = {
> +		/* only needed for pipe mode */
> +		.attr = perf_event__process_attr,
> +		.feature = process_header_feature,
> +	};
>  	bool has_tracepoint = false;
>  
> -	session = perf_session__new(&data, 0, NULL);
> +	session = perf_session__new(&data, 0, &tool);
>  	if (IS_ERR(session))
>  		return PTR_ERR(session);
>  
> +	if (data.is_pipe)
> +		perf_session__process_events(session);
> +
>  	evlist__for_each_entry(session->evlist, pos) {
>  		evsel__fprintf(pos, details, stdout);
>  
> -- 
> 2.29.2.576.ga3fc446d84-goog
> 


  reply	other threads:[~2020-12-13 23:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10  6:13 [PATCH 1/2] perf report: Support --header-only for pipe mode Namhyung Kim
2020-12-10  6:13 ` [PATCH 2/2] perf evlist: Support pipe mode display Namhyung Kim
2020-12-13 23:00   ` Jiri Olsa [this message]
2020-12-14 13:22     ` Arnaldo Carvalho de Melo
2020-12-13 23:00 ` [PATCH 1/2] perf report: Support --header-only for pipe mode Jiri Olsa
2020-12-14 13:22   ` Arnaldo Carvalho de Melo

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=20201213230035.GC502638@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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