From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, zhlbj@cn.ibm.com
Subject: Re: perf_evlist__filter_pollfd() in trace__run()
Date: Sun, 1 Feb 2015 11:10:25 -0300 [thread overview]
Message-ID: <20150201141025.GG3101@kernel.org> (raw)
In-Reply-To: <20150130201611.GA13679@us.ibm.com>
Em Fri, Jan 30, 2015 at 12:16:11PM -0800, Sukadev Bhattiprolu escreveu:
> Arnaldo Carvalho de Melo [acme@kernel.org] wrote:
> | Em Thu, Jan 29, 2015 at 03:55:22PM -0800, Sukadev Bhattiprolu escreveu:
> | > Should there be another check to before reading the mmap again ?
> |
> | Possibly, checking, but a similar algorithm should be in place for
> | 'record', do you see any problems there? I.e. with 'perf record sleep
> | 1'?
>
> No, I don't see the failure with perf record in several hundred attempts.
> (both the distro and latest perf-core versions work ok).
Ok, so its a matter of comparing what both are doing, will try.
> | > I must add that I don't get the SIGSEGV on recent perf-core and the
> | > system where we get the crash, first runs into the following
> | > errors that we are still looking into (maybe related to "ppc64le"
> | > architecture).
>
> With recent perf core I did not get the SIGSEGV (or the syscall translation
> failures below) on a different system.
>
> But on this system, a power KVM guest, I get both errors even with latest
> perf core (commit c52686f9f88).
>
> | >
> | > Problems reading syscall 45 information
> | > Problems reading syscall 5 information
> | > Problems reading syscall 5 information
> | > Problems reading syscall 108 information
> | > Problems reading syscall 108 information
> | > Problems reading syscall 90 information
> | > Problems reading syscall 90 information
> | > Problems reading syscall 6 information
> | >
> | > Unlike the SIGSEGV, these errors occur always.
>
> Most likely this syscall number translation is due to the
>
> https://fedorahosted.org/audit/browser/trunk/lib/machinetab.h
>
> missing this change set 1013, which added support for ppc64le.
We have to improve that message to mention that perhaps a newer
audit-libs package is required.
- Arnaldo
prev parent reply other threads:[~2015-02-01 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 23:55 perf_evlist__filter_pollfd() in trace__run() Sukadev Bhattiprolu
2015-01-30 15:22 ` Arnaldo Carvalho de Melo
2015-01-30 20:16 ` Sukadev Bhattiprolu
2015-02-01 14:10 ` 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=20150201141025.GG3101@kernel.org \
--to=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=zhlbj@cn.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