From: Namhyung Kim <namhyung@kernel.org>
To: 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>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Yunseong Kim <yskelg@gmail.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <ak@linux.intel.com>,
Charlie Jenkins <charlie@rivosinc.com>,
John Garry <john.g.garry@oracle.com>,
Leo Yan <leo.yan@linux.dev>, Michael Petlan <mpetlan@redhat.com>,
Tavian Barnes <tavianator@tavianator.com>,
Veronika Molnarova <vmolnaro@redhat.com>,
coresight@lists.linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] perf libunwind: Fixup conversion perf_sample->user_regs to a pointer
Date: Tue, 18 Mar 2025 11:02:16 -0700 [thread overview]
Message-ID: <174232093676.2542685.15670125863336766245.b4-ty@kernel.org> (raw)
In-Reply-To: <20250313033121.758978-1-irogers@google.com>
On Wed, 12 Mar 2025 20:31:21 -0700, Ian Rogers wrote:
> The dc6d2bc2d893a878 ("perf sample: Make user_regs and intr_regs optional") misses
> the changes to a file, resulting in this problem:
>
> $ make LIBUNWIND=1 -C tools/perf O=/tmp/build/perf-tools-next install-bin
> <SNIP>
> CC /tmp/build/perf-tools-next/util/unwind-libunwind-local.o
> CC /tmp/build/perf-tools-next/util/unwind-libunwind.o
> <SNIP>
> util/unwind-libunwind-local.c: In function ‘access_mem’:
> util/unwind-libunwind-local.c:582:56: error: ‘ui->sample->user_regs’ is a pointer; did you mean to use ‘->’?
> 582 | if (__write || !stack || !ui->sample->user_regs.regs) {
> | ^
> | ->
> util/unwind-libunwind-local.c:587:38: error: passing argument 2 of ‘perf_reg_value’ from incompatible pointer type [-Wincompatible-pointer-types]
> 587 | ret = perf_reg_value(&start, &ui->sample->user_regs,
> | ^~~~~~~~~~~~~~~~~~~~~~
> | |
> | struct regs_dump **
> <SNIP>
> ⬢ [acme@toolbox perf-tools-next]$ git bisect bad
> dc6d2bc2d893a878e7b58578ff01b4738708deb4 is the first bad commit
> commit dc6d2bc2d893a878e7b58578ff01b4738708deb4 (HEAD)
> Author: Ian Rogers <irogers@google.com>
> Date: Mon Jan 13 11:43:45 2025 -0800
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
prev parent reply other threads:[~2025-03-18 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 3:31 Ian Rogers
2025-03-15 1:11 ` Namhyung Kim
2025-03-17 16:02 ` Ian Rogers
2025-03-18 18:02 ` Namhyung Kim [this message]
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=174232093676.2542685.15670125863336766245.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=charlie@rivosinc.com \
--cc=coresight@lists.linaro.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=peterz@infradead.org \
--cc=tavianator@tavianator.com \
--cc=vmolnaro@redhat.com \
--cc=yskelg@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
all inboxes | Powered by JetHome®