[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200430020901.GC874567@tassilo.jf.intel.com>
Date: Wed, 29 Apr 2020 19:09:01 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Stephane Eranian <eranian@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>, mingo@...e.hu,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Jiri Olsa <jolsa@...hat.com>, Ian Rogers <irogers@...gle.com>,
"Liang, Kan" <kan.liang@...el.com>
Subject: Re: [PATCH] perf/script: remove extraneous newline in
perf_sample__fprintf_regs()
> I was under the impression that perf script was generating one line
> per sample. Otherwise, seems hard to parse.
That's only true for simple cases. A lot of the extended output options
have long generated multiple lines. And of course call stacks always did.
> Could you give me the cmdline options of perf script that justify the newline.
e.g. perf script -F iregs,uregs
-Andi
Powered by blists - more mailing lists