linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Chun-Tse Shao <ctshao@google.com>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Liang Kan <kan.liang@linux.intel.com>,
	Ze Gao <zegao2021@gmail.com>,
	Yang Jihong <yangjihong1@huawei.com>,
	Weilin Wang <weilin.wang@intel.com>,
	linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2 1/3] perf evsel: Improve the evsel__open_strerror for EBUSY
Date: Mon, 4 Nov 2024 16:01:36 -0800	[thread overview]
Message-ID: <ZylgYE2HXzGpAdKQ@google.com> (raw)
In-Reply-To: <20241101211757.824743-1-ctshao@google.com>

Hello CT,

On Fri, Nov 01, 2024 at 09:17:55PM +0000, Chun-Tse Shao wrote:
> From: Ian Rogers <irogers@google.com>
> 
> The existing EBUSY strerror message is:
> ```
> The sys_perf_event_open() syscall returned with 16 (Device or resource busy) for event (intel_bts//).
> "dmesg | grep -i perf" may provide additional information.
> ```

Just a nitpick.  I'd like to avoid this github markdown style notation
of triple backticks as it doesn't clearly separate code blocks (IMHO)
nor protect anything like '#' sign in the beginning of a line.

I prefer indenting with 2 spaces before and after a blank line.


> The dmesg won't be useful. What is more useful is knowing what
> processes are potentially using the PMU, which some procfs scanning can
> reveal. When parallel testing tests/shell/stat_all_pmu.sh this yields:
> ```
> Testing intel_bts//
> Error:
> The PMU intel_bts counters are busy and in use by another process.
> Possible processes:
> 2585882 perf list
> 2585902 perf list -j -o /tmp/__perf_test.list_output.json.KF9MY
> 2585904 perf list
> 2585911 perf record -e task-clock --filter period > 1 -o /dev/null --quiet true
> 2585912 perf list
> 2585915 perf list
> 2586042 /tmp/perf/perf record -asdg -e cpu-clock -o /tmp/perftool-testsuite_report.dIF/perf_report/perf.data -- sleep 2
> 2589078 perf record -g -e task-clock:u -o - perf test -w noploop
> 2589148 /tmp/perf/perf record --control=fifo:control,ack -e cpu-clock -m 1 sleep 10
> 2589379 perf --buildid-dir /tmp/perf.debug.Umx record --buildid-all -o /tmp/perf.data.YBm /tmp/perf.ex.MD5.ZQW
> 2589568 perf record -o /tmp/__perf_test.program.mtcZH/perf.data --branch-filter any,save_type,u -- perf test -w brstack
> 2589649 perf record --per-thread -o /tmp/__perf_test.perf.data.5d3dc perf test -w thloop
> 2589898 perf record -o /tmp/perf-test-script.BX2b27Dcnj/pp-perf.data --sample-cpu uname
> ```
> Which gets a little closer to finding the issue.
> 
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
>  tools/perf/util/evsel.c | 79 ++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 78 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> index dbf9c8cee3c56..9a5b6a6f8d2e5 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -3286,6 +3286,78 @@ static bool find_process(const char *name)
>  	return ret ? false : true;
>  }
> 
> +static int dump_perf_event_processes(char *msg, size_t size)
> +{
> +	DIR *proc_dir;
> +	struct dirent *proc_entry;
> +	int printed = 0;
> +
> +	proc_dir = opendir(procfs__mountpoint());
> +	if (!proc_dir)
> +		return 0;
> +
> +	/* Walk through the /proc directory. */
> +	while ((proc_entry = readdir(proc_dir)) != NULL) {
> +		char path[PATH_MAX];

Can we use a much smaller buffer as it expects PIDs only?


> +		DIR *fd_dir;
> +		struct dirent *fd_entry;
> +		int fd_dir_fd;
> +
> +		if ((proc_entry->d_type != DT_DIR) ||
> +		     !strcmp(".", proc_entry->d_name) ||
> +		     !strcmp("..", proc_entry->d_name))

Maybe something like this?

		if (proc_entry->d_type != DT_DIR ||
		    !isdigit(proc_entry->d_name[0]) ||
		    strlen(proc_entry->d_name) > sizeof(path) - 4)

Thanks,
Namhyung


> +			continue;
> +
> +		scnprintf(path, sizeof(path), "%s/fd", proc_entry->d_name);
> +		fd_dir_fd = openat(dirfd(proc_dir), path, O_DIRECTORY);
> +		if (fd_dir_fd == -1)
> +			continue;
> +		fd_dir = fdopendir(fd_dir_fd);
> +		if (!fd_dir) {
> +			close(fd_dir_fd);
> +			continue;
> +		}
> +		while ((fd_entry = readdir(fd_dir)) != NULL) {
> +			ssize_t link_size;
> +
> +			if (fd_entry->d_type != DT_LNK)
> +				continue;
> +			link_size = readlinkat(fd_dir_fd, fd_entry->d_name, path, sizeof(path));
> +			if (link_size < 0)
> +				continue;
> +			/* Take care as readlink doesn't null terminate the string. */
> +			if (!strncmp(path, "anon_inode:[perf_event]", link_size)) {
> +				int cmdline_fd;
> +				ssize_t cmdline_size;
> +
> +				scnprintf(path, sizeof(path), "%s/cmdline", proc_entry->d_name);
> +				cmdline_fd = openat(dirfd(proc_dir), path, O_RDONLY);
> +				if (cmdline_fd == -1)
> +					continue;
> +				cmdline_size = read(cmdline_fd, path, sizeof(path) - 1);
> +				close(cmdline_fd);
> +				if (cmdline_size < 0)
> +					continue;
> +				path[cmdline_size] = '\0';
> +				for (ssize_t i = 0; i < cmdline_size; i++) {
> +					if (path[i] == '\0')
> +						path[i] = ' ';
> +				}
> +
> +				if (printed == 0)
> +					printed += scnprintf(msg, size, "Possible processes:\n");
> +
> +				printed += scnprintf(msg + printed, size - printed,
> +						"%s %s\n", proc_entry->d_name, path);
> +				break;
> +			}
> +		}
> +		closedir(fd_dir);
> +	}
> +	closedir(proc_dir);
> +	return printed;
> +}
> +
>  int __weak arch_evsel__open_strerror(struct evsel *evsel __maybe_unused,
>  				     char *msg __maybe_unused,
>  				     size_t size __maybe_unused)
> @@ -3319,7 +3391,7 @@ int evsel__open_strerror(struct evsel *evsel, struct target *target,
>  			printed += scnprintf(msg, size,
>  				"No permission to enable %s event.\n\n", evsel__name(evsel));
> 
> -		return scnprintf(msg + printed, size - printed,
> +		return printed + scnprintf(msg + printed, size - printed,
>  		 "Consider adjusting /proc/sys/kernel/perf_event_paranoid setting to open\n"
>  		 "access to performance monitoring and observability operations for processes\n"
>  		 "without CAP_PERFMON, CAP_SYS_PTRACE or CAP_SYS_ADMIN Linux capability.\n"
> @@ -3382,6 +3454,11 @@ int evsel__open_strerror(struct evsel *evsel, struct target *target,
>  			return scnprintf(msg, size,
>  	"The PMU counters are busy/taken by another profiler.\n"
>  	"We found oprofile daemon running, please stop it and try again.");
> +		printed += scnprintf(
> +			msg, size,
> +			"The PMU %s counters are busy and in use by another process.\n",
> +			evsel->pmu ? evsel->pmu->name : "");
> +		return printed + dump_perf_event_processes(msg + printed, size - printed);
>  		break;
>  	case EINVAL:
>  		if (evsel->core.attr.sample_type & PERF_SAMPLE_CODE_PAGE_SIZE && perf_missing_features.code_page_size)
> --
> 2.47.0.163.g1226f6d8fa-goog
> 

  parent reply	other threads:[~2024-11-05  0:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 21:17 [PATCH v2 1/3] perf evsel: Improve the evsel__open_strerror for EBUSY Chun-Tse Shao
2024-11-01 21:17 ` [PATCH v2 2/3] perf: Reveal PMU type in fdinfo Chun-Tse Shao
2024-11-05  0:12   ` Namhyung Kim
2024-11-06  0:32     ` Chun-Tse Shao
2024-11-01 21:17 ` [PATCH v2 3/3] perf evsel: Find process with busy PMUs for EBUSY Chun-Tse Shao
2024-11-01 21:35   ` Chun-Tse Shao
2024-11-05  0:01 ` Namhyung Kim [this message]
2024-11-06  0:31   ` [PATCH v2 1/3] perf evsel: Improve the evsel__open_strerror " Chun-Tse Shao

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=ZylgYE2HXzGpAdKQ@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ctshao@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=weilin.wang@intel.com \
    --cc=yangjihong1@huawei.com \
    --cc=zegao2021@gmail.com \
    /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).