Linux Perf Users
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf libunwind: Fix calls to thread__e_machine
Date: Wed, 11 Feb 2026 09:01:46 -0300	[thread overview]
Message-ID: <aYxvqoTR5NGYy1uj@x1> (raw)
In-Reply-To: <20260211053827.140534-1-irogers@google.com>

On Tue, Feb 10, 2026 at 09:38:27PM -0800, Ian Rogers wrote:
> Add the missing e_flags option to fix the build.
> 
> Fixes: 4e66527f8859 ("perf thread: Add optional e_flags output argument to thread__e_machine")
> Signed-off-by: Ian Rogers <irogers@google.com>

Thanks, applied to perf-tools-next,

- Arnaldo
> ---
>  tools/perf/util/unwind-libunwind-local.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/perf/util/unwind-libunwind-local.c b/tools/perf/util/unwind-libunwind-local.c
> index ecf0c01fe51f..5b39ce21e333 100644
> --- a/tools/perf/util/unwind-libunwind-local.c
> +++ b/tools/perf/util/unwind-libunwind-local.c
> @@ -584,7 +584,9 @@ static int access_mem(unw_addr_space_t __maybe_unused as,
>  	}
>  
>  	ret = perf_reg_value(&start, perf_sample__user_regs(ui->sample),
> -			     perf_arch_reg_sp(thread__e_machine(ui->thread, ui->machine)));
> +			     perf_arch_reg_sp(thread__e_machine(ui->thread,
> +								ui->machine,
> +								/*e_flags=*/NULL)));
>  	if (ret)
>  		return ret;
>  
> @@ -733,7 +735,7 @@ static void _unwind__finish_access(struct maps *maps)
>  static int get_entries(struct unwind_info *ui, unwind_entry_cb_t cb,
>  		       void *arg, int max_stack)
>  {
> -	uint16_t e_machine = thread__e_machine(ui->thread, ui->machine);
> +	uint16_t e_machine = thread__e_machine(ui->thread, ui->machine, /*e_flags=*/NULL);
>  	u64 val;
>  	unw_word_t ips[max_stack];
>  	unw_addr_space_t addr_space;
> -- 
> 2.53.0.239.g8d8fc8a987-goog
> 

      reply	other threads:[~2026-02-11 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  5:38 [PATCH v1] perf libunwind: Fix calls to thread__e_machine Ian Rogers
2026-02-11 12:01 ` Arnaldo Carvalho de Melo [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=aYxvqoTR5NGYy1uj@x1 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@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