From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf intel-pt: Fix 'CPU too large' error
Date: Thu, 7 Jan 2021 15:46:03 -0500 [thread overview]
Message-ID: <225955df-f11f-d627-0690-6864f46151f5@linux.intel.com> (raw)
In-Reply-To: <20210107174159.24897-1-adrian.hunter@intel.com>
On 1/7/2021 12:41 PM, Adrian Hunter wrote:
> In some cases, the number of cpus (nr_cpus_online) is confused with the
> maximum cpu number (nr_cpus_avail), which results in the error in the
> example below:
>
> Example on system with 8 cpus:
>
> Before:
> # echo 0 > /sys/devices/system/cpu/cpu2/online
> # ./perf record --kcore -e intel_pt// taskset --cpu-list 7 uname
> Linux
> [ perf record: Woken up 1 times to write data ]
> [ perf record: Captured and wrote 0.147 MB perf.data ]
> # ./perf script --itrace=e
> Requested CPU 7 too large. Consider raising MAX_NR_CPUS
> 0x25908 [0x8]: failed to process type: 68 [Invalid argument]
>
> After:
> # ./perf script --itrace=e
> #
>
> Fixes: 8c7274691f0d ("perf machine: Replace MAX_NR_CPUS with perf_env::nr_cpus_online")
> Fixes: 7df4e36a4785 ("perf session: Replace MAX_NR_CPUS with perf_env::nr_cpus_online")
> Cc: stable@vger.kernel.org
> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
Tested-by: Kan Liang <kan.liang@linux.intel.com>
Thanks,
Kan
> ---
> tools/perf/util/machine.c | 4 ++--
> tools/perf/util/session.c | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index 1ae32a81639c..46844599d25d 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -2977,7 +2977,7 @@ int machines__for_each_thread(struct machines *machines,
>
> pid_t machine__get_current_tid(struct machine *machine, int cpu)
> {
> - int nr_cpus = min(machine->env->nr_cpus_online, MAX_NR_CPUS);
> + int nr_cpus = min(machine->env->nr_cpus_avail, MAX_NR_CPUS);
>
> if (cpu < 0 || cpu >= nr_cpus || !machine->current_tid)
> return -1;
> @@ -2989,7 +2989,7 @@ int machine__set_current_tid(struct machine *machine, int cpu, pid_t pid,
> pid_t tid)
> {
> struct thread *thread;
> - int nr_cpus = min(machine->env->nr_cpus_online, MAX_NR_CPUS);
> + int nr_cpus = min(machine->env->nr_cpus_avail, MAX_NR_CPUS);
>
> if (cpu < 0)
> return -EINVAL;
> diff --git a/tools/perf/util/session.c b/tools/perf/util/session.c
> index 3b3c50b12791..2777c2df7d87 100644
> --- a/tools/perf/util/session.c
> +++ b/tools/perf/util/session.c
> @@ -2391,7 +2391,7 @@ int perf_session__cpu_bitmap(struct perf_session *session,
> {
> int i, err = -1;
> struct perf_cpu_map *map;
> - int nr_cpus = min(session->header.env.nr_cpus_online, MAX_NR_CPUS);
> + int nr_cpus = min(session->header.env.nr_cpus_avail, MAX_NR_CPUS);
>
> for (i = 0; i < PERF_TYPE_MAX; ++i) {
> struct evsel *evsel;
>
next prev parent reply other threads:[~2021-01-07 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 17:41 [PATCH] perf intel-pt: Fix 'CPU too large' error Adrian Hunter
2021-01-07 20:46 ` Liang, Kan [this message]
2021-01-15 19:33 ` Arnaldo Carvalho de Melo
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=225955df-f11f-d627-0690-6864f46151f5@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox