From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG REPORT]: ARM64: perf: System hung in perf test
Date: Mon, 21 Dec 2015 14:01:04 +0000 [thread overview]
Message-ID: <20151221140104.GQ23092@arm.com> (raw)
In-Reply-To: <5677F6E3.9050902@huawei.com>
On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
> System hung can be reproduced on qemu and real hardware using:
>
> # perf test -v signal
>
> If qemu is started with '-smp 1', system hung. In real hardware and in
> qemu with smp > 1, the result is:
That sounds like a qemu issue...
> # /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.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: "Wangnan (F)" <wangnan0@huawei.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: Mon, 21 Dec 2015 14:01:04 +0000 [thread overview]
Message-ID: <20151221140104.GQ23092@arm.com> (raw)
In-Reply-To: <5677F6E3.9050902@huawei.com>
On Mon, Dec 21, 2015 at 08:56:03PM +0800, Wangnan (F) wrote:
> System hung can be reproduced on qemu and real hardware using:
>
> # perf test -v signal
>
> If qemu is started with '-smp 1', system hung. In real hardware and in
> qemu with smp > 1, the result is:
That sounds like a qemu issue...
> # /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.
Will
next prev parent reply other threads:[~2015-12-21 14:01 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 [this message]
2015-12-21 14:01 ` Will Deacon
2015-12-22 14:16 ` Wangnan (F)
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=20151221140104.GQ23092@arm.com \
--to=will.deacon@arm.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.