From: kim.phillips@arm.com (Kim Phillips)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/3] perf tool: Introduce arch-specific supplemental perf open strerror capability
Date: Tue, 24 Oct 2017 20:11:08 -0500 [thread overview]
Message-ID: <20171024201108.0fcc0118cf0c7ccd835c63d6@arm.com> (raw)
In-Reply-To: <20171024133535.GC13445@arm.com>
On Tue, 24 Oct 2017 14:35:35 +0100
Will Deacon <will.deacon@arm.com> wrote:
> On Tue, Oct 24, 2017 at 03:04:04AM -0500, Kim Phillips wrote:
> > Introduce new tools/perf/arch/*/util/evsel.c:perf_evsel__suppl_strerror()
> > so each arch can start to customize usability for its h/w PMU drivers.
> >
> > Signed-off-by: Kim Phillips <kim.phillips@arm.com>
> > ---
> > tools/perf/arch/x86/util/Build | 1 +
> > tools/perf/arch/x86/util/evsel.c | 24 ++++++++++++++++++++++++
> > tools/perf/util/evsel.c | 21 +++++++++++++++------
> > tools/perf/util/evsel.h | 2 ++
> > 4 files changed, 42 insertions(+), 6 deletions(-)
> > create mode 100644 tools/perf/arch/x86/util/evsel.c
>
> This looks sensible to me, although it's difficult to justify all of the
> parameters to perf_evsel__suppl_strerror judging by this patch alone.
I looked at possibly reducing the number of parameters, but since both
evsel and target elements are used to evaluate the condition the error
occurred in, and err, msg, and size are required for basic strerror
functioning, they all look to stay: see the shared strerror function to
see how they're all used.
Thanks,
Kim
next prev parent reply other threads:[~2017-10-25 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 8:04 [RFC 1/3] perf tool: Introduce arch-specific supplemental perf open strerror capability Kim Phillips
2017-10-24 13:35 ` Will Deacon
2017-10-25 1:11 ` Kim Phillips [this message]
2017-10-24 14:27 ` Arnaldo Carvalho de Melo
2017-10-25 1:23 ` Kim Phillips
2017-10-26 2:22 ` Kim Phillips
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=20171024201108.0fcc0118cf0c7ccd835c63d6@arm.com \
--to=kim.phillips@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).