mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [RFC PATCHSET 0/3] tools lib traceevent: Generic error handling for pevent
Date: Tue, 12 Jun 2012 16:42:36 +0900	[thread overview]
Message-ID: <1339486959-25241-1-git-send-email-namhyung@kernel.org> (raw)

Hi,

This is a small patch series for preparation of the die removal.
I added some error code to be used for pevent_parse_event() and
_strerror function much like the perf target does.

I don't like the name 'pevent' but since it's a part of the API
so I used it for the name.

This can eliminate a few of die() and do_warning() but will lose
some details on the error message - i.e. event name. I couldn't
think of a way that doesn't lose such info after returning from
the function. But I guess we might get the info from the context.

Patch 01 is independent and can be applied separately.

Any comments are welcome.

Thanks,
Namhyung


Namhyung Kim (3):
  tools lib traceevent: Do not link broken field arg for an old ftrace event
  tools lib traceevent: Introduce pevent_errno
  tools lib traceevent: Introduce pevent_strerror

 tools/lib/traceevent/event-parse.c |  104 ++++++++++++++++++++++++++++--------
 tools/lib/traceevent/event-parse.h |   28 +++++++++-
 2 files changed, 107 insertions(+), 25 deletions(-)

-- 
1.7.10.2


             reply	other threads:[~2012-06-12  7:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12  7:42 Namhyung Kim [this message]
2012-06-12  7:42 ` [PATCH 1/3] tools lib traceevent: Do not link broken field arg for an old ftrace event Namhyung Kim
2012-06-12 17:51   ` Steven Rostedt
2012-06-12  7:42 ` [PATCH 2/3] tools lib traceevent: Introduce pevent_errno Namhyung Kim
2012-06-12 17:57   ` Steven Rostedt
2012-06-12  7:42 ` [PATCH 3/3] tools lib traceevent: Introduce pevent_strerror Namhyung Kim
2012-06-12 18:01   ` Steven Rostedt
2012-06-13  3:02     ` Namhyung Kim
2012-06-15  3:27       ` Steven Rostedt
2012-06-15  9:04         ` Namhyung Kim
2012-06-15 12:25           ` Steven Rostedt
2012-06-15 22:18             ` Namhyung Kim
2012-06-15 22:23               ` Steven Rostedt
2012-06-15 12:39   ` Steven Rostedt
2012-06-15 22:25     ` Namhyung Kim
2012-06-15 22:45       ` Steven Rostedt
2012-06-15 22:51         ` Namhyung Kim
2012-06-15 23:03           ` Steven Rostedt
2012-06-12 17:49 ` [RFC PATCHSET 0/3] tools lib traceevent: Generic error handling for pevent Steven Rostedt
2012-06-13  2:57   ` Namhyung Kim

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=1339486959-25241-1-git-send-email-namhyung@kernel.org \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.org \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®