Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755687AbaJHJSD (ORCPT ); Wed, 8 Oct 2014 05:18:03 -0400 Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:38537 "EHLO cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754565AbaJHJSB (ORCPT ); Wed, 8 Oct 2014 05:18:01 -0400 Date: Wed, 8 Oct 2014 10:17:41 +0100 From: Will Deacon To: zhangzhiqiang Cc: Mark Rutland , "cov@codeaurora.org" , "gregkh@linuxfoundation.org" , "lizefan@huawei.com" , "wangnan0@huawei.com" , "stable@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH] arm: armv7: perf: fix armv7 ref-cycles error Message-ID: <20141008091741.GC26140@arm.com> References: <5434AA24.7010600@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5434AA24.7010600@huawei.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/