From: Namhyung Kim <namhyung@kernel.org>
To: Thomas Richter <tmricht@linux.ibm.com>
Cc: Leo Yan <leo.yan@arm.com>,
Arnaldo Carvalho de Melo <acme@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>,
"Liang, Kan" <kan.liang@linux.intel.com>,
Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Jing Zhang <renyu.zj@linux.alibaba.com>,
Guilherme Amadio <amadio@gentoo.org>
Subject: Re: [PATCH v2] perf test record+probe_libc_inet_pton: Make test resilient
Date: Mon, 2 Dec 2024 12:28:03 -0800 [thread overview]
Message-ID: <Z04YU78EMUWhHtXL@google.com> (raw)
In-Reply-To: <2b3bc88a-e435-4ccc-a543-c8f8566dd306@linux.ibm.com>
Hello,
On Mon, Dec 02, 2024 at 02:48:01PM +0100, Thomas Richter wrote:
> On 12/2/24 12:19, Leo Yan wrote:
> > The test failed back and forth due to the call chain being heavily
> > impacted by the libc, which varies across different architectures and
> > distros.
> >
>
> For s390 using 6.13.0.rc1
>
> Tested-by: Thomas Richter <tmricht@linux.ibm.com>
Thanks for the test, but I think the patch excludes s390 to be safe.
And I think we can test s390 in the same way. If you're willing to do
some more tests, Leo can update the patch to include s390 as well.
Thanks,
Namhyung
>
> --
> Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
> --
> IBM Deutschland Research & Development GmbH
>
> Vorsitzender des Aufsichtsrats: Wolfgang Wendt
>
> Geschäftsführung: David Faller
>
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2024-12-02 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 11:19 [PATCH v2] perf test record+probe_libc_inet_pton: Make test resilient Leo Yan
2024-12-02 13:48 ` Thomas Richter
2024-12-02 20:28 ` Namhyung Kim [this message]
2025-01-03 17:47 ` Leo Yan
2025-01-07 16:51 ` James Clark
2025-01-13 15:50 ` Arnaldo Carvalho de Melo
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=Z04YU78EMUWhHtXL@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=amadio@gentoo.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.com \
--cc=tmricht@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).