Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753980AbYHSJ1E (ORCPT ); Tue, 19 Aug 2008 05:27:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754880AbYHSJ0p (ORCPT ); Tue, 19 Aug 2008 05:26:45 -0400 Received: from mx2.mail.elte.hu ([157.181.151.9]:43959 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754534AbYHSJ0o (ORCPT ); Tue, 19 Aug 2008 05:26:44 -0400 Date: Tue, 19 Aug 2008 11:25:43 +0200 From: Ingo Molnar To: Peter Zijlstra Cc: Justin Madru , lkml , Michal Januszewski , Antonino Daplas , Greg KH , Rafael Wysocki , Romano Giannetti , Adrian Bunk , Jeremy Nickurak Subject: Re: Backport hr-tick fix into .25/.26 Message-ID: <20080819092543.GD28713@elte.hu> References: <48A9BDC0.9070800@gawab.com> <20080819003110.GH9914@elte.hu> <1219127296.10800.357.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1219127296.10800.357.camel@twins> User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 34 * Peter Zijlstra wrote: > On Tue, 2008-08-19 at 02:31 +0200, Ingo Molnar wrote: > > * Justin Madru wrote: > > > > > This commit introduced the bug. > > > commit 8f4d37ec073c17e2d4aa8851df5837d798606d6f > > > sched: high-res preemption tick > > > > > And this one fixed it > > > > > > commit 31656519e132f6612584815f128c83976a9aaaef > > > sched, x86: clean up hrtick implementation > > > > hm, the backport of 31656519 is a bit intrusive. > > > > find below is an (untested!) version of it - i havent even build-tested > > it. Does it work for you? But this is Greg's call really. > > > > It largely depends on all the new IPI stuff that went into 27 as well, > so I'd be surprised if its easily backportable.. ah, i see. How about a simple patch then that disables hrtick [given that it's now fixed .27 but the fix is too intrusive to backport]? Would that be too risky for -stable? Ingo -- 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/