All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Li Zhijian <zhijianx.li@intel.com>
Cc: linux-kernel@vger.kernel.org, "Li, Philip" <philip.li@intel.com>
Subject: Re: perf test vfs_getname failed
Date: Mon, 23 Oct 2017 11:24:09 -0300	[thread overview]
Message-ID: <20171023142409.GA21936@kernel.org> (raw)
In-Reply-To: <3f9e521d-a90c-72c4-6985-2953bfe20182@intel.com>

Em Mon, Oct 23, 2017 at 05:38:49PM +0800, Li Zhijian escreveu:
> Those cases can be passed on fedora-26 with the same kernel(and configuration) with rhel7.1
> [root@localhost perf]# ./perf test vfs_getname
> 60: Add vfs_getname probe to get syscall args filenames   : Ok
> 61: Use vfs_getname probe to get syscall args filenames   : Ok
> 62: Check open filename arg using perf trace + vfs_getname: Ok
> 
> totally, i tested at 3 distro
> 1. fedora-26: OK
> 2. ubuntu 16.04: FAIL
> 3. rhel7.1 beta: FAIL
> 
> Does it means that those cases are related to special distro(require special middle wares) ?

Nope, its supposed to work with all of them, I'll check and try to fix
it.

- Arnaldo
 
> 
> Thanks
> 
> 
> On 10/19/2017 4:31 PM, Li Zhijian wrote:
> > Hi Arnaldo
> > 
> > i encounter some problem when running perf test, the details arelike
> > below:
> > 
> > -----------------------------
> > 
> > [lizj@rhel71 perf]$ sudo ./perf test vfs_getname -v
> > 61: Add vfs_getname probe to get syscall args filenames   :
> > --- start ---
> > test child forked, pid 5958
> > Failed to find 'result' in this function.
> >   Error: Failed to add events.
> > test child finished with -1
> > ---- end ----
> > Add vfs_getname probe to get syscall args filenames: FAILED!
> > 62: Use vfs_getname probe to get syscall args filenames   :
> > --- start ---
> > test child forked, pid 5979
> > Failed to find 'result' in this function.
> >   Error: Failed to add events.
> > test child finished with -1
> > ---- end ----
> > Use vfs_getname probe to get syscall args filenames: FAILED!
> > 63: Check open filename arg using perf trace + vfs_getname:
> > --- start ---
> > test child forked, pid 6001
> > Failed to find 'result' in this function.
> >   Error: Failed to add events.
> > test child finished with -1
> > ---- end ----
> > Check open filename arg using perf trace + vfs_getname: FAILED!
> > -----------------------------
> > 
> > my environment:
> > 1. perf features
> > the enabled features are:
> > -----------------------------
> > 
> > Auto-detecting system features:
> > ...                         dwarf: [ on  ]
> > ...            dwarf_getlocations: [ on  ]
> > ...                         glibc: [ on  ]
> > ...                          gtk2: [ on  ]
> > ...                      libaudit: [ on  ]
> > ...                        libbfd: [ on  ]
> > ...                        libelf: [ on  ]
> > ...                       libnuma: [ on  ]
> > ...        numa_num_possible_cpus: [ on  ]
> > ...                       libperl: [ on  ]
> > ...                     libpython: [ on  ]
> > ...                      libslang: [ OFF ]
> > ...                     libcrypto: [ on  ]
> > ...                     libunwind: [ on  ]
> > ...            libdw-dwarf-unwind: [ on  ]
> > ...                          zlib: [ on  ]
> > ...                          lzma: [ on  ]
> > ...                     get_cpuid: [ on  ]
> > ...                           bpf: [ on  ]
> > -----------------------------
> > 2. host
> > [lizj@rhel71 perf]$ cat /etc/redhat-release
> > Red Hat Enterprise Linux Server release 7.1 Beta (Maipo)
> > 
> > 3. kernel
> > [lizj@rhel71 perf]$ uname -a
> > Linux rhel71 4.14.0-rc1+ #2 SMP Wed Oct 18 23:49:30 EDT 2017 x86_64
> > x86_64 x86_64 GNU/Linux
> > 
> > if i miss something, fell free to let me know :)
> > 
> > Thanks
> > 
> > Zhijian
> > 
> > 

      reply	other threads:[~2017-10-23 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  8:31 perf test vfs_getname failed Li Zhijian
2017-10-23  9:38 ` Li Zhijian
2017-10-23 14:24   ` Arnaldo Carvalho de Melo [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=20171023142409.GA21936@kernel.org \
    --to=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philip.li@intel.com \
    --cc=zhijianx.li@intel.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.