From: Namhyung Kim <namhyung@kernel.org>
To: Pablo Galindo Salgado <pablogsal@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 2/2] perf test: Add python JIT dump test
Date: Fri, 14 Nov 2025 15:27:42 -0800 [thread overview]
Message-ID: <aRe67vqAUlIEo90-@google.com> (raw)
In-Reply-To: <CAFjbc8ENz1AhCH0MBMmcrJB34GvjWPjzV3i0PEfnsTAampe8-w@mail.gmail.com>
On Fri, Nov 14, 2025 at 10:27:43PM +0000, Pablo Galindo Salgado wrote:
> The version is likely the more reliable method, but you could use
> sys.is_stack_trampoline_active()
> in combination with the X option. For example:
My concern is platform support. Is it available on ARM and others?
>
> $ python -c 'import sys; print(sys.is_stack_trampoline_active())'
> False
> $ python -Xperf_jit -c 'import sys; print(sys.is_stack_trampoline_active())'
> True
>
> If you get False even when passing Xperf_jit, then it is not supported.
I like this. I guess it'll return False on unsupported archs.
Thanks,
Namhyung
next prev parent reply other threads:[~2025-11-14 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 9:29 [PATCH 1/2] perf jitdump: Add load_addr to build-ID generation Namhyung Kim
2025-11-14 9:29 ` [PATCH 2/2] perf test: Add python JIT dump test Namhyung Kim
2025-11-14 17:44 ` Ian Rogers
2025-11-14 19:03 ` Namhyung Kim
2025-11-14 19:12 ` Pablo Galindo Salgado
2025-11-14 19:23 ` Namhyung Kim
2025-11-14 22:27 ` Pablo Galindo Salgado
2025-11-14 23:27 ` Namhyung Kim [this message]
2025-11-14 23:49 ` Pablo Galindo Salgado
2025-11-14 17:33 ` [PATCH 1/2] perf jitdump: Add load_addr to build-ID generation Ian Rogers
2025-11-14 18:57 ` Namhyung Kim
2025-11-14 19:32 ` Ian Rogers
2025-11-14 23:24 ` Namhyung Kim
2025-11-14 23:58 ` Ian Rogers
2025-11-16 7:22 ` Fangrui Song
2025-11-17 16:58 ` Ian Rogers
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=aRe67vqAUlIEo90-@google.com \
--to=namhyung@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=pablogsal@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