From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Mao Han <han_mao@c-sky.com>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v3 1/3] perf: use hweight64 instead of hweight_long
Date: Wed, 10 Apr 2019 10:08:41 -0300 [thread overview]
Message-ID: <20190410130841.GE13888@kernel.org> (raw)
In-Reply-To: <29ad7947dc8fd1ff0abd2093a72cc27a2446be9f.1554883878.git.han_mao@c-sky.com>
Em Wed, Apr 10, 2019 at 04:16:43PM +0800, Mao Han escreveu:
> On 32-bits platform with more than 32 registers, the 64 bits mask is
> truncate to the lower 32 bits and the return value of hweight_long will
> always smaller than 32. When kernel outputs more than 32 registers, but
> the user perf program only counts 32, there will be a data mismatch
> result to overflow check fail.
>
> CC: Peter Zijlstra <peterz@infradead.org>
> CC: Ingo Molnar <mingo@redhat.com>
> CC: Arnaldo Carvalho de Melo <acme@kernel.org>
> CC: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> CC: Jiri Olsa <jolsa@redhat.com>
> CC: Namhyung Kim <namhyung@kernel.org>
>
> Signed-off-by: Mao Han <han_mao@c-sky.com>
> ---
> tools/perf/util/evsel.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
> index 7835e05..73c78be 100644
> --- a/tools/perf/util/evsel.c
> +++ b/tools/perf/util/evsel.c
> @@ -2322,7 +2322,7 @@ int perf_evsel__parse_sample(struct perf_evsel *evsel, union perf_event *event,
> if (data->user_regs.abi) {
> u64 mask = evsel->attr.sample_regs_user;
>
> - sz = hweight_long(mask) * sizeof(u64);
> + sz = hweight64(mask) * sizeof(u64);
> OVERFLOW_CHECK(array, sz, max_size);
> data->user_regs.mask = mask;
> data->user_regs.regs = (u64 *)array;
Later on, in the same function, perf_evsel__parse_sample() we have:
data->intr_regs.abi = PERF_SAMPLE_REGS_ABI_NONE;
if (type & PERF_SAMPLE_REGS_INTR) {
OVERFLOW_CHECK_u64(array);
data->intr_regs.abi = *array;
array++;
if (data->intr_regs.abi != PERF_SAMPLE_REGS_ABI_NONE) {
u64 mask = evsel->attr.sample_regs_intr;
sz = hweight_long(mask) * sizeof(u64);
OVERFLOW_CHECK(array, sz, max_size);
data->intr_regs.mask = mask;
data->intr_regs.regs = (u64 *)array;
array = (void *)array + sz;
}
}
You forgot to convert that one, doing it for you,
Thanks,
- Arnaldo
next prev parent reply other threads:[~2019-04-10 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 8:16 [PATCH v3 0/3] csky: perf callchain dwarf support Mao Han
2019-04-10 8:16 ` [PATCH v3 1/3] perf: use hweight64 instead of hweight_long Mao Han
2019-04-10 13:08 ` Arnaldo Carvalho de Melo [this message]
2019-04-10 13:10 ` Arnaldo Carvalho de Melo
2019-04-10 13:28 ` Arnaldo Carvalho de Melo
2019-04-11 7:40 ` Mao Han
2019-04-12 16:40 ` [tip:perf/urgent] perf evsel: Use hweight64() instead of hweight_long(attr.sample_regs_user) tip-bot for Mao Han
2019-04-16 15:30 ` tip-bot for Mao Han
2019-04-10 8:16 ` [PATCH v3 2/3] csky: Add support for perf registers sampling Mao Han
2019-04-10 8:16 ` [PATCH v3 3/3] csky: add support for libdw Mao Han
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=20190410130841.GE13888@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=han_mao@c-sky.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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