linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 10 Aug 2021 22:06:13 +0300	[thread overview]
Message-ID: <e0eba7e7-d9ae-eff4-254c-6fe16809a675@intel.com> (raw)
In-Reply-To: <YRLGTfQdg7pBcf29@kernel.org>

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!
> [root@five ~]# perf test -v dlfilter
> 72: dlfilter C API                                                  :
> --- start ---
> test child forked, pid 3358542
> Checking for gcc
> Command: gcc --version
> gcc (GCC) 11.1.1 20210531 (Red Hat 11.1.1-3)
> Copyright (C) 2021 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> dlfilters path: /var/home/acme/libexec/perf-core/dlfilters
> Command: gcc -g -o /tmp/dlfilter-test-3358542-prog /tmp/dlfilter-test-3358542-prog.c
> Creating new host machine structure
> Command: /var/home/acme/bin/perf script -i /tmp/dlfilter-test-3358542-perf-data --dlfilter /var/home/acme/libexec/perf-core/dlfilters/dlfilter-test-api-v0.so --dlarg first --dlarg 1 --dlarg 4198669 --dlarg 4198662 --dlarg 0 --dlarg last
> Failed with return value 139
> test child finished with -1
> ---- end ----
> dlfilter C API: FAILED!
> [root@five ~]# cat /etc/redhat-release
> Fedora release 34 (Thirty Four)
> [root@five ~]# cat /etc/os-release
> NAME=Fedora
> VERSION="34.20210721.0 (Silverblue)"
> ID=fedora
> VERSION_ID=34
> VERSION_CODENAME=""
> PLATFORM_ID="platform:f34"
> PRETTY_NAME="Fedora 34.20210721.0 (Silverblue)"
> ANSI_COLOR="0;38;2;60;110;180"
> LOGO=fedora-logo-icon
> CPE_NAME="cpe:/o:fedoraproject:fedora:34"
> HOME_URL="https://fedoraproject.org/"
> DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora-silverblue/"
> SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
> BUG_REPORT_URL="https://bugzilla.redhat.com/"
> REDHAT_BUGZILLA_PRODUCT="Fedora"
> REDHAT_BUGZILLA_PRODUCT_VERSION=34
> REDHAT_SUPPORT_PRODUCT="Fedora"
> REDHAT_SUPPORT_PRODUCT_VERSION=34
> PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
> VARIANT="Silverblue"
> VARIANT_ID=silverblue
> OSTREE_VERSION='34.20210721.0'
> [root@five ~]#
> 
> Trying to figure this out...

What does it give with two 'v''s ?
i.e.

perf test -vv dlfilter

  reply	other threads:[~2021-08-10 19:05 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 [this message]
2021-08-10 20:21       ` Arnaldo Carvalho de Melo
2021-08-11 10:10         ` Adrian Hunter

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=e0eba7e7-d9ae-eff4-254c-6fe16809a675@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).