Re: [PATCH] perf record: fix priv level with branch sampling for paranoid=2

2019-09-20 Thread Stephane Eranian
On Fri, Sep 20, 2019 at 12:12 PM Jiri Olsa wrote: > > On Tue, Sep 03, 2019 at 11:26:03PM -0700, Stephane Eranian wrote: > > Now that the default perf_events paranoid level is set to 2, a regular user > > cannot monitor kernel level activity anymore. As such, with the following > > cmdline: > > > >

Re: [PATCH] perf record: fix priv level with branch sampling for paranoid=2

2019-09-20 Thread Jiri Olsa
On Tue, Sep 03, 2019 at 11:26:03PM -0700, Stephane Eranian wrote: > Now that the default perf_events paranoid level is set to 2, a regular user > cannot monitor kernel level activity anymore. As such, with the following > cmdline: > > $ perf record -e cycles date > > The perf tool first tries cyc

Re: [PATCH] perf record: fix priv level with branch sampling for paranoid=2

2019-09-13 Thread Stephane Eranian
On Tue, Sep 3, 2019 at 11:26 PM Stephane Eranian wrote: > > Now that the default perf_events paranoid level is set to 2, a regular user > cannot monitor kernel level activity anymore. As such, with the following > cmdline: > > $ perf record -e cycles date > > The perf tool first tries cycles:uk bu

[PATCH] perf record: fix priv level with branch sampling for paranoid=2

2019-09-03 Thread Stephane Eranian
Now that the default perf_events paranoid level is set to 2, a regular user cannot monitor kernel level activity anymore. As such, with the following cmdline: $ perf record -e cycles date The perf tool first tries cycles:uk but then falls back to cycles:u as can be seen in the perf report --heade