From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] to find all the tracepoints by the __start___tracepoints and __stop___tracepoints
Date: Wed, 11 Mar 2009 14:15:07 -0400 [thread overview]
Message-ID: <20090311181506.GA10259@Krystal> (raw)
In-Reply-To: <49B7FA2E.5080900@polymtl.ca>
And given we don't rely on such automagic linker features for the
kernel, include/asm-generic/vmlinux.lds.h specifies :
#define DATA_DATA
...
VMLINUX_SYMBOL(__start___tracepoints) = .; \
*(__tracepoints) \
VMLINUX_SYMBOL(__stop___tracepoints) = .; \
Therefore, as Pierre-Marc says, the linker is responsible for
initialising those symbols.
Mathieu
* Pierre-Marc Fournier (pierre-marc.fournier at polymtl.ca) wrote:
> Hello,
>
> These symbols are automatically placed by the linker at the boundaries
> of the __tracepoints section.
>
> This magic is done in the linker script.
>
> pmf
>
> long xu wrote:
> > Hello,
> >
> > I find when we use the fuction "tracepoint_update_probe_range", it usese
> > the "__start___tracepoints" and "__stop___tracepoints" to find all of
> > the tracepoints. But i don't find where it do the initialisation of the
> > "__start___tracepoints" and "__stop___tracepoints". How can they point
> > the first tracepoint and the last point?
> >
> > Thanks,
> >
> > Best Regard,
> >
> > Long XU
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > ltt-dev mailing list
> > ltt-dev at lists.casi.polymtl.ca
> > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2009-03-11 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 17:36 long xu
2009-03-11 17:36 ` long xu
2009-03-11 17:36 ` long xu
2009-03-11 17:51 ` Pierre-Marc Fournier
2009-03-11 18:15 ` Mathieu Desnoyers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090311181506.GA10259@Krystal \
--to=compudj@krystal.dyndns.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox