From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Naohiro Aota <naota@elisp.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: (ltc-kernel 9923) [PATCH 0/8] perf: Replace strerror with strerror_r for thread-safety
Date: Thu, 14 Aug 2014 11:23:26 +0900 [thread overview]
Message-ID: <53EC1D9E.1090501@hitachi.com> (raw)
In-Reply-To: <20140814022025.3140.33134.stgit@kbuild-fedora.novalocal>
Oops, this is not a complete series... I'll resend same series.
(2014/08/14 11:20), Masami Hiramatsu wrote:
> Hi,
>
> Here is a series to get rid of thread-unsafe strerror() from
> perf tools. Of course, there maybe other thread-unsafe functions,
> so this goes just one step forward. :)
>
> This introduces STRERR_BUFSIZE(=128) macro for allocating local
> buffer, but some strerror_r()s don't use that. If there are
> already a local buffer on the stack, and if it is bigger than
> STRERR_BUFSIZE, I chose it for strerror_r()'s buffer.
>
> By the way, while doing this cleanup, I've found some confusions
> on the code. Currently perf has 3 ways to output messages except
> for standard (f)printf, pr_XXX, ui__XXX and warning/error functions.
> Is there any differences among those APIs? What is the expected
> use cases for them?
> For example, a pure printf is in kvm_live_open_events@builtin-kvm.c
> but it seems to be ui__error, because the error output next to it
> uses that. However, other parts use pr_XXX too. It seems inconsistent.
>
> Thank you,
>
> ---
>
> Masami Hiramatsu (8):
> perf probe: Don't use strerror if strlist__add failed
> perf: Use strerror_r instead of strerror
> perf probe: Make error messages thread-safe
> perf/util: Replace strerror with strerror_r for thread-safety
> perf top: Use strerror_r instead of strerror
> perf trace: Use strerror_r instead of strerror
> perf record: Use strerror_r instead of strerror
> perf test: Use strerror_r instead of strerror
>
>
> tools/perf/builtin-probe.c | 5 +++-
> tools/perf/builtin-record.c | 7 +++---
> tools/perf/builtin-top.c | 2 +-
> tools/perf/builtin-trace.c | 6 +++--
> tools/perf/perf.c | 10 ++++++---
> tools/perf/tests/builtin-test.c | 4 +++
> tools/perf/tests/mmap-basic.c | 7 +++---
> tools/perf/tests/open-syscall-all-cpus.c | 5 +++-
> tools/perf/tests/open-syscall-tp-fields.c | 7 ++++--
> tools/perf/tests/open-syscall.c | 3 ++-
> tools/perf/tests/perf-record.c | 13 ++++++++---
> tools/perf/tests/rdpmc.c | 6 +++--
> tools/perf/tests/sw-clock.c | 6 +++--
> tools/perf/tests/task-exit.c | 6 +++--
> tools/perf/util/cloexec.c | 6 +++--
> tools/perf/util/data.c | 8 +++++--
> tools/perf/util/debug.h | 3 +++
> tools/perf/util/dso.c | 8 +++++--
> tools/perf/util/evlist.c | 2 +-
> tools/perf/util/evsel.c | 7 ++++--
> tools/perf/util/parse-events.c | 5 +++-
> tools/perf/util/probe-event.c | 34 ++++++++++++++++-------------
> tools/perf/util/probe-finder.c | 7 ++++--
> tools/perf/util/run-command.c | 9 ++++++--
> tools/perf/util/util.c | 5 +++-
> 25 files changed, 121 insertions(+), 60 deletions(-)
>
> --
> Masami HIRAMATSU
> Software Platform Research Dept. Linux Technology Research Center
> Hitachi, Ltd., Yokohama Research Laboratory
> E-mail: masami.hiramatsu.pt@hitachi.com
>
>
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
prev parent reply other threads:[~2014-08-14 2:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 2:20 [PATCH 0/8] perf: Replace strerror with strerror_r for thread-safety Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 1/8] perf probe: Don't use strerror if strlist__add failed Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 2/8] perf: Use strerror_r instead of strerror Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 3/8] perf probe: Make error messages thread-safe Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 4/8] perf/util: Replace strerror with strerror_r for thread-safety Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 5/8] perf top: Use strerror_r instead of strerror Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 6/8] perf trace: " Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 7/8] perf record: " Masami Hiramatsu
2014-08-14 2:20 ` [PATCH 8/8] perf test: " Masami Hiramatsu
2014-08-14 2:23 ` Masami Hiramatsu [this message]
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=53EC1D9E.1090501@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naota@elisp.net \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.