Skip to contentSkip to conversation

Removing timing overhead via tracepoint()

DISCUSSION Mark E. Dawson, Jr. 1 participant 2 messages Sep 26, 2016 – Sep 28, 2016 2 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

All,
Simple question alert!
If I want to remove a ton of compiled-in calls to an "rdtscp-based" C timing function and replace them with conditionally-enabled timing based on whether or not I enable a tracing session, I can do so by adding the aforementioned call as one of the arguments to tracepoint() with our defined provider and event name, correct?

_______________________________________________
lttng-dev mailing list
[email protected]
https://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]

#3 lore raw

ping

From: "Mark E. Dawson, Jr." <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Monday, September 26, 2016 1:32 PM
Subject: Removing timing overhead via tracepoint()

All,
Simple question alert!
If I want to remove a ton of compiled-in calls to an "rdtscp-based" C timing function and replace them with conditionally-enabled timing based on whether or not I enable a tracing session, I can do so by adding the aforementioned call as one of the arguments to tracepoint() with our defined provider and event name, correct?

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