From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Nakamura Shun <nakamura.shun@fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Rob Herring <robh@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: libperf: lack of interface
Date: Thu, 2 Sep 2021 10:41:56 +0200 [thread overview]
Message-ID: <YTCOVGyffe+VwL6G@krava> (raw)
In-Reply-To: <YS+B6PVHtiTmqZS+@kernel.org>
On Wed, Sep 01, 2021 at 10:36:40AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 01, 2021 at 09:45:10AM +0000, nakamura.shun@fujitsu.com escreveu:
> > Hello.
> >
> > I'm trying to change rdpmc test in perf_event_tests[1] to use libperf, but libperf doesn't have enough interfaces.
> > Does anyone plan to implement any of these libperf features?
> >
> > - Interfaces that can run ioctl (PERF_EVENT_IOC_RESET) from userland
> > - Interfaces that can run fcntl (SIGIO) from userland
hi,
we could add perf_evsel__fd like below, would it help your usecase?
if you described your usecases in more details we could
see if we could add/move something to libperf for that
as Arnaldo said below it could be already in tools/perf/util/*.c
somewhere ;-)
jirka
> >
> > [1] https://github.com/deater/perf_event_tests/tree/master/tests/rdpmc
>
> So, while in this specific case you should probably follow PeterZ's
> advice, feel free to submit patches moving stuff that is in
> tools/perf/util/ to tools/lib/perf/ (libperf) when you have a reasonable
> use case, such as Vince's test suite.
>
> We can then discuss if any adjustment is needed, but doing it this
> piecemeal way, with justification, should be a good way to enrich
> libperf with things that are in quiescent state in tools/perf/util/ and
> that have external users.
>
> Thanks,
>
> - Arnaldo
>
---
tools/lib/perf/evsel.c | 13 +++++++++++++
tools/lib/perf/include/perf/evsel.h | 1 +
2 files changed, 14 insertions(+)
diff --git a/tools/lib/perf/evsel.c b/tools/lib/perf/evsel.c
index d8886720e83d..8cbdaa78749c 100644
--- a/tools/lib/perf/evsel.c
+++ b/tools/lib/perf/evsel.c
@@ -413,3 +413,16 @@ void perf_evsel__free_id(struct perf_evsel *evsel)
zfree(&evsel->id);
evsel->ids = 0;
}
+
+int perf_evsel__fd(struct perf_evsel *evsel, int cpu, int thread)
+{
+ int max_thread = xyarray__max_y(evsel->fd);
+ int max_cpu = xyarray__max_x(evsel->fd);
+
+ if (thread >= max_thread)
+ return -EINVAL;
+ if (cpu >= max_cpu)
+ return -EINVAL;
+
+ return FD(evsel, cpu, thread);
+}
diff --git a/tools/lib/perf/include/perf/evsel.h b/tools/lib/perf/include/perf/evsel.h
index 60eae25076d3..5f29935efcaf 100644
--- a/tools/lib/perf/include/perf/evsel.h
+++ b/tools/lib/perf/include/perf/evsel.h
@@ -39,5 +39,6 @@ LIBPERF_API int perf_evsel__disable_cpu(struct perf_evsel *evsel, int cpu);
LIBPERF_API struct perf_cpu_map *perf_evsel__cpus(struct perf_evsel *evsel);
LIBPERF_API struct perf_thread_map *perf_evsel__threads(struct perf_evsel *evsel);
LIBPERF_API struct perf_event_attr *perf_evsel__attr(struct perf_evsel *evsel);
+LIBPERF_API int perf_evsel__fd(struct perf_evsel *evsel, int cpu, int thread);
#endif /* __LIBPERF_EVSEL_H */
--
2.31.1
next prev parent reply other threads:[~2021-09-02 8:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 9:45 libperf: lack of interface nakamura.shun
2021-09-01 9:57 ` Peter Zijlstra
2021-09-01 13:36 ` Arnaldo Carvalho de Melo
2021-09-02 8:41 ` Jiri Olsa [this message]
2021-09-21 9:46 ` nakamura.shun
2021-10-18 8:57 ` nakamura.shun
2021-10-20 12:20 ` Jiri Olsa
2021-10-22 6:17 ` nakamura.shun
2021-12-03 9:00 ` nakamura.shun
2021-12-07 5:49 ` nakamura.shun
2021-12-07 17:04 ` Jiri Olsa
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=YTCOVGyffe+VwL6G@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=nakamura.shun@fujitsu.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=robh@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 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.