From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754106AbbAEN77 (ORCPT ); Mon, 5 Jan 2015 08:59:59 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:54928 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753806AbbAEN76 (ORCPT ); Mon, 5 Jan 2015 08:59:58 -0500 Date: Mon, 5 Jan 2015 14:59:42 +0100 From: Peter Zijlstra To: Mike Galbraith Cc: mingo@kernel.org, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org Subject: Re: [RFC][PATCH 0/3] sched: skip_clock_update madness Message-ID: <20150105135942.GE29390@twins.programming.kicks-ass.net> References: <20150105101809.860964488@infradead.org> <1420454949.5266.138.camel@marge.simpson.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1420454949.5266.138.camel@marge.simpson.net> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 05, 2015 at 11:49:09AM +0100, Mike Galbraith wrote: > On Mon, 2015-01-05 at 11:18 +0100, Peter Zijlstra wrote: > > Hi, > > > > So the big lockup thread got me looking at the skip_clock_update stuff again > > and here's what I came up with. > > > > It seems to build a kernel without generating lockdep splats. > > > > Mike can you see if it cures the wobblies you were seeing? > > Nope, those hiccups were production IO beasts from hell staying in the > kernel for ages at a time. Watchdog being falsely credited with what is > usually dinky wakeup -> switch delta throttled it effectively forever. OK, fair enough. Does the thing otherwise look sane to you?