From: Zumeng Chen <zumeng.chen@windriver.com>
To: Ian Munsie <imunsie@au1.ibm.com>, Michael Ellerman <mpe@ellerman.id.au>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
paulus <paulus@samba.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
Zumeng Chen <zumeng.chen@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"romeo.cane.ext" <romeo.cane.ext@coriant.com>
Subject: Re: BUG: perf error on syscalls for powerpc64.
Date: Sat, 18 Jul 2015 10:00:19 +0800 [thread overview]
Message-ID: <55A9B333.4030506@windriver.com> (raw)
In-Reply-To: <1437098328-sup-6685@delenn.ozlabs.ibm.com>
On 2015年07月17日 09:59, Ian Munsie wrote:
> Excerpts from Sukadev Bhattiprolu's message of 2015-07-17 11:51:04 +1000:
>> 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.
> You could be on to something there - IIRC the ABI was changed for LE to
> remove the dot symbols. Might be worth testing on both.
Yeah, thanks Ian for your hints. it should be the dot symbols. So I'll
believe it's good in 4.x, thanks Michael for your patience as well.
Cheers,
Zumeng
>
> Cheers,
> -Ian
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
next prev parent reply other threads:[~2015-07-18 2:00 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
2015-07-17 1:59 ` Ian Munsie
2015-07-18 2:00 ` Zumeng Chen [this message]
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=55A9B333.4030506@windriver.com \
--to=zumeng.chen@windriver.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=sukadev@linux.vnet.ibm.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