From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
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>,
Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH 3/3] tools lib traceevent: Introduce pevent_strerror
Date: Wed, 13 Jun 2012 12:02:51 +0900 [thread overview]
Message-ID: <87ehpj6hic.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1339524114.13377.140.camel@gandalf.stny.rr.com> (Steven Rostedt's message of "Tue, 12 Jun 2012 14:01:54 -0400")
Hi,
On Tue, 12 Jun 2012 14:01:54 -0400, Steven Rostedt wrote:
> On Tue, 2012-06-12 at 16:42 +0900, Namhyung Kim wrote:
>> +int pevent_strerror(struct pevent *pevent, enum pevent_errno errnum,
>> + char *buf, size_t buflen)
>
> Hmm, actually I wonder if we should put the error into the pevent
> structure. Then we wouldn't even need to waste time to pass the data
> through.
>
> That is, you can simply do:
>
> ret = pevent_foo();
> if (ret < 0) {
> pevent_strerr(pevent, buf, buflen);
> printf("%s\n", buf);
> }
>
> Perhaps even include a pevent_perror(), to just do:
>
> if (ret < 0) {
> pevent_perror(pevent);
> return ret;
> }
>
I thought something like this, but worried about the thread-safety. What
about if more than one thread call pevent functions for a same pevent
concurrently? Should we make the pevent->errno TLS?
Thanks,
Namhyung
next prev parent reply other threads:[~2012-06-13 3:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 7:42 [RFC PATCHSET 0/3] tools lib traceevent: Generic error handling for pevent Namhyung Kim
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 [this message]
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=87ehpj6hic.fsf@sejong.aot.lge.com \
--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=namhyung.kim@lge.com \
--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