From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753841AbaBQKIv (ORCPT <rfc822;w@1wt.eu>);
	Mon, 17 Feb 2014 05:08:51 -0500
Received: from cam-admin0.cambridge.arm.com ([217.140.96.50]:59274 "EHLO
	cam-admin0.cambridge.arm.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1753308AbaBQKIr (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 17 Feb 2014 05:08:47 -0500
Date: Mon, 17 Feb 2014 10:08:27 +0000
From: Will Deacon <will.deacon@arm.com>
To: Weng Meiling <wengmeiling.weng@huawei.com>
Cc: Robert Richter <rric@kernel.org>,
        "oprofile-list@lists.sf.net" <oprofile-list@lists.sf.net>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Li Zefan <lizefan@huawei.com>,
        "wangnan0@huawei.com" <wangnan0@huawei.com>,
        "zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
        Huang Qiang <h.huangqiang@huawei.com>,
        "sdu.liu@huawei.com" <sdu.liu@huawei.com>
Subject: Re: [PATCH] oprofile: check whether oprofile perf enabled in
 op_overflow_handler()
Message-ID: <20140217100827.GA26312@mudshark.cambridge.arm.com>
References: <52D5EC44.30101@huawei.com>
 <20140115102445.GE20315@rric.localhost>
 <52D73148.4090408@huawei.com>
 <52D7A750.50906@huawei.com>
 <20140116115245.GB8360@rric.localhost>
 <20140116193652.GD22105@mudshark.cambridge.arm.com>
 <52D8A56F.1010507@huawei.com>
 <52F9A82F.3060806@huawei.com>
 <20140211155207.GK8693@mudshark.cambridge.arm.com>
 <52FED3C5.1060703@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52FED3C5.1060703@huawei.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sat, Feb 15, 2014 at 02:41:09AM +0000, Weng Meiling wrote:
> Hi Will,
> 
>  I test kernel with this patch, the problem has be fixed. When the
>  event's sample_period is small, the cpu will not stall except printing
>  warning "oprofile: ignoring spurious overflow ignoring spurious overflow".
>  This is normal for unregistered event.
> 
>  So would you please send a formal one? :) Thanks very much!

It's already in -next.

Will