Em Tue, Feb 27, 2018 at 08:53:13AM +0800, Jin, Yao escreveu:
>
>
> On 1/23/2018 10:19 PM, Jiri Olsa wrote:
> > On Mon, Jan 22, 2018 at 01:10:31PM +0800, Jin, Yao wrote:
> > >
> > >
> > > On 1/16/2018 9:17 PM, Jiri Olsa wrote:
> > > > On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
>
Em Tue, Feb 27, 2018 at 08:53:13AM +0800, Jin, Yao escreveu:
>
>
> On 1/23/2018 10:19 PM, Jiri Olsa wrote:
> > On Mon, Jan 22, 2018 at 01:10:31PM +0800, Jin, Yao wrote:
> > >
> > >
> > > On 1/16/2018 9:17 PM, Jiri Olsa wrote:
> > > > On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
>
On 1/23/2018 10:19 PM, Jiri Olsa wrote:
On Mon, Jan 22, 2018 at 01:10:31PM +0800, Jin, Yao wrote:
On 1/16/2018 9:17 PM, Jiri Olsa wrote:
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much..
On 1/23/2018 10:19 PM, Jiri Olsa wrote:
On Mon, Jan 22, 2018 at 01:10:31PM +0800, Jin, Yao wrote:
On 1/16/2018 9:17 PM, Jiri Olsa wrote:
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much..
On Mon, Jan 22, 2018 at 01:10:31PM +0800, Jin, Yao wrote:
>
>
> On 1/16/2018 9:17 PM, Jiri Olsa wrote:
> > On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
> > > Just tested. But looks it's not OK for '--per-thread' case.
> >
> > yea, I haven't tested much.. might need soem tweaking,
>
On Mon, Jan 22, 2018 at 01:10:31PM +0800, Jin, Yao wrote:
>
>
> On 1/16/2018 9:17 PM, Jiri Olsa wrote:
> > On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
> > > Just tested. But looks it's not OK for '--per-thread' case.
> >
> > yea, I haven't tested much.. might need soem tweaking,
>
On 1/16/2018 9:17 PM, Jiri Olsa wrote:
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much.. might need soem tweaking,
but my point was that it could be doable on one place
instead of introducing
On 1/16/2018 9:17 PM, Jiri Olsa wrote:
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much.. might need soem tweaking,
but my point was that it could be doable on one place
instead of introducing
On 1/16/2018 9:17 PM, Jiri Olsa wrote:
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much.. might need soem tweaking,
but my point was that it could be doable on one place
instead of introducing
On 1/16/2018 9:17 PM, Jiri Olsa wrote:
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much.. might need soem tweaking,
but my point was that it could be doable on one place
instead of introducing
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
> Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much.. might need soem tweaking,
but my point was that it could be doable on one place
instead of introducing another if possible
jirka
On Tue, Jan 16, 2018 at 09:06:09PM +0800, Jin, Yao wrote:
> Just tested. But looks it's not OK for '--per-thread' case.
yea, I haven't tested much.. might need soem tweaking,
but my point was that it could be doable on one place
instead of introducing another if possible
jirka
Just tested. But looks it's not OK for '--per-thread' case.
jinyao@skl:~/$ ./perf stat --per-thread
WARNING: Ignored open failure for pid 1
WARNING: Ignored open failure for pid 2
WARNING: Ignored open failure for pid 4
WARNING: Ignored open failure for pid 6
WARNING: Ignored open failure for
Just tested. But looks it's not OK for '--per-thread' case.
jinyao@skl:~/$ ./perf stat --per-thread
WARNING: Ignored open failure for pid 1
WARNING: Ignored open failure for pid 2
WARNING: Ignored open failure for pid 4
WARNING: Ignored open failure for pid 6
WARNING: Ignored open failure for
On Tue, Jan 16, 2018 at 11:43:08PM +0800, Jin Yao wrote:
> If we execute 'perf stat --per-thread' with non-root account
> (even set kernel.perf_event_paranoid = -1 yet), it reports the error:
>
> jinyao@skl:~$ perf stat --per-thread
> Error:
> You may not have permission to collect system-wide
On Tue, Jan 16, 2018 at 11:43:08PM +0800, Jin Yao wrote:
> If we execute 'perf stat --per-thread' with non-root account
> (even set kernel.perf_event_paranoid = -1 yet), it reports the error:
>
> jinyao@skl:~$ perf stat --per-thread
> Error:
> You may not have permission to collect system-wide
If we execute 'perf stat --per-thread' with non-root account
(even set kernel.perf_event_paranoid = -1 yet), it reports the error:
jinyao@skl:~$ perf stat --per-thread
Error:
You may not have permission to collect system-wide stats.
Consider tweaking /proc/sys/kernel/perf_event_paranoid,
which
If we execute 'perf stat --per-thread' with non-root account
(even set kernel.perf_event_paranoid = -1 yet), it reports the error:
jinyao@skl:~$ perf stat --per-thread
Error:
You may not have permission to collect system-wide stats.
Consider tweaking /proc/sys/kernel/perf_event_paranoid,
which
18 matches
Mail list logo
