mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Li Zefan <lizf@cn.fujitsu.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Tom Zanussi <tzanussi@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [RFC][GIT PULL] bkl ftrace events + filter regex support
Date: Sat,  1 Aug 2009 09:23:23 +0200	[thread overview]
Message-ID: <1249111408-8657-1-git-send-email-fweisbec@gmail.com> (raw)

Hi everyone,

This patchset provides the support for bkl tracing, with the
support of regex in ftrace filters, so that one can easily filter
the bkl event traces per subsystem/directory/file.

Thanks,
Frederic.


The following changes since commit d34a4debef933061924ee17c2ede33f5c44925fb:
  jolsa@redhat.com (1):
        tracing: Remove .globl in the scripts/recordmcount.pl doc

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git tracing/bkl

Frederic Weisbecker (5):
      tracing/bkl: Add bkl ftrace events
      tracing/event: Cleanup the useless dentry variable
      tracing/filters: Cleanup useless headers
      tracing/filters: Provide basic regex support
      tracing/filters: Provide support for char * pointers

 include/linux/smp_lock.h           |   19 +++-
 include/trace/events/bkl.h         |   61 +++++++++++
 kernel/trace/trace.h               |   33 ++++--
 kernel/trace/trace_events.c        |  106 +++++++++++++++-----
 kernel/trace/trace_events_filter.c |  192 +++++++++++++++++++++++++++++-------
 lib/kernel_lock.c                  |   11 +-
 6 files changed, 340 insertions(+), 82 deletions(-)
 create mode 100644 include/trace/events/bkl.h

             reply	other threads:[~2009-08-01  7:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01  7:23 Frederic Weisbecker [this message]
2009-08-01  7:23 ` [RFC][PATCH 1/5] tracing/bkl: Add bkl ftrace events Frederic Weisbecker
2009-08-01  7:23 ` [RFC][PATCH 2/5] tracing/event: Cleanup the useless dentry variable Frederic Weisbecker
2009-08-01  7:23 ` [RFC][PATCH 3/5] tracing/filters: Cleanup useless headers Frederic Weisbecker
2009-08-03  5:19   ` Li Zefan
2009-08-05 22:30     ` Frederic Weisbecker
2009-08-01  7:23 ` [RFC][PATCH 4/5] tracing/filters: Provide basic regex support Frederic Weisbecker
2009-08-03  5:39   ` Li Zefan
2009-08-05 22:47     ` Frederic Weisbecker
2009-08-06  1:14       ` Li Zefan
2009-08-06  1:49         ` Frederic Weisbecker
2009-08-07  4:14           ` Tom Zanussi
2009-08-07  5:19             ` Frederic Weisbecker
2009-08-07  8:11             ` Peter Zijlstra
2009-08-01  7:23 ` [RFC][PATCH 5/5] tracing/filters: Provide support for char * pointers Frederic Weisbecker
2009-08-03  6:58   ` Li Zefan
2009-08-05 23:02     ` Frederic Weisbecker
2009-08-06  1:35       ` Li Zefan
2009-08-06  1:59         ` Frederic Weisbecker
2009-08-06  3:50           ` Li Zefan

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=1249111408-8657-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tzanussi@gmail.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

Powered by JetHome