linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/5] perf jitdump: Fix PID namespace detection
Date: Wed,  5 Nov 2025 20:10:23 +0100	[thread overview]
Message-ID: <20251105191626.34998-1-iii@linux.ibm.com> (raw)

Hi,

I ran into a problem with perf jitdump not working with still running
namespaced processes and started (very slowly) working on a series that
allows perf to record accurate PID namespace information [1] and use
that instead of resorting to guesswork.

However, I realized that at least short-term it's possible to fix the
existing heuristic, so I've created this series. Patch 1 is the fix.
Patches 2-4 are small changes to the existing test, and patch 5 adds
a test that reproduces the situation that I'm facing.

[1] https://github.com/iii-i/linux/commits/iii/wip/nspid/

Best regards,
Ilya

Ilya Leoshkevich (5):
  perf jitdump: Fix PID namespace detection
  perf test java symbol: Get rid of shellcheck warnings
  perf test java symbol: Extract LIBJVMTI detection
  perf test java symbol: Fix a false negative in symbol regex
  perf test java symbol: Add PID namespace variant

 tools/perf/tests/shell/lib/setup_libjvmti.sh  |  18 +++
 tools/perf/tests/shell/test_java_symbol.sh    |  39 +++--
 .../tests/shell/test_java_symbol_pidns.sh     | 135 ++++++++++++++++++
 tools/perf/util/jitdump.c                     |  27 +++-
 tools/perf/util/namespaces.c                  |   9 ++
 tools/perf/util/namespaces.h                  |   2 +
 6 files changed, 201 insertions(+), 29 deletions(-)
 create mode 100644 tools/perf/tests/shell/lib/setup_libjvmti.sh
 create mode 100755 tools/perf/tests/shell/test_java_symbol_pidns.sh

-- 
2.51.1


             reply	other threads:[~2025-11-05 19:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 19:10 Ilya Leoshkevich [this message]
2025-11-05 19:10 ` [PATCH 1/5] perf jitdump: Fix PID namespace detection Ilya Leoshkevich
2025-11-07  2:16   ` Namhyung Kim
2025-11-07  8:19     ` Ilya Leoshkevich
2025-11-14  8:07       ` Namhyung Kim
2025-11-14 12:44         ` Ilya Leoshkevich
2025-11-14 18:44           ` Namhyung Kim
2025-11-05 19:10 ` [PATCH 2/5] perf test java symbol: Get rid of shellcheck warnings Ilya Leoshkevich
2025-11-07  2:07   ` Namhyung Kim
2025-11-07  7:57     ` Ilya Leoshkevich
2025-11-05 19:10 ` [PATCH 3/5] perf test java symbol: Extract LIBJVMTI detection Ilya Leoshkevich
2025-11-05 19:10 ` [PATCH 4/5] perf test java symbol: Fix a false negative in symbol regex Ilya Leoshkevich
2025-11-07  2:08   ` Namhyung Kim
2025-11-07  7:59     ` Ilya Leoshkevich
2025-11-05 19:10 ` [PATCH 5/5] perf test java symbol: Add PID namespace variant Ilya Leoshkevich

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=20251105191626.34998-1-iii@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=acme@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).