[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141008091741.GC26140@arm.com>
Date: Wed, 8 Oct 2014 10:17:41 +0100
From: Will Deacon <will.deacon@....com>
To: zhangzhiqiang <zhangzhiqiang.zhang@...wei.com>
Cc: Mark Rutland <Mark.Rutland@....com>,
"cov@...eaurora.org" <cov@...eaurora.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"lizefan@...wei.com" <lizefan@...wei.com>,
"wangnan0@...wei.com" <wangnan0@...wei.com>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm: armv7: perf: fix armv7 ref-cycles error
On Wed, Oct 08, 2014 at 04:06:12AM +0100, zhangzhiqiang wrote:
> hi all,
> ----------------------------------------
>
> ref-cycles event is specially to Intel core, but can still used in arm architecture
> with the wrong return value with 3.10 stable. for instance:
>
> perf stat -e ref-cycles sleep 1
>
> Performance counter stats for 'sleep 1':
>
> 0 ref-cycles
>
> 1.002381916 seconds time elapsed
>
> this patch fix the bug and make it return NOT SUPPORTED
> distinctly.
>
> In upstream this bug has been fixed by other way(not primary for the bug), which changes more than one file
> and more than 1000 lines. the primary commit is 6b7658ec8a100b608e59e3cde353434db51f5be0.
> besides we can not simply cherry-pick.
I thought I saw Greg pick this up the other day?
Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists