Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jp_ikaheimonen@mentor.com (JP Ikaheimonen)
Subject: [lttng-dev] [PATCH lttng-tools 00/28] UST Event exclusions
Date: Thu,  7 Nov 2013 12:16:43 +0200	[thread overview]
Message-ID: <1383819403-6386-1-git-send-email-jp_ikaheimonen@mentor.com> (raw)

This patch set, along with a patch set for lttng-ust, implements
a new option for lttng enable-event command.

The new option makes it possible to exclude events from a wildcarded
event definition.

That is, running command

lttng enable-event -u -c c1 'myevents*' -x 'myevents:dbg*'

would enable all UST tracepoint events whose names start with 'myevents'
except those that start with 'myevents:dbg'.

The lttng list command is also updated, so that it points out the
fact that an event has some exclusions.

JP Ikaheimonen (28):
  Add exclusion data to enable-command
  Define a structure for event exclusion data
  Add exclusion data to cmd_enable_event
  Add exclusions to event_ust_enable_tracepoint
  Add event exclusion data to ltt_ust_event structure
  Add exclusion matching logic to trace_ust_ht_match_event
  Add exclusion data to trace_ust_create_event
  Add exclusion data to trace_ust_find_event
  Copy exclusion data in add_unique_ust_event.
  Add new error codes for exclusion processing
  Add handling of LTTNG_ENABLE_EVENT_WITH_EXCLUSION
  Collate handling of LTTNG_ENABLE_EVENT_WITH_FILTER
  Add exclusion data to ust_app_event structure
  Compare also exclusions in ht_match_ust_app_event
  Copy event exclusion data in add_unique_ust_app_event
  Free exclusion data when ust_app_event is deleted
  Add exclusion data to find_ust_app_event
  Copy exclusion data in shadow_copy_event
  Set event exclusions in the target when event is created
  Send enable-event commands with exclusion data
  Collate lttng_enable_event* code
  Add -exclude option to enable-event command
  Add usage for --exclude option
  Add a function to check for legal exclusions
  Parse exclusions and forward them to the control handler
  Detect and report exclusion option errors
  Add exclusion names to diagnostic printouts
  When listing events, show exclusions if they exist

 include/lttng/lttng-error.h              |   2 +
 include/lttng/lttng.h                    |  20 ++-
 src/bin/lttng-sessiond/cmd.c             |  13 +-
 src/bin/lttng-sessiond/cmd.h             |   4 +-
 src/bin/lttng-sessiond/event.c           |  12 +-
 src/bin/lttng-sessiond/event.h           |   3 +-
 src/bin/lttng-sessiond/main.c            | 110 +++++++-----
 src/bin/lttng-sessiond/trace-ust.c       |  23 ++-
 src/bin/lttng-sessiond/trace-ust.h       |  14 +-
 src/bin/lttng-sessiond/ust-app.c         |  95 +++++++++-
 src/bin/lttng-sessiond/ust-app.h         |   2 +
 src/bin/lttng/commands/enable_events.c   | 242 +++++++++++++++++++++++--
 src/bin/lttng/commands/list.c            |  15 +-
 src/common/sessiond-comm/sessiond-comm.h |  22 ++-
 src/lib/lttng-ctl/lttng-ctl.c            | 291 ++++++++++++++++++-------------
 tests/unit/test_ust_data.c               |   2 +-
 16 files changed, 657 insertions(+), 213 deletions(-)

-- 
1.8.1.2




             reply	other threads:[~2013-11-07 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 10:16 JP Ikaheimonen [this message]
2013-11-13 21:07 ` David Goulet
2013-11-14  7:29   ` Ikaheimonen, JP
2013-11-14 14:42     ` Ikaheimonen, JP
2013-11-14 20:52       ` David Goulet
2013-11-15  6:36         ` Ikaheimonen, JP

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=1383819403-6386-1-git-send-email-jp_ikaheimonen@mentor.com \
    --to=jp_ikaheimonen@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