From: "Phillips, Kim" <kim.phillips@amd.com>
To: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"jolsa@redhat.com" <jolsa@redhat.com>,
"namhyung@kernel.org" <namhyung@kernel.org>,
"sandipan@linux.ibm.com" <sandipan@linux.ibm.com>,
"mpetlan@redhat.com" <mpetlan@redhat.com>,
"kim.phillips@arm.com" <kim.phillips@arm.com>,
"brueckner@linux.ibm.com" <brueckner@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tests: Fix record+probe_libc_inet_pton.sh for powerpc64
Date: Tue, 2 Jul 2019 15:10:53 +0000 [thread overview]
Message-ID: <dfdd84b7-eb68-cde2-903d-1542e3f80896@amd.com> (raw)
In-Reply-To: <1561630614-3216-1-git-send-email-s1seetee@linux.vnet.ibm.com>
On 6/27/19 5:16 AM, Seeteena Thoufeek wrote:
> 'probe libc's inet_pton & backtrace it with ping' testcase sometimes
> fails on powerpc because distro ping binary does not have symbol
> information and thus it prints "[unknown]" function name in the
> backtrace.
>
> Accept "[unknown]" as valid function name for powerpc as well.
...
> Signed-off-by: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
Fixes: 1632936480a5 ("perf tests: Fix record+probe_libc_inet_pton.sh without ping's debuginfo")
Reviewed-by: Kim Phillips <kim.phillips@amd.com>
Thanks,
Kim
next prev parent reply other threads:[~2019-07-02 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 10:16 [PATCH] perf tests: Fix record+probe_libc_inet_pton.sh for powerpc64 Seeteena Thoufeek
2019-07-02 15:10 ` Phillips, Kim [this message]
2019-07-09 11:31 ` [tip:perf/core] " tip-bot for Seeteena Thoufeek
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=dfdd84b7-eb68-cde2-903d-1542e3f80896@amd.com \
--to=kim.phillips@amd.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brueckner@linux.ibm.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=s1seetee@linux.vnet.ibm.com \
--cc=sandipan@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