All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Jing Zhang <renyu.zj@linux.alibaba.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Richter <tmricht@linux.ibm.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	xueshuai@linux.alibaba.com, zhuo.song@linux.alibaba.com
Subject: Re: [PATCH] perf/tests: fix record+probe_libc_inet_pton test on aarch64
Date: Thu, 17 Oct 2024 15:12:36 -0700	[thread overview]
Message-ID: <ZxGL1LF9mVzrUGOU@google.com> (raw)
In-Reply-To: <1728978807-81116-1-git-send-email-renyu.zj@linux.alibaba.com>

Hello,

On Tue, Oct 15, 2024 at 03:53:27PM +0800, Jing Zhang wrote:
> Since commit 1f85d016768f ("perf test record+probe_libc_inet_pton: Fix
> call chain match on x86_64") remove function getaddrinfo() on expected
> file, the test failed on aarch64. On aarch64, function getaddrinfo()
> show up in the call chain.
> 
> $perf script -i /tmp/perf.data.1PV
> ping 2588319 [125] 500119.122843: probe_libc:inet_pton: (ffff9a4f7410)
>             ffff9a4f7410 __GI___inet_pton+0x0 (/usr/lib64/libc-2.32.so)
>             ffff9a4c5f7c getaddrinfo+0xec (/usr/lib64/libc-2.32.so)
>             aaaad6d32b38 [unknown] (/usr/bin/ping)

I'm curious how other ARM folks don't see this.  Does it depend on
something other?  Then can we make the line optional like we did on
s390 recently?

> 
> So just remove getaddrinfo() on x86_64.

I'm not sure how it works on other archs.

Thanks,
Namhyung

> 
> Fixes: 1f85d016768f ("perf test record+probe_libc_inet_pton: Fix call chain match on x86_64")
> Signed-off-by: Jing Zhang <renyu.zj@linux.alibaba.com>
> ---
>  tools/perf/tests/shell/record+probe_libc_inet_pton.sh | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/tools/perf/tests/shell/record+probe_libc_inet_pton.sh b/tools/perf/tests/shell/record+probe_libc_inet_pton.sh
> index 47a26f2..09d7b0b 100755
> --- a/tools/perf/tests/shell/record+probe_libc_inet_pton.sh
> +++ b/tools/perf/tests/shell/record+probe_libc_inet_pton.sh
> @@ -52,8 +52,12 @@ trace_libc_inet_pton_backtrace() {
>  		echo "getaddrinfo\+0x[[:xdigit:]]+[[:space:]]\($libc\)$" >> $expected
>  		echo ".*(\+0x[[:xdigit:]]+|\[unknown\])[[:space:]]\(.*/bin/ping.*\)$" >> $expected
>  		;;
> +	x86_64)
> +		eventattr='max-stack=3'
> +		echo ".*(\+0x[[:xdigit:]]+|\[unknown\])[[:space:]]\(.*/bin/ping.*\)$" >> $expected
>  	*)
>  		eventattr='max-stack=3'
> +		echo "getaddrinfo\+0x[[:xdigit:]]+[[:space:]]\($libc\)$" >> $expected
>  		echo ".*(\+0x[[:xdigit:]]+|\[unknown\])[[:space:]]\(.*/bin/ping.*\)$" >> $expected
>  		;;
>  	esac
> -- 
> 1.8.3.1
> 

  reply	other threads:[~2024-10-17 22:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15  7:53 [PATCH] perf/tests: fix record+probe_libc_inet_pton test on aarch64 Jing Zhang
2024-10-17 22:12 ` Namhyung Kim [this message]
2024-10-20 11:35   ` Leo Yan
2024-10-25 13:20     ` Leo Yan

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=ZxGL1LF9mVzrUGOU@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=renyu.zj@linux.alibaba.com \
    --cc=tmricht@linux.ibm.com \
    --cc=xueshuai@linux.alibaba.com \
    --cc=zhuo.song@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.