[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091005211123.GF6071@nowhere>
Date: Mon, 5 Oct 2009 23:11:24 +0200
From: Frederic Weisbecker <fweisbec@...il.com>
To: Masami Hiramatsu <mhiramat@...hat.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...e.hu>,
lkml <linux-kernel@...r.kernel.org>,
systemtap <systemtap@...rces.redhat.com>,
DLE <dle-develop@...ts.sourceforge.net>,
Thomas Gleixner <tglx@...utronix.de>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Christoph Hellwig <hch@...radead.org>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
Jim Keniston <jkenisto@...ibm.com>,
"Frank Ch. Eigler" <fche@...hat.com>
Subject: Re: [PATCH tracing/kprobes v2 1/5] tracing/kprobes: Rename special
variables syntax
On Mon, Oct 05, 2009 at 05:05:32PM -0400, Masami Hiramatsu wrote:
> Frederic Weisbecker wrote:
>>> - @global-symbol
>>
>>
>> We could use global-symbol as is. Shadowing between global
>> and local vars could be dealt with scope resolution:
>>
>> function:var
>> file:var
>> file:line:var
>>
>> And throw errors while submitting a shadowed var name, crying until
>> the user defines the scope, only if needed of course (if there are
>> no shadowing detected, we can submit a naked variable name).
>
> Sure, via perf-probe, global/local symbols will be translated into
> @address by debuginfo.
> But without debuginfo, we still need @symbol syntax for accessing
> global defined symbols.
Ah right.
>>> - +|-Offs(ARG)
>>
>> You mean for arg numbers?
>> So we would have +1 for argument 1?
>
> Sorry for confusing you, it is for deref syntax.
Ok :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists