Date: Mon, 21 Dec 2015 14:01:04 +0000
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
Message-ID: <20151221140104.GQ23092@arm.com>
References: <5677F6E3.9050902@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5677F6E3.9050902@huawei.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1121
Lines: 32

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/