From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: John Garry <john.garry@huawei.com>,
Adrian Hunter <adrian.hunter@intel.com>
Cc: peterz@infradead.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, mingo@redhat.com, irogers@google.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
James Clark <James.Clark@arm.com>
Subject: Re: [PATCH 0/2] perf jevents: Enable build warnings
Date: Wed, 20 Oct 2021 14:25:43 -0300 [thread overview]
Message-ID: <YXBRF0vM8sEwherG@kernel.org> (raw)
In-Reply-To: <744e6d05-eaec-49d9-1e3d-2f96d4e01e1a@huawei.com>
Em Wed, Oct 20, 2021 at 03:41:01PM +0100, John Garry escreveu:
> On 20/10/2021 15:31, Arnaldo Carvalho de Melo wrote:
> > Em Sat, Oct 16, 2021 at 12:48:25AM +0800, John Garry escreveu:
> > > Currently jevents builds without any complier warning flags enabled. So
> > > use newly-defined HOSTCFLAGS, which comes from EXTRA_WARNINGS. I am not
> > > 100% confident that this is the best way, but sending out for review.
> > >
> > > Baseline is be8ecc57f180 (HEAD, acme/perf/core) perf srcline: Use
> > > long-running addr2line per DSO
> >
> > Thanks, applied.
> I was going to send a v2, with changes according to James Clark's review -
> that was to add -Wall & -Werror, but they caused a problem on your perf/core
> branch as they triggered the warn fixed in commit b94729919db2.
> I suppose the best thing now is to send a patch on top once perf/core
> contains that commit. Let me know otherwise.
You can send a v2, as:
29 8.60 debian:experimental-x-mipsel : FAIL gcc version 11.2.0 (Debian 11.2.0-9)
util/intel-pt.c: In function 'intel_pt_synth_pebs_sample':
util/intel-pt.c:2146:33: error: passing argument 1 of 'find_first_bit' from incompatible pointer type [-Werror=incompatible-pointer-types]
2146 | for_each_set_bit(hw_id, &items->applicable_counters, INTEL_PT_MAX_PEBS) {
/git/perf-5.15.0-rc4/tools/include/linux/bitops.h:37:38: note: in definition of macro 'for_each_set_bit'
37 | for ((bit) = find_first_bit((addr), (size)); \
| ^~~~
In file included from /git/perf-5.15.0-rc4/tools/include/asm-generic/bitops.h:21,
from /git/perf-5.15.0-rc4/tools/include/linux/bitops.h:34,
from /git/perf-5.15.0-rc4/tools/include/linux/bitmap.h:6,
from util/header.h:10,
from util/session.h:7,
from util/intel-pt.c:16:
/git/perf-5.15.0-rc4/tools/include/asm-generic/bitops/find.h:109:51: note: expected 'const long unsigned int *' but argument is of type 'const uint64_t *' {aka 'const long long unsigned int *'}
Adrian, this is on:
commit 803a3c9233990e1adac8ea2421e3759c2d380cf8
Author: Adrian Hunter <adrian.hunter@intel.com>
Date: Tue Sep 7 19:39:03 2021 +0300
perf intel-pt: Add support for PERF_RECORD_AUX_OUTPUT_HW_ID
Originally, software only supported redirecting at most one PEBS event to
Intel PT (PEBS-via-PT) because it was not able to differentiate one event
from another. To overcome that, add support for the
PERF_RECORD_AUX_OUTPUT_HW_ID side-band event.
Reviewed-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Reviewed-by: Andi Kleen <ak@linux.intel.com>
That is still just on tmp.perf/core, so we can fix it, probably its just
making that uint64_t into a unsigned long, will check later if you don't
beat me to it.
- Arnaldo
next prev parent reply other threads:[~2021-10-20 17:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 16:48 [PATCH 0/2] perf jevents: Enable build warnings John Garry
2021-10-15 16:48 ` [PATCH 1/2] perf jevents: Fix some would-be warnings John Garry
2021-10-15 16:48 ` [PATCH 2/2] perf jevents: Enable warnings through HOSTCFLAGS John Garry
2021-10-18 10:41 ` James Clark
2021-10-19 8:37 ` John Garry
2021-10-20 14:31 ` [PATCH 0/2] perf jevents: Enable build warnings Arnaldo Carvalho de Melo
2021-10-20 14:41 ` John Garry
2021-10-20 16:34 ` Arnaldo Carvalho de Melo
2021-10-20 17:25 ` Arnaldo Carvalho de Melo [this message]
2021-10-21 20:31 ` [RFC] Support Intel-PT code build in 32-bit arches Arnaldo Carvalho de Melo
2021-10-22 12:23 ` Adrian Hunter
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=YXBRF0vM8sEwherG@kernel.org \
--to=acme@kernel.org \
--cc=James.Clark@arm.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--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=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 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.