On Thu, Sep 26, 2013 at 9:41 AM, Denys Vlasenko
wrote:
> On Wed, Sep 18, 2013 at 4:33 PM, Arnaldo Carvalho de Melo
> wrote:
>>> The problem: ~100 more tracepoints need to be added merely to get
>>> to the point where strace already is, wrt quality of syscall decoding.
>>> strace has nearly 300 se
On Wed, Sep 18, 2013 at 4:33 PM, Arnaldo Carvalho de Melo
wrote:
>> > Look at the tmp.perf/trace2 branch in my git repo, tglx and Ingo added a
>> > tracepoint to vfs_getname to use that.
>>
>> I know that this is the way how to fetch syscall args without stopping,
>> yes.
>>
>> The problem: ~100 m
Em Wed, Sep 18, 2013 at 01:35:13PM +0200, Denys Vlasenko escreveu:
> On 09/17/2013 09:06 PM, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Sep 17, 2013 at 05:10:55PM +0200, Denys Vlasenko escreveu:
> >> I'm trying to figure out how to extend "perf trace".
> >
> >> Currently, it shows syscall names
* David Ahern wrote:
> On 9/18/13 5:35 AM, Denys Vlasenko wrote:
> >Therefore my question should be restated as:
> >
> >Would perf developers accept the "syscall pausing" feature,
> >or it won't be accepted?
>
> I have been using perf-trace a lot lately specifically because it is
> effectively
On 9/18/13 5:35 AM, Denys Vlasenko wrote:
Therefore my question should be restated as:
Would perf developers accept the "syscall pausing" feature,
or it won't be accepted?
I have been using perf-trace a lot lately specifically because it is
effectively a 'passive' observer of the task (e.g.,
On 09/17/2013 09:06 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 17, 2013 at 05:10:55PM +0200, Denys Vlasenko escreveu:
>> I'm trying to figure out how to extend "perf trace".
>
>> Currently, it shows syscall names and arguments, and only them.
>> Meaning that syscalls such as open(2) are sh
Em Tue, Sep 17, 2013 at 05:10:55PM +0200, Denys Vlasenko escreveu:
> I'm trying to figure out how to extend "perf trace".
> Currently, it shows syscall names and arguments, and only them.
> Meaning that syscalls such as open(2) are shown as:
> open(filename: 140736118412184, flags: 0, mode:
Em Tue, Sep 17, 2013 at 05:10:55PM +0200, Denys Vlasenko escreveu:
> I'm trying to figure out how to extend "perf trace".
> Currently, it shows syscall names and arguments, and only them.
> Meaning that syscalls such as open(2) are shown as:
> open(filename: 140736118412184, flags: 0, mode:
Hi,
I'm trying to figure out how to extend "perf trace".
Currently, it shows syscall names and arguments, and only them.
Meaning that syscalls such as open(2) are shown as:
open(filename: 140736118412184, flags: 0, mode: 140736118403776) = 3
The problem is, of course, that user wants to see
9 matches
Mail list logo
