From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] perf tools: Add dlfilter test
Date: Wed, 11 Aug 2021 13:10:22 +0300 [thread overview]
Message-ID: <a02ebcc2-798a-6c0c-60b2-7a90fd12163b@intel.com> (raw)
In-Reply-To: <YRLf0+ij2rNLvdRj@kernel.org>
On 10/08/21 11:21 pm, Arnaldo Carvalho de Melo wrote:
> Em Tue, Aug 10, 2021 at 10:06:13PM +0300, Adrian Hunter escreveu:
>> On 10/08/21 9:32 pm, Arnaldo Carvalho de Melo wrote:
>>> Em Tue, Aug 10, 2021 at 02:48:13PM +0300, Adrian Hunter escreveu:
>>>> Add a perf test to test the dlfilter C API.
>>>>
>>>> A perf.data file is synthesized and then processed by perf script with a
>>>> dlfilter named dlfilter-test-api-v0.so. Also a C file is compiled to
>>>> provide a dso to match the synthesized perf.data file.
>>>
>>> [root@five ~]# perf test dlfilter
>>> 72: dlfilter C API : FAILED!
Should be fixed in V2
prev parent reply other threads:[~2021-08-11 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 11:48 [PATCH 0/5] perf tools: Add dlfilter test Adrian Hunter
2021-08-10 11:48 ` [PATCH 1/5] perf script: Fix unnecessary machine_resolve() Adrian Hunter
2021-08-10 18:25 ` Arnaldo Carvalho de Melo
2021-08-11 10:18 ` Adrian Hunter
2021-08-10 11:48 ` [PATCH 2/5] perf script: Fix --list-dlfilters documentation Adrian Hunter
2021-08-10 18:28 ` Arnaldo Carvalho de Melo
2021-08-10 11:48 ` [PATCH 3/5] perf tools: Amend dlfilter documentation wrt library dependencies Adrian Hunter
2021-08-10 11:48 ` [PATCH 4/5] perf tools: Move perf_dlfilters.h in the source tree Adrian Hunter
2021-08-10 11:48 ` [PATCH 5/5] perf tools: Add dlfilter test Adrian Hunter
2021-08-10 18:32 ` Arnaldo Carvalho de Melo
2021-08-10 19:06 ` Adrian Hunter
2021-08-10 20:21 ` Arnaldo Carvalho de Melo
2021-08-11 10:10 ` Adrian Hunter [this message]
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=a02ebcc2-798a-6c0c-60b2-7a90fd12163b@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@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).