From: James Clark <james.clark@arm.com>
To: Chaitanya S Prakash <ChaitanyaS.Prakash@arm.com>,
linux-perf-users@vger.kernel.org
Cc: anshuman.khandual@arm.com,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Arnaldo Carvalho de Melo" <acme@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>, "Ian Rogers" <irogers@google.com>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Georg Müller" <georgmueller@gmx.net>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Liam Howlett" <liam.howlett@oracle.com>,
"Athira Rajeev" <atrajeev@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] perf tools: Fix test "perf probe of function from different CU"
Date: Tue, 20 Feb 2024 10:16:29 +0000 [thread overview]
Message-ID: <7df55836-f782-3765-d8eb-67b6ae6a3bc4@arm.com> (raw)
In-Reply-To: <20240220042957.2022391-1-ChaitanyaS.Prakash@arm.com>
On 20/02/2024 04:29, Chaitanya S Prakash wrote:
> From: Chaitanya S Prakash <chaitanyas.prakash@arm.com>
>
> Defconfig doesn't provide all the necessary configs required for the
> test "perf probe of function from different CU" to run successfully on
> all platforms. Therefore the required configs have been added to
> config fragments to resolve this issue. On further investigation it was
> seen that the Perf treated all files beginning with "/tmp/perf-" as a
> map file despite them always ending in ".map", this caused the test to
> fail when Perf was built with NO_DWARF=1. As the file was parsed as a
> map file, the probe...--funcs command output garbage values instead of
> listing the functions in the binary. After fixing the issue an
> additional check to test the output of the probe...--funcs command has
> been added.
>
> This patch series has been tested on 6.8-rc3 mainline kernerl, both on
> arm64 and x86 platforms.
>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>
> Cc: Jiri Olsa <jolsa@kernel.org>
> Cc: Ian Rogers <irogers@google.com>
> Cc: Adrian Hunter <adrian.hunter@intel.com>
> Cc: James Clark <james.clark@arm.com>
> Cc: Georg Müller <georgmueller@gmx.net>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> Cc: Liam Howlett <liam.howlett@oracle.com>
> Cc: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> Cc: linux-perf-users@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
>
> Chaitanya S Prakash (3):
> perf tools: Enable configs required for
> test_uprobe_from_different_cu.sh
> perf tools: Only treat files as map files when they have the extension
> .map
> perf test: Check output of the probe ... --funcs command
>
> tools/perf/builtin-script.c | 15 +--------------
> tools/perf/tests/config-fragments/config | 3 +++
> .../shell/test_uprobe_from_different_cu.sh | 2 +-
> tools/perf/util/string.c | 18 ++++++++++++++++++
> tools/perf/util/string2.h | 1 +
> tools/perf/util/symbol.c | 5 ++++-
> 6 files changed, 28 insertions(+), 16 deletions(-)
>
Reviewed-by: James Clark <james.clark@arm.com>
next prev parent reply other threads:[~2024-02-20 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 4:29 Chaitanya S Prakash
2024-02-20 10:16 ` James Clark [this message]
[not found] ` <20240220042957.2022391-3-ChaitanyaS.Prakash@arm.com>
[not found] ` <CAP-5=fUFmeoTjLuZTgcaV23iGQU1AdddG+7Rw=d6buMU007+1Q@mail.gmail.com>
2024-02-21 14:58 ` [PATCH 2/3] perf tools: Only treat files as map files when they have the extension .map Arnaldo Carvalho de Melo
2024-02-23 12:10 ` Chaitanya S Prakash
2024-03-15 20:34 ` Arnaldo Carvalho de Melo
2024-03-19 2:26 ` Chaitanya S Prakash
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=7df55836-f782-3765-d8eb-67b6ae6a3bc4@arm.com \
--to=james.clark@arm.com \
--cc=ChaitanyaS.Prakash@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=georgmueller@gmx.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@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
all inboxes | Powered by JetHome®