From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Zumeng Chen <zumeng.chen@gmail.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, paulus@samba.org,
imunsie@au1.ibm.com, linuxppc-dev@lists.ozlabs.org,
romeo.cane.ext@coriant.com
Subject: Re: BUG: perf error on syscalls for powerpc64.
Date: Thu, 16 Jul 2015 18:51:04 -0700 [thread overview]
Message-ID: <20150717015104.GA25558@us.ibm.com> (raw)
In-Reply-To: <CA+Y31wf16voXS6psDUDpNjMFTD8HTMwrdn=sDXC_B1=n7m=1FQ@mail.gmail.com>
Zumeng Chen [zumeng.chen@gmail.com] wrote:
| 3. What I have seen in 3.14.x kernel,
| ======================
| And so far, no more difference to 4.x kernel from me about this part if
| I'm right.
|
| *) With 1028ccf5
|
| perf list|grep -i syscall got me nothing.
|
|
| *) Without 1028ccf5
| root@localhost:~# perf list|grep -i syscall
| syscalls:sys_enter_socket [Tracepoint event]
| syscalls:sys_exit_socket [Tracepoint event]
| syscalls:sys_enter_socketpair [Tracepoint event]
| syscalls:sys_exit_socketpair [Tracepoint event]
| syscalls:sys_enter_bind [Tracepoint event]
| syscalls:sys_exit_bind [Tracepoint event]
| syscalls:sys_enter_listen [Tracepoint event]
| syscalls:sys_exit_listen [Tracepoint event]
| ... ...
Are you seeing this on big-endian or little-endian system?
IIRC, I saw the opposite behavior on an LE system a few months ago.
i.e. without 1028ccf5, 'perf listf|grep syscall' failed.
Applying 1028ccf5, seemed to fix it.
Sukadev
next prev parent reply other threads:[~2015-07-17 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 5:57 BUG: perf error on syscalls for powerpc64 Zumeng Chen
2015-07-16 9:04 ` Michael Ellerman
2015-07-17 1:27 ` Zumeng Chen
2015-07-17 1:51 ` Sukadev Bhattiprolu [this message]
2015-07-17 1:59 ` Ian Munsie
2015-07-18 2:00 ` Zumeng Chen
2015-07-17 5:33 ` Zumeng Chen
2015-07-17 4:07 ` Michael Ellerman
2015-07-17 5:28 ` Zumeng Chen
2015-07-21 6:40 ` Michael Ellerman
2015-07-21 23:00 ` czm
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=20150717015104.GA25558@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=romeo.cane.ext@coriant.com \
--cc=zumeng.chen@gmail.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;
as well as URLs for NNTP newsgroup(s).