From: wangnan0@huawei.com (Wangnan (F))
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG REPORT]: ARM64: perf: System hung in perf test
Date: Tue, 22 Dec 2015 22:16:42 +0800 [thread overview]
Message-ID: <56795B4A.2000404@huawei.com> (raw)
In-Reply-To: <20151221140104.GQ23092@arm.com>
On 2015/12/21 22:01, Will Deacon wrote:
> On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
>
[SNIP]
>> # /perf test -v signal
>> 17: Test breakpoint overflow signal handler :
>> --- start ---
>> test child forked, pid 792
>> count1 11, count2 11, overflow 11
>> failed: RF EFLAG recursion issue detected
>> failed: wrong overflow hit
>> failed: wrong count for bp2
>> test child finished with -1
>> ---- end ----
>> Test breakpoint overflow signal handler: FAILED!
> ... and this sounds like the perf tool expecting to single-step over
> signal handlers, whereas (on arm64) we deliberately single-step into
> them, so you can run into a loop for this case.
Could you please provide me more information? Do you think it is
a kernel bug and should be fixed? Or it is an invalid testcase for
aarch64?
Thank you.
> Will
WARNING: multiple messages have this Message-ID (diff)
From: "Wangnan (F)" <wangnan0@huawei.com>
To: Will Deacon <will.deacon@arm.com>
Cc: <guohanjun@huawei.com>, Jiri Olsa <jolsa@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, pi3orama <pi3orama@163.com>,
xiakaixu 00238161 <xiakaixu@huawei.com>
Subject: Re: [BUG REPORT]: ARM64: perf: System hung in perf test
Date: Tue, 22 Dec 2015 22:16:42 +0800 [thread overview]
Message-ID: <56795B4A.2000404@huawei.com> (raw)
In-Reply-To: <20151221140104.GQ23092@arm.com>
On 2015/12/21 22:01, Will Deacon wrote:
> On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
>
[SNIP]
>> # /perf test -v signal
>> 17: Test breakpoint overflow signal handler :
>> --- start ---
>> test child forked, pid 792
>> count1 11, count2 11, overflow 11
>> failed: RF EFLAG recursion issue detected
>> failed: wrong overflow hit
>> failed: wrong count for bp2
>> test child finished with -1
>> ---- end ----
>> Test breakpoint overflow signal handler: FAILED!
> ... and this sounds like the perf tool expecting to single-step over
> signal handlers, whereas (on arm64) we deliberately single-step into
> them, so you can run into a loop for this case.
Could you please provide me more information? Do you think it is
a kernel bug and should be fixed? Or it is an invalid testcase for
aarch64?
Thank you.
> Will
next prev parent reply other threads:[~2015-12-22 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 12:56 [BUG REPORT]: ARM64: perf: System hung in perf test Wangnan (F)
2015-12-21 12:56 ` Wangnan (F)
2015-12-21 14:01 ` Will Deacon
2015-12-21 14:01 ` Will Deacon
2015-12-22 14:16 ` Wangnan (F) [this message]
2015-12-22 14:16 ` Wangnan (F)
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=56795B4A.2000404@huawei.com \
--to=wangnan0@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.