Message-ID: <56795B4A.2000404@huawei.com>
Date: Tue, 22 Dec 2015 22:16:42 +0800
From: "Wangnan (F)" <wangnan0@huawei.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
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
References: <5677F6E3.9050902@huawei.com> <20151221140104.GQ23092@arm.com>
In-Reply-To: <20151221140104.GQ23092@arm.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1119
Lines: 35


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


--
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/