Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761561AbZGIPJ0 (ORCPT ); Thu, 9 Jul 2009 11:09:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761182AbZGIPJE (ORCPT ); Thu, 9 Jul 2009 11:09:04 -0400 Received: from waste.org ([66.93.16.53]:37760 "EHLO waste.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760922AbZGIPJD (ORCPT ); Thu, 9 Jul 2009 11:09:03 -0400 Subject: Re: [PATCH] netpoll: Fix carrier detection for drivers that are using phylib From: Matt Mackall To: Peter Zijlstra Cc: Linus Torvalds , Anton Vorontsov , Andrew Morton , oleg@redhat.com, mingo@elte.hu, linux-kernel@vger.kernel.org, netdev@vger.kernel.org In-Reply-To: <1247151079.12784.10.camel@twins> References: <20090707235812.GA12824@oksana.dev.rtsoft.ru> <20090708005000.GA12380@redhat.com> <1247034263.9777.24.camel@twins> <20090708141024.f8b581c5.akpm@linux-foundation.org> <20090708213331.GA9346@oksana.dev.rtsoft.ru> <20090708144744.5555b88d.akpm@linux-foundation.org> <20090708222003.GA12318@oksana.dev.rtsoft.ru> <1247145977.21295.899.camel@calx> <1247147206.7439.2.camel@twins> <1247149093.21295.915.camel@calx> <1247149862.12784.6.camel@twins> <1247150580.21295.937.camel@calx> <1247151079.12784.10.camel@twins> Content-Type: text/plain Date: Thu, 09 Jul 2009 10:06:08 -0500 Message-Id: <1247151968.21295.947.camel@calx> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 978 Lines: 25 On Thu, 2009-07-09 at 16:51 +0200, Peter Zijlstra wrote: > > Does anything actually use scheduler_running yet? Perhaps my tree is > > old. > > # git grep scheduler_running > kernel/sched.c:static __read_mostly int scheduler_running; > kernel/sched.c: scheduler_running = 1; > kernel/sched_rt.c: if (unlikely(!scheduler_running)) > kernel/sched_rt.c: if (unlikely(!scheduler_running)) > > If memory serves there used to be more, but I think that migrated into > kernel/sched_clock.c, which has sched_clock_running. The static in the first line makes that a bit of a head-scratcher? Oh, I see: it's living in sin. Going to avert my eyes for now. -- http://selenic.com : development and support for Mercurial and Linux -- 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/