From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762610AbZE1Qwf (ORCPT ); Thu, 28 May 2009 12:52:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756302AbZE1Qw2 (ORCPT ); Thu, 28 May 2009 12:52:28 -0400 Received: from fifo99.com ([67.223.236.141]:38488 "EHLO fifo99.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755844AbZE1Qw1 (ORCPT ); Thu, 28 May 2009 12:52:27 -0400 Subject: Re: [PATCH] sched: Support current clocksource handling in fallback sched_clock(). From: Daniel Walker To: Paul Mundt Cc: Peter Zijlstra , Thomas Gleixner , Linus Walleij , Ingo Molnar , Andrew Victor , Haavard Skinnemoen , Andrew Morton , linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk, John Stultz In-Reply-To: <20090528164011.GA30104@linux-sh.org> References: <20090527001543.GA8493@linux-sh.org> <1243441525.28705.19.camel@desktop> <20090528091936.GA27545@linux-sh.org> <1243503281.23657.80.camel@twins> <20090528110902.GA27884@linux-sh.org> <20090528124207.GA28830@linux-sh.org> <1243515570.6600.96.camel@laptop> <1243527218.28705.35.camel@desktop> <1243528329.6645.77.camel@laptop> <20090528164011.GA30104@linux-sh.org> Content-Type: text/plain Date: Thu, 28 May 2009 09:52:27 -0700 Message-Id: <1243529547.28705.43.camel@desktop> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2009-05-29 at 01:40 +0900, Paul Mundt wrote: > On Thu, May 28, 2009 at 06:32:09PM +0200, Peter Zijlstra wrote: > > On Thu, 2009-05-28 at 09:13 -0700, Daniel Walker wrote: > > > On Thu, 2009-05-28 at 14:59 +0200, Peter Zijlstra wrote: > > > > CPU0 CPU1 > > > > > > > > clock = ACCESS_ONCE(sched_clocksource); > > > > > > > > unload module > > > > clocksource_unregister() > > > > sched_clocksource = jiffies > > > > unmap data/text > > > > > > > > cyc2ns(clock, clocksource_read(clock)) <--- fireworks > > > > > > > > > > > > > > Do any module based clocksources even exist right now? > > > clocksource_unregister only seems to be used 3 times.. > > > > Good point, it appears its not even exported. > > > > Thomas mentioned modules, I assumed. > > > The drivers/clocksource/ drivers in theory could be modular anyways. > Handling this transition properly is at least one less barrier to modular > clocksources, so I think it's progress regardless. I don't remember what > all of the other issues were though, John probably remembers. I don't think it's an important case to consider right now .. clocksources are usually so integral to the system putting one in a module seems counterintuitive. Daniel