[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANLsYkxAVU7yX-a0mUGxC0EtLZUpORPSpbgHeUPo99JOFRu2xg@mail.gmail.com>
Date: Wed, 3 Aug 2016 15:46:29 -0600
From: Mathieu Poirier <mathieu.poirier@...aro.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>, jolsa@...nel.org,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH V3 4/6] perf tools: pushing driver configuration down to
the kernel
On 31 July 2016 at 06:03, Jiri Olsa <jolsa@...hat.com> wrote:
> On Thu, Jul 28, 2016 at 03:42:21PM -0600, Mathieu Poirier wrote:
>> Now that PMU specific driver configuration are queued in
>> evsel::config_terms, all we need to do is re-use the current
>> ioctl() mechanism to push down the information to the kernel
>> driver.
>>
>> Signed-off-by: Mathieu Poirier <mathieu.poirier@...aro.org>
>> ---
>> tools/perf/builtin-record.c | 9 +++++++++
>> tools/perf/builtin-stat.c | 8 ++++++++
>
> how about perf top?
It took me a while to notice the "event" option in cmd_top(). You are
correct, it applies there as well.
Mathieu
>
> jirka
Powered by blists - more mailing lists