From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752593AbbCYFco (ORCPT ); Wed, 25 Mar 2015 01:32:44 -0400 Received: from e32.co.us.ibm.com ([32.97.110.150]:50033 "EHLO e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751018AbbCYFcm (ORCPT ); Wed, 25 Mar 2015 01:32:42 -0400 Message-ID: <5512486C.7080200@linux.vnet.ibm.com> Date: Wed, 25 Mar 2015 11:02:28 +0530 From: Preeti U Murthy 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 , tglx@linutronix.de, mingo@kernel.org CC: linux-kernel@vger.kernel.org, rjw@rjwysocki.net, Michael Ellerman Subject: Re: [PATCH 32/35] clockevents: Fix cpu down race for hrtimer based broadcasting References: <20150216121435.203983131@infradead.org> <20150216122413.880378334@infradead.org> <20150221124659.GG23367@worktop.ger.corp.intel.com> <20150223161457.GA5029@twins.programming.kicks-ass.net> <54EEAFCF.4080208@linux.vnet.ibm.com> <54F02F81.10901@linux.vnet.ibm.com> <20150302145635.GN21418@twins.programming.kicks-ass.net> <5506617B.1060107@linux.vnet.ibm.com> In-Reply-To: <5506617B.1060107@linux.vnet.ibm.com> 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: 15032505-0005-0000-0000-000009AB6B1E Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Ping. On 03/16/2015 10:22 AM, Preeti U Murthy wrote: > 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? >>