From: Levi Yun <yeoreum.yun@arm.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, james.clark@linaro.org,
asmadeus@codewreck.org
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
nd@arm.com, Levi Yun <yeoreum.yun@arm.com>
Subject: [PATCH v2 0/2] Minor fixes error handling of perf stat
Date: Fri, 13 Sep 2024 11:14:54 +0100 [thread overview]
Message-ID: <20240913101456.633819-1-yeoreum.yun@arm.com> (raw)
This patchset fixes two issues that were seen when running
"perf stat -r" with perf_event_paranoid=3
1. failed with Too many open files.
$ perf stat -r 1044 -- false
...
failed to create 'go' pipe: Too many open files
failed to prepare workload: Too many open files
...
2. repating error message
$ perf stat -r 1044 -- false
Error:
Access to performance monitoring and observability operations is limited.
...
(repating with same error message 1044 times).
v3:
- Fix comments.
v2:
- Add some comments.
Levi Yun (2):
perf stat: Close cork_fd when create_perf_stat_counter() failed
perf stat: Stop repeating when ref_perf_stat() returns -1
tools/perf/builtin-stat.c | 11 ++++++++++-
tools/perf/util/evlist.c | 14 +++++++++++++-
tools/perf/util/evlist.h | 1 +
3 files changed, 24 insertions(+), 2 deletions(-)
--
LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
next reply other threads:[~2024-09-13 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 10:14 Levi Yun [this message]
2024-09-13 10:14 ` [PATCH v3 1/2] perf stat: Close cork_fd when create_perf_stat_counter() failed Levi Yun
2024-09-13 10:14 ` [PATCH v3 2/2] perf stat: Stop repeating when ref_perf_stat() returns -1 Levi Yun
2024-09-13 13:49 ` James Clark
2024-09-13 13:56 ` Yeo Reum Yun
-- strict thread matches above, loose matches on Subject: below --
2024-09-13 2:02 [PATCH v2 0/2] Minor fixes error handling of perf stat Levi Yun
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=20240913101456.633819-1-yeoreum.yun@arm.com \
--to=yeoreum.yun@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=asmadeus@codewreck.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nd@arm.com \
--cc=peterz@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).