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 S1752637AbbCPEwl (ORCPT <rfc822;w@1wt.eu>);
	Mon, 16 Mar 2015 00:52:41 -0400
Received: from e7.ny.us.ibm.com ([32.97.182.137]:44164 "EHLO e7.ny.us.ibm.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751206AbbCPEwj (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 16 Mar 2015 00:52:39 -0400
Message-ID: <5506617B.1060107@linux.vnet.ibm.com>
Date: Mon, 16 Mar 2015 10:22:11 +0530
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Peter Zijlstra <peterz@infradead.org>
CC: tglx@linutronix.de, linux-kernel@vger.kernel.org, mingo@kernel.org,
        rjw@rjwysocki.net, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 32/35] clockevents: Fix cpu down race for hrtimer based
 broadcasting
References: <20150216121435.203983131@infradead.org> <20150216122413.880378334@infradead.org> <alpine.LFD.2.11.1502191124510.22104@knanqh.ubzr> <20150221124659.GG23367@worktop.ger.corp.intel.com> <alpine.LFD.2.11.1502211135230.25484@knanqh.ubzr> <20150223161457.GA5029@twins.programming.kicks-ass.net> <alpine.LFD.2.11.1502231124030.25484@knanqh.ubzr> <alpine.LFD.2.11.1502231214240.25484@knanqh.ubzr> <54EEAFCF.4080208@linux.vnet.ibm.com> <54F02F81.10901@linux.vnet.ibm.com> <20150302145635.GN21418@twins.programming.kicks-ass.net>
In-Reply-To: <20150302145635.GN21418@twins.programming.kicks-ass.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15031604-0037-0000-0000-000000D95A45
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi Peter, Ingo, Thomas,

Can you please take a look at the conversation on this thread ?
This fix is urgent.

Regards
Preeti U Murthy

On 03/02/2015 08:26 PM, Peter Zijlstra wrote:
> On Fri, Feb 27, 2015 at 02:19:05PM +0530, Preeti U Murthy wrote:
>> The problem reported in the changelog of this patch is causing severe
>> regressions very frequently on our machines for certain usecases. It would
>> help to put in a fix in place first and then follow that up with these
>> cleanups.  A fix on the below lines :
> 
> Regression how? Neither Thomas' Changelog, nor yours mention its a
> regression.
> 
> If its a (recent) Regression you need to have a Fixes tag at the very
> least. So when was this broken and by which patch?
>