On 2015/05/30 10:27, Alexei Starovoitov wrote:
> On 5/29/15 4:55 PM, Masami Hiramatsu wrote:
>> On 2015/05/29 15:30, He Kuang wrote:
>>> hi, Alexei
>>>
>>> On 2015/5/29 2:10, Alexei Starovoitov wrote:
On 5/28/15 6:01 AM, He Kuang wrote:
>> I don't think you can break it down in two steps l
On 5/29/15 4:55 PM, Masami Hiramatsu wrote:
> On 2015/05/29 15:30, He Kuang wrote:
>> hi, Alexei
>>
>> On 2015/5/29 2:10, Alexei Starovoitov wrote:
>>> On 5/28/15 6:01 AM, He Kuang wrote:
> I don't think you can break it down in two steps like this.
>> There is no such thing as 'calling reg
On 2015/05/29 15:30, He Kuang wrote:
> hi, Alexei
>
> On 2015/5/29 2:10, Alexei Starovoitov wrote:
>> On 5/28/15 6:01 AM, He Kuang wrote:
I don't think you can break it down in two steps like this.
> There is no such thing as 'calling regs'. x86_32 with ax,dx,cx
> are not 'calling reg
hi, Alexei
On 2015/5/29 2:10, Alexei Starovoitov wrote:
> On 5/28/15 6:01 AM, He Kuang wrote:
>>> I don't think you can break it down in two steps like this.
There is no such thing as 'calling regs'. x86_32 with ax,dx,cx
are not 'calling regs'. 64-bit values will be passed in a pair.
>>>
On 5/28/15 6:01 AM, He Kuang wrote:
>> I don't think you can break it down in two steps like this.
>> >There is no such thing as 'calling regs'. x86_32 with ax,dx,cx
>> >are not 'calling regs'. 64-bit values will be passed in a pair.
>> >Only 'pt_regs + arch + func_proto + asmlinkage' makes sense
>
On 2015/5/27 23:30, Alexei Starovoitov wrote:
> On 5/26/15 7:27 PM, He Kuang wrote:
>> hi, Alexei
>>
>> On 2015/5/27 1:50, Alexei Starovoitov wrote:
>>> On 5/25/15 1:33 AM, He Kuang wrote:
Right, I learnt regparm(3) is mandatory in x86_32, according to rules,
the first three args will g
On 5/26/15 7:27 PM, He Kuang wrote:
> hi, Alexei
>
> On 2015/5/27 1:50, Alexei Starovoitov wrote:
>> On 5/25/15 1:33 AM, He Kuang wrote:
>>> Right, I learnt regparm(3) is mandatory in x86_32, according to rules,
>>> the first three args will go to regparm(ax, dx, cx). But we should not
>>> refer a
On 2015/05/27 11:27, He Kuang wrote:
> hi, Alexei
>
> On 2015/5/27 1:50, Alexei Starovoitov wrote:
>> On 5/25/15 1:33 AM, He Kuang wrote:
>>> Right, I learnt regparm(3) is mandatory in x86_32, according to rules,
>>> the first three args will go to regparm(ax, dx, cx). But we should not
>>> refer
hi, Alexei
On 2015/5/27 1:50, Alexei Starovoitov wrote:
> On 5/25/15 1:33 AM, He Kuang wrote:
>> Right, I learnt regparm(3) is mandatory in x86_32, according to rules,
>> the first three args will go to regparm(ax, dx, cx). But we should not
>> refer arg1~3 to ax, dx, cx because of 64bit parameter
On 5/25/15 1:33 AM, He Kuang wrote:
> Right, I learnt regparm(3) is mandatory in x86_32, according to rules,
> the first three args will go to regparm(ax, dx, cx). But we should not
> refer arg1~3 to ax, dx, cx because of 64bit parameters (other reasons?).
>
> Consider this keyword is used for gen
On 2015/05/25 21:46, Arnaldo Carvalho de Melo wrote:
> Em Mon, May 25, 2015 at 09:22:50PM +0900, Masami Hiramatsu escreveu:
>> Actually, I'm working on the perf-probe cache enhancement (and it will be
>> perf-cache)
>> which allows you to cache the result of debuginfo analysis under
>> buildid-ca
Em Mon, May 25, 2015 at 09:22:50PM +0900, Masami Hiramatsu escreveu:
> Actually, I'm working on the perf-probe cache enhancement (and it will be
> perf-cache)
> which allows you to cache the result of debuginfo analysis under
> buildid-cache.
> So, if the build-id is same on remote machines, you
On 2015/05/25 17:33, He Kuang wrote:
> hi,
>
> On 2015/5/24 16:49, Masami Hiramatsu wrote:
>> On 2015/05/24 17:28, He Kuang wrote:
>>> When probing at function entry, fallback $params to calling regs if no
>>> debuginfo is provided.
>>>
>>> Before this path:
>>>$ perf probe -v --add='generic_p
hi,
On 2015/5/24 16:49, Masami Hiramatsu wrote:
> On 2015/05/24 17:28, He Kuang wrote:
>> When probing at function entry, fallback $params to calling regs if no
>> debuginfo is provided.
>>
>> Before this path:
>>$ perf probe -v --add='generic_perform_write $params'
>>...
>>Added new e
On 2015/05/24 17:28, He Kuang wrote:
> When probing at function entry, fallback $params to calling regs if no
> debuginfo is provided.
>
> Before this path:
> $ perf probe -v --add='generic_perform_write $params'
> ...
> Added new event:
> Writing event: p:probe/generic_perform_write _stex
When probing at function entry, fallback $params to calling regs if no
debuginfo is provided.
Before this path:
$ perf probe -v --add='generic_perform_write $params'
...
Added new event:
Writing event: p:probe/generic_perform_write _stext+1246632 $params
[86152.161204] Parse error at arg
16 matches
Mail list logo
