[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150717015104.GA25558@us.ibm.com>
Date: Thu, 16 Jul 2015 18:51:04 -0700
From: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
To: Zumeng Chen <zumeng.chen@...il.com>
Cc: Michael Ellerman <mpe@...erman.id.au>,
linux-kernel@...r.kernel.org, paulus@...ba.org,
imunsie@....ibm.com, linuxppc-dev@...ts.ozlabs.org,
romeo.cane.ext@...iant.com
Subject: Re: BUG: perf error on syscalls for powerpc64.
Zumeng Chen [zumeng.chen@...il.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@...alhost:~# 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists