Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Paul_Woegerer@mentor.com (Woegerer, Paul)
Subject: [lttng-dev] [PATCH] tracepoint event exclusion
Date: Wed, 27 Jun 2012 16:08:14 +0200	[thread overview]
Message-ID: <4FEB13CE.1010206@mentor.com> (raw)

Hi,

In order to support situations where a user wants generally all 
tracepoints enabled but specific tracepoints to be suppressed during a 
trace session, I created a small patch that allows us to do the following:

...
lttng enable-event -u -c met_tools -a
lttng enable-event -u -c met_tools --tracepoint '!met_func:*'
lttng enable-event -u -c met_tools --tracepoint '!met_call:*'
...

This has the effect that all tracepoints get recorded except for 
tracepoints that match met_func:* or met_call:*.

If you think this feature is useful for others we would be happy to see 
this patch merged into trunk.

Thanks,
Paul

-- 
Paul Woegerer | SW Development Engineer
Mentor Embedded(tm) | Prinz Eugen Stra?e 72/2/4, Vienna, 1040 Austria
P 43.1.535991320
Nucleus? | Linux? | Android(tm) | Services | UI | Multi-OS

Android is a trademark of Google Inc. Use of this trademark is subject to Google Permissions.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: event_exclusion.patch
Type: text/x-patch
Size: 2157 bytes
Desc: not available
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20120627/3a8a1c68/attachment.bin>


             reply	other threads:[~2012-06-27 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27 14:08 Woegerer, Paul [this message]
2012-06-27 18:33 ` Mathieu Desnoyers
2012-06-28  9:26   ` Woegerer, Paul

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=4FEB13CE.1010206@mentor.com \
    --to=paul_woegerer@mentor.com \
    /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