* Bug Report
@ 2015-05-11 16:57 Alex Newman
2015-05-11 17:14 ` David Ahern
0 siblings, 1 reply; 4+ messages in thread
From: Alex Newman @ 2015-05-11 16:57 UTC (permalink / raw)
To: linux-perf-users
Hello mailing list friends,
I am sorry if this is not the best place for this (where should I
report improvements for perf).
This command works when I have the correct permissions but if I don't
rather than getting "bad permissions" I get
posix4e@posix4e-P27GV2:~$ perf stat -e 'ext4:' -a
invalid or unsupported event: 'ext4:'
Run 'perf list' for a list of valid events
usage: perf stat [] []
-e, --event <event> event selector. use 'perf list' to list available events
I'd be happy to help fix this but I am still getting my head around
the parse_events infrastructure.
-Alex
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug Report
2015-05-11 16:57 Bug Report Alex Newman
@ 2015-05-11 17:14 ` David Ahern
2015-05-11 17:56 ` Alex Newman
0 siblings, 1 reply; 4+ messages in thread
From: David Ahern @ 2015-05-11 17:14 UTC (permalink / raw)
To: Alex Newman, linux-perf-users
On 5/11/15 10:57 AM, Alex Newman wrote:
> Hello mailing list friends,
>
> I am sorry if this is not the best place for this (where should I
> report improvements for perf).
>
> This command works when I have the correct permissions but if I don't
> rather than getting "bad permissions" I get
>
> posix4e@posix4e-P27GV2:~$ perf stat -e 'ext4:' -a
that's an invalid event list; it should never work. Did you mean -e
'ext4:*'?
David
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug Report
2015-05-11 17:14 ` David Ahern
@ 2015-05-11 17:56 ` Alex Newman
2015-05-11 21:42 ` Arnaldo Carvalho de Melo
0 siblings, 1 reply; 4+ messages in thread
From: Alex Newman @ 2015-05-11 17:56 UTC (permalink / raw)
To: David Ahern; +Cc: linux-perf-users
Ah sorry for the typo. David, that's correct. But you should be able
to replicate that the error message is not revealing.
On Mon, May 11, 2015 at 10:14 AM, David Ahern <dsahern@gmail.com> wrote:
> On 5/11/15 10:57 AM, Alex Newman wrote:
>>
>> Hello mailing list friends,
>>
>> I am sorry if this is not the best place for this (where should I
>> report improvements for perf).
>>
>> This command works when I have the correct permissions but if I don't
>> rather than getting "bad permissions" I get
>>
>> posix4e@posix4e-P27GV2:~$ perf stat -e 'ext4:' -a
>
>
> that's an invalid event list; it should never work. Did you mean -e
> 'ext4:*'?
>
> David
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Bug Report
2015-05-11 17:56 ` Alex Newman
@ 2015-05-11 21:42 ` Arnaldo Carvalho de Melo
0 siblings, 0 replies; 4+ messages in thread
From: Arnaldo Carvalho de Melo @ 2015-05-11 21:42 UTC (permalink / raw)
To: Alex Newman; +Cc: David Ahern, linux-perf-users
Em Mon, May 11, 2015 at 10:56:39AM -0700, Alex Newman escreveu:
> Ah sorry for the typo. David, that's correct. But you should be able
> to replicate that the error message is not revealing.
It should be changed to emit better messages like was done for 'perf
trace':
[acme@zoo linux]$ trace usleep 1
Error: No permissions to read /sys/kernel/debug/tracing/events/raw_syscalls/sys_(enter|exit)
Hint: Try 'sudo mount -o remount,mode=755 /sys/kernel/debug'
[acme@zoo linux]$ sudo mount -o remount,mode=755 /sys/kernel/debug
[sudo] password for acme:
[acme@zoo linux]$ trace usleep 1
0.095 ( 0.002 ms): usleep/974 brk( ) = 0x7f2dc04fd000
0.112 ( 0.003 ms): usleep/974 mmap(len: 4096, prot: READ|WRITE, flags: PRIVATE|ANONYMOUS, fd: -1 ) = 0x7f2dbf39e000
0.123 ( 0.006 ms): usleep/974 access(filename: 0x7f2dbf19c270, mode: R ) = -1 ENOENT No such file or directory
0.137 ( 0.006 ms): usleep/974 open(filename: 0x7f2dbf19ab92, flags: CLOEXEC ) = 3
0.141 ( 0.002 ms): usleep/974 fstat(fd: 3, statbuf: 0x7ffffabf0d60 ) = 0
0.146 ( 0.004 ms): usleep/974 mmap(len: 98505, prot: READ, flags: PRIVATE, fd: 3 ) = 0x7f2dbf385000
0.148 ( 0.001 ms): usleep/974 close(fd: 3 ) = 0
0.164 ( 0.007 ms): usleep/974 open(filename: 0x7f2dbf39427a, flags: CLOEXEC ) = 3
0.168 ( 0.002 ms): usleep/974 read(fd: 3, buf: 0x7ffffabf0ef0, count: 832 ) = 832
0.171 ( 0.001 ms): usleep/974 fstat(fd: 3, statbuf: 0x7ffffabf0d90 ) = 0
0.179 ( 0.005 ms): usleep/974 mmap(len: 2147728, prot: EXEC|READ, flags: PRIVATE|DENYWRITE, fd: 3 ) = 0x7f2dbef71000
0.188 ( 0.007 ms): usleep/974 mprotect(start: 0x7f2dbef7c000, len: 2097152 ) = 0
0.194 ( 0.005 ms): usleep/974 mmap(addr: 0x7f2dbf17c000, len: 8192, prot: READ|WRITE, flags: PRIVATE|DENYWRITE|FIXED, fd: 3, off: 45056) = 0x7f2dbf17c000
0.205 ( 0.001 ms): usleep/974 close(fd: 3 ) = 0
0.220 ( 0.007 ms): usleep/974 open(filename: 0x7f2dbf39b33b, flags: CLOEXEC ) = 3
0.223 ( 0.002 ms): usleep/974 read(fd: 3, buf: 0x7ffffabf0ec0, count: 832 ) = 832
0.230 ( 0.002 ms): usleep/974 fstat(fd: 3, statbuf: 0x7ffffabf0d60 ) = 0
0.237 ( 0.006 ms): usleep/974 mmap(len: 3919744, prot: EXEC|READ, flags: PRIVATE|DENYWRITE, fd: 3 ) = 0x7f2dbebb4000
0.247 ( 0.009 ms): usleep/974 mprotect(start: 0x7f2dbed67000, len: 2097152 ) = 0
0.255 ( 0.006 ms): usleep/974 mmap(addr: 0x7f2dbef67000, len: 24576, prot: READ|WRITE, flags: PRIVATE|DENYWRITE|FIXED, fd: 3, off: 1781760) = 0x7f2dbef67000
0.273 ( 0.011 ms): usleep/974 mmap(addr: 0x7f2dbef6d000, len: 16256, prot: READ|WRITE, flags: PRIVATE|ANONYMOUS|FIXED, fd: -1) = 0x7f2dbef6d000
0.281 ( 0.001 ms): usleep/974 close(fd: 3 ) = 0
0.291 ( 0.003 ms): usleep/974 mmap(len: 4096, prot: READ|WRITE, flags: PRIVATE|ANONYMOUS, fd: -1 ) = 0x7f2dbf384000
0.306 ( 0.003 ms): usleep/974 mmap(len: 4096, prot: READ|WRITE, flags: PRIVATE|ANONYMOUS, fd: -1 ) = 0x7f2dbf383000
0.311 ( 0.002 ms): usleep/974 mmap(len: 4096, prot: READ|WRITE, flags: PRIVATE|ANONYMOUS, fd: -1 ) = 0x7f2dbf382000
0.316 ( 0.001 ms): usleep/974 arch_prctl(option: 4098, arg2: 139834458388224, arg3: 139834458382352, arg4: 34, arg5: 4294967295) = 0
0.386 ( 0.006 ms): usleep/974 mprotect(start: 0x7f2dbef67000, len: 16384, prot: READ ) = 0
0.396 ( 0.003 ms): usleep/974 mprotect(start: 0x7f2dbf17c000, len: 4096, prot: READ ) = 0
0.407 ( 0.004 ms): usleep/974 mprotect(start: 0x7f2dbf5a3000, len: 4096, prot: READ ) = 0
0.416 ( 0.005 ms): usleep/974 mprotect(start: 0x7f2dbf39f000, len: 4096, prot: READ ) = 0
0.429 ( 0.012 ms): usleep/974 munmap(addr: 0x7f2dbf385000, len: 98505 ) = 0
0.487 ( 0.002 ms): usleep/974 brk( ) = 0x7f2dc04fd000
0.492 ( 0.004 ms): usleep/974 brk(brk: 0x7f2dc051e000 ) = 0x7f2dc051e000
0.495 ( 0.001 ms): usleep/974 brk( ) = 0x7f2dc051e000
0.573 ( 0.059 ms): usleep/974 nanosleep(rqtp: 0x7ffffabf14e0 ) = 0
0.581 ( 0.000 ms): usleep/974 exit_group(
[acme@zoo linux]$
[acme@zoo linux]$ trace --all-cpus
Error: Operation not permitted.
Hint: Check /proc/sys/kernel/perf_event_paranoid setting.
Hint: For system wide tracing it needs to be set to -1.
Hint: Try: 'sudo sh -c "echo -1 > /proc/sys/kernel/perf_event_paranoid"'
Hint: The current value is 1.
[acme@zoo linux]$
Will try to do it soon,
- Arnaldo
> On Mon, May 11, 2015 at 10:14 AM, David Ahern <dsahern@gmail.com> wrote:
> > On 5/11/15 10:57 AM, Alex Newman wrote:
> >>
> >> Hello mailing list friends,
> >>
> >> I am sorry if this is not the best place for this (where should I
> >> report improvements for perf).
> >>
> >> This command works when I have the correct permissions but if I don't
> >> rather than getting "bad permissions" I get
> >>
> >> posix4e@posix4e-P27GV2:~$ perf stat -e 'ext4:' -a
> >
> >
> > that's an invalid event list; it should never work. Did you mean -e
> > 'ext4:*'?
> >
> > David
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-05-11 21:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-11 16:57 Bug Report Alex Newman
2015-05-11 17:14 ` David Ahern
2015-05-11 17:56 ` Alex Newman
2015-05-11 21:42 ` Arnaldo Carvalho de Melo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).