* Re: system call tracing on sparc
2015-04-09 22:18 system call tracing on sparc David Ahern
@ 2015-04-09 22:21 ` David Ahern
2015-04-09 22:33 ` David Miller
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: David Ahern @ 2015-04-09 22:21 UTC (permalink / raw)
To: sparclinux
On 4/9/15 4:18 PM, David Ahern wrote:
> Dave:
>
> Have you ever used system call tracing on sparc? It does not work for
> 2.6.39 or 4.0; wondering if it has ever worked. I see signs in
> arch/sparc/kernel/syscalls.S for example that suggests it should have at
> one point.
>
To clarify I mean through perf. Using the tracing interface via debugfs
I can get the raw_syscall tracepoints, just not through perf.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: system call tracing on sparc
2015-04-09 22:18 system call tracing on sparc David Ahern
2015-04-09 22:21 ` David Ahern
@ 2015-04-09 22:33 ` David Miller
2015-04-09 22:34 ` David Miller
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: David Miller @ 2015-04-09 22:33 UTC (permalink / raw)
To: sparclinux
From: David Ahern <david.ahern@oracle.com>
Date: Thu, 09 Apr 2015 16:18:48 -0600
> Have you ever used system call tracing on sparc? It does not work for
> 2.6.39 or 4.0; wondering if it has ever worked. I see signs in
> arch/sparc/kernel/syscalls.S for example that suggests it should have
> at one point.
I've used strace in the past, and at the time it worked.
But admittedly this was many years ago.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: system call tracing on sparc
2015-04-09 22:18 system call tracing on sparc David Ahern
2015-04-09 22:21 ` David Ahern
2015-04-09 22:33 ` David Miller
@ 2015-04-09 22:34 ` David Miller
2015-04-10 1:33 ` David Ahern
2015-04-10 2:13 ` David Ahern
4 siblings, 0 replies; 6+ messages in thread
From: David Miller @ 2015-04-09 22:34 UTC (permalink / raw)
To: sparclinux
From: David Ahern <david.ahern@oracle.com>
Date: Thu, 09 Apr 2015 16:21:27 -0600
> On 4/9/15 4:18 PM, David Ahern wrote:
>> Dave:
>>
>> Have you ever used system call tracing on sparc? It does not work for
>> 2.6.39 or 4.0; wondering if it has ever worked. I see signs in
>> arch/sparc/kernel/syscalls.S for example that suggests it should have
>> at
>> one point.
>>
>
> To clarify I mean through perf. Using the tracing interface via
> debugfs I can get the raw_syscall tracepoints, just not through perf.
Oh, I've never tried to use that.
Only the usual syscall tracing faciltiies via ptrace() that programs
like strace make use of.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: system call tracing on sparc
2015-04-09 22:18 system call tracing on sparc David Ahern
` (2 preceding siblings ...)
2015-04-09 22:34 ` David Miller
@ 2015-04-10 1:33 ` David Ahern
2015-04-10 2:13 ` David Ahern
4 siblings, 0 replies; 6+ messages in thread
From: David Ahern @ 2015-04-10 1:33 UTC (permalink / raw)
To: sparclinux
On 4/9/15 4:34 PM, David Miller wrote:
>>> Have you ever used system call tracing on sparc? It does not work for
>>> 2.6.39 or 4.0; wondering if it has ever worked. I see signs in
>>> arch/sparc/kernel/syscalls.S for example that suggests it should have
>>> at
>>> one point.
>>>
>>
>> To clarify I mean through perf. Using the tracing interface via
>> debugfs I can get the raw_syscall tracepoints, just not through perf.
>
> Oh, I've never tried to use that.
>
> Only the usual syscall tracing faciltiies via ptrace() that programs
> like strace make use of.
>
strace works fine, but the overhead of ptrace limits its use for
performance analysis. The entries in the trace facility are not user
friendly:
sshd-14987 [008] 25489.727139: sys_enter: NR 93 (b, 100001c8f10,
100001c8ef0, 0, 0, 0)
sshd-14987 [008] 25489.727141: sys_exit: NR 93 = 93
sshd-14987 [008] 25489.727143: sys_enter: NR 103 (1, 7feff9d8bb8,
7feff9d8c38, 8, fffffc01017d8d4c, 7feff9d8bb8)
sshd-14987 [008] 25489.727144: sys_exit: NR 103 = 103
The point of perf-trace is user friendly output (well, not user friendly
with line wrapping):
1.200 ( 0.023 ms): ls/13344 write(fd: 1, buf: 0x7f023781f000,
count: 90 ) = 90
1.226 ( 0.022 ms): ls/13344 write(fd: 1, buf: 0x7f023781f000,
count: 81 ) = 81
and the low overhead means you can use it to get stats to analyze
performance problems.
I'll ping Frederic and Steve for ideas on where to look.
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: system call tracing on sparc
2015-04-09 22:18 system call tracing on sparc David Ahern
` (3 preceding siblings ...)
2015-04-10 1:33 ` David Ahern
@ 2015-04-10 2:13 ` David Ahern
4 siblings, 0 replies; 6+ messages in thread
From: David Ahern @ 2015-04-10 2:13 UTC (permalink / raw)
To: sparclinux
On 4/9/15 4:21 PM, David Ahern wrote:
>> Have you ever used system call tracing on sparc? It does not work for
>> 2.6.39 or 4.0; wondering if it has ever worked. I see signs in
>> arch/sparc/kernel/syscalls.S for example that suggests it should have at
>> one point.
>>
>
> To clarify I mean through perf. Using the tracing interface via debugfs
> I can get the raw_syscall tracepoints, just not through perf.
hmmm... nevermind. It does work on 4.0 (too many perf problems and too
many kernel versions). I'll figure out when it started working.
^ permalink raw reply [flat|nested] 6+ messages in thread