Linux Perf Users
 help / color / mirror / Atom feed
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 11:23:51 -0800	[thread overview]
Message-ID: <aReBx2jFezxbhWt0@google.com> (raw)
In-Reply-To: <CAFjbc8FK_qs9XqMEf5k81VRNCNXSyda=VUSuJwp8LALOq8fGvg@mail.gmail.com>

Hi Pablo,

On Fri, Nov 14, 2025 at 07:12:42PM +0000, Pablo Galindo Salgado wrote:
> One important aspect to have in mind here is that Python 3.13 was the
> first version to add Perf JIT support. In older versions -Xperf_jit is
> a noop. You may want to check for the version in your test and skip if
> the running version of Python is lower or alternatively ensure you
> always run with 3.13+.

Good point.  Is there a better way to check if -Xperf_jit is available
or not other than reading the version number?

Thanks,
Namhyung


  reply	other threads:[~2025-11-14 19:23 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 [this message]
2025-11-14 22:27       ` Pablo Galindo Salgado
2025-11-14 23:27         ` Namhyung Kim
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=aReBx2jFezxbhWt0@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