Skip to contentSkip to conversation

Can tracepoint be listed before app registered?

DISCUSSION Jérémie Galarneau 3 participants 4 messages Mar 7, 2014 – Mar 12, 2014 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 6 lines · zlynus

Hi,
Sorry to bother you guys. The lttng-tool man page dosen't make it clear that when the tracepoints of user-space application can be listed. So I did a little test. As far as I can tell ,the tracepoint information is only available during the application is running.

Correct.

Quoted 9 lines

So is it possible that the tracepoint can be available *before* app get running, specifically, before enable-event subcommand? I think it can be quite convenient to output the list when specify which events to trace. If it is not for now,
maybe it's a feature worth working on. My idea is lttng-tool could read tracer provider library and get the info,and add a option after 'list' subcommand which let user specify the provider library to read. Just a personal opion from a new comer :-)

You can enable an event before the app is started. However, as you pointed out, the session daemon has no knowledge of application events before they are launched.

My understanding of your suggestion is that we should define a public provider API on which the lttng client could hook itself to list events. It would be of limited use in the case of statically linked providers, but It's an interesting problem... Do you have a specific use-case in mind?

Regards,
Jérémie

Quoted 9 lines

Best regards,
Lingyu Zhu

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Signature · 3 lines
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

A message that is not in the archive (sent off-list or not yet received): CA+jJMxtsE91pFis=SQbce0eHWS-vVfAiJg6deyvFSfp=B2WvYQ@mail.gmail.com

#3 lore raw

----- Original Message -----

Quoted 31 lines

From: "Jérémie Galarneau" <[email protected]>
To: "zlynus" <[email protected]>
Cc: "lttng-dev" <[email protected]>
Sent: Friday, March 7, 2014 1:23:01 PM
Subject: Re: [lttng-dev] Can tracepoint be listed before app registered?

Quoted 7 lines · zlynus

Hi,
Sorry to bother you guys. The lttng-tool man page dosen't make it clear that
when the tracepoints of user-space application can be listed. So I did a little test. As far as I can tell ,the tracepoint information is only available during the application is running.

Correct.

Quoted 9 lines

So is it possible that the tracepoint can be available *before* app get running, specifically, before enable-event subcommand? I think it can be quite convenient to output the list when specify which events to trace. If it is not for now,
maybe it's a feature worth working on. My idea is lttng-tool could read tracer provider library and get the info,and add a option after 'list' subcommand which let user specify the provider library to read. Just a personal opion from a new comer :-)

You can enable an event before the app is started. However, as you pointed out, the session daemon has no knowledge of application events before they are launched.

Quoted 5 lines

My understanding of your suggestion is that we should define a public provider API on which the lttng client could hook itself to list events. It would be of limited use in the case of statically linked providers, but It's an interesting problem... Do you have a specific use-case in mind?

Another option that would take care of statically linked providers would be to let a lttng library look at all the executables on the system (or from a certain path in the system), as well as .so, and list a specific "tracepoint provider" section that we could specify. We'd need to parse ELF for this.

Thoughts ?

Thanks,

Mathieu

Quoted 26 lines

Regards,
Jérémie

Quoted 9 lines

Best regards,
Lingyu Zhu

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

--
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Signature · 8 lines
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw
Quoted 40 lines · Mathieu Desnoyers

----- Original Message -----

Quoted 31 lines

From: "Jérémie Galarneau" <[email protected]>
To: "zlynus" <[email protected]>
Cc: "lttng-dev" <[email protected]>
Sent: Friday, March 7, 2014 1:23:01 PM
Subject: Re: [lttng-dev] Can tracepoint be listed before app registered?

Quoted 7 lines · zlynus

Hi,
Sorry to bother you guys. The lttng-tool man page dosen't make it clear that
when the tracepoints of user-space application can be listed. So I did a little test. As far as I can tell ,the tracepoint information is only available during the application is running.

Correct.

Quoted 9 lines

So is it possible that the tracepoint can be available *before* app get running, specifically, before enable-event subcommand? I think it can be quite convenient to output the list when specify which events to trace. If it is not for now,
maybe it's a feature worth working on. My idea is lttng-tool could read tracer provider library and get the info,and add a option after 'list' subcommand which let user specify the provider library to read. Just a personal opion from a new comer :-)

You can enable an event before the app is started. However, as you pointed out, the session daemon has no knowledge of application events before they are launched.

Quoted 5 lines

My understanding of your suggestion is that we should define a public provider API on which the lttng client could hook itself to list events. It would be of limited use in the case of statically linked providers, but It's an interesting problem... Do you have a specific use-case in mind?

Quoted 8 lines

Another option that would take care of statically linked providers would be to let a lttng library look at all the executables on the system (or from a certain path in the system), as well as .so, and list a specific "tracepoint provider" section that we could specify. We'd need to parse ELF for this.

Thoughts ?

I like the idea. Lingyu, would that be something you'd like to propose as a GSoC project?

Regards,
Jérémie

Quoted 35 lines

Thanks,

Mathieu

Quoted 21 lines

Regards,
Jérémie

Quoted 9 lines

Best regards,
Lingyu Zhu

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

--
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

Quoted 5 lines

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

Signature · 3 lines
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

A message that is not in the archive (sent off-list or not yet received): CA+jJMxu_BWt-LO-zfH4V3HA+ONo0-cO0f1TrV26bGOwcq3zHuA@mail.gmail.com

#7 lore raw

Here is the mail I send to Jérémie a few days ago, and I forgot cc to mail list (maybe the mail was rejected):

-------------------------------------------------
So far, I'm not familiar with the detailed implementation of lttng-ust, thus my idea is simple and naive: we can make use of the
tracepoint probe library which generated by lttng-gen-tp or manually by user. Whether the probe library is dynamic or static ,it must contain the tracepoint information.
The use case is as such a scenario:
The target app has defined many events and the user don't want to go over the source code to recall them. Instead, after creating a new session, user issue a hypothetical subcommand 'load_probe' which gather the information from the probe library.And since then, user is able to list all available events yet before any app is launched.

-----------------------------------------------

mathieu 's idea implementing a ELF parser to provide early event-listing feature is a good proposal. However, do you think the quantity of work is plenty enough to be a GSoC proposal? I asked that because I saw some idea was turned down due to 'not complex enough' in some IRC channel.

Lingyu
------------------ Original ------------------

From:  "Jérémie Galarne";<[email protected]>;
Date:  Wed, Mar 12, 2014 03:23 AM
To:  "Mathieu Desnoyers"<[email protected]>; 

Cc: "zlynus"<[email protected]>; "lttng-dev"<[email protected]>;
Subject: Re: [lttng-dev] Can tracepoint be listed before app registered?

Quoted 40 lines · Mathieu Desnoyers

----- Original Message -----

Quoted 31 lines

From: "Jérémie Galarneau" <[email protected]>
To: "zlynus" <[email protected]>
Cc: "lttng-dev" <[email protected]>
Sent: Friday, March 7, 2014 1:23:01 PM
Subject: Re: [lttng-dev] Can tracepoint be listed before app registered?

Quoted 7 lines · zlynus

Hi,
Sorry to bother you guys. The lttng-tool man page dosen't make it clear that
when the tracepoints of user-space application can be listed. So I did a little test. As far as I can tell ,the tracepoint information is only available during the application is running.

Correct.

Quoted 9 lines

So is it possible that the tracepoint can be available *before* app get running, specifically, before enable-event subcommand? I think it can be quite convenient to output the list when specify which events to trace. If it is not for now,
maybe it's a feature worth working on. My idea is lttng-tool could read tracer provider library and get the info,and add a option after 'list' subcommand which let user specify the provider library to read. Just a personal opion from a new comer :-)

You can enable an event before the app is started. However, as you pointed out, the session daemon has no knowledge of application events before they are launched.

Quoted 5 lines

My understanding of your suggestion is that we should define a public provider API on which the lttng client could hook itself to list events. It would be of limited use in the case of statically linked providers, but It's an interesting problem... Do you have a specific use-case in mind?

Quoted 8 lines

Another option that would take care of statically linked providers would be to let a lttng library look at all the executables on the system (or from a certain path in the system), as well as .so, and list a specific "tracepoint provider" section that we could specify. We'd need to parse ELF for this.

Thoughts ?

I like the idea. Lingyu, would that be something you'd like to propose as a GSoC project?

Regards,
Jérémie

Quoted 35 lines

Thanks,

Mathieu

Quoted 21 lines

Regards,
Jérémie

Quoted 9 lines

Best regards,
Lingyu Zhu

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

--
Jérémie Galarneau
EfficiOS Inc.
http://www.efficios.com

Quoted 5 lines

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

Signature · 3 lines
Jérémie Galarneau
EfficiOS Inc.
http://www.efficio

_______________________________________________
lttng-dev mailing list
[email protected]
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev