public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: [PATCH 0/8] tools lib traceevent: Add changes from trace-cmd repo
Date: Fri, 01 Nov 2013 17:53:52 -0400	[thread overview]
Message-ID: <20131101215352.875376844@goodmis.org> (raw)


Arnaldo,

I was looking at the differences between the event-parse.c file in
trace-cmd compared to what's in tools/lib/traceevent, and discovered
that they have diverged a little. I pulled in several patches from
upstream and realized I had some clean ups that I would like to be
added too.

Maybe someday we can get a nice package that puts libtraceevent into
its own .so that can be used by all.

Anyway you can pull this or you can take the patches straight in.
I based off of Linus's 3.12-rc7.

-- Steve


Please pull the latest traceevent/updates tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
traceevent/updates

Head SHA1: 29ad23b00474c34e3b5040dda508c78d33a1a3eb
9ab76c2620680c767771f307e2dc5b152a153350


Howard Cochran (1):
      tools lib traceevent: Handle __print_hex(__get_dynamic_array(fieldname), len)

Steven Rostedt (2):
      tools lib traceevent: Add flags NOHANDLE and PRINTRAW to individual events
      tools lib traceevent: Add pevent_print_func_field() helper function

Steven Rostedt (Red Hat) (4):
      tools lib traceevent: Update printk formats when entered
      tools lib traceevent: If %s is a pointer, check printk formats
      tools lib traceevent: Have bprintk output the same as the kernel does
      tools lib traceevent: Check for spaces in character array

Yoshihiro YUNOMAE (1):
      tools lib traceevent: Add support for extracting trace_clock in report

----
 tools/lib/traceevent/event-parse.c | 165 ++++++++++++++++++++++++++++---------
 tools/lib/traceevent/event-parse.h |  14 +++-
 2 files changed, 136 insertions(+), 43 deletions(-)

             reply	other threads:[~2013-11-01 21:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 21:53 Steven Rostedt [this message]
2013-11-01 21:53 ` [PATCH 1/8] tools lib traceevent: Add support for extracting trace_clock in report Steven Rostedt
2013-11-01 21:53 ` [PATCH 2/8] tools lib traceevent: Update printk formats when entered Steven Rostedt
2013-11-04 20:22   ` [tip:perf/core] " tip-bot for Steven Rostedt (Red Hat)
2013-11-01 21:53 ` [PATCH 3/8] tools lib traceevent: If %s is a pointer, check printk formats Steven Rostedt
2013-11-04 20:22   ` [tip:perf/core] " tip-bot for Steven Rostedt (Red Hat)
2013-11-01 21:53 ` [PATCH 4/8] tools lib traceevent: Handle __print_hex(__get_dynamic_array(fieldname), len) Steven Rostedt
2013-11-01 21:53 ` [PATCH 5/8] tools lib traceevent: Have bprintk output the same as the kernel does Steven Rostedt
2013-11-04 20:23   ` [tip:perf/core] " tip-bot for Steven Rostedt (Red Hat)
2013-11-01 21:53 ` [PATCH 6/8] tools lib traceevent: Check for spaces in character array Steven Rostedt
2013-11-04 20:23   ` [tip:perf/core] " tip-bot for Steven Rostedt (Red Hat)
2013-11-01 21:53 ` [PATCH 7/8] tools lib traceevent: Add flags NOHANDLE and PRINTRAW to individual events Steven Rostedt
2013-11-04 20:23   ` [tip:perf/core] " tip-bot for Steven Rostedt
2013-11-01 21:54 ` [PATCH 8/8] tools lib traceevent: Add pevent_print_func_field() helper function Steven Rostedt
2013-11-04 20:23   ` [tip:perf/core] tools lib traceevent: Add pevent_print_func_field () " tip-bot for Steven Rostedt

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=20131101215352.875376844@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    /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