[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1209761165.6929.25.camel@lappy>
Date: Fri, 02 May 2008 22:46:05 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Guillaume Chazarain <guichaz@...il.com>
Cc: Mike Galbraith <efault@....de>, Frans Pop <elendil@...net.nl>,
Parag Warudkar <parag.warudkar@...il.com>,
Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Andi Kleen <andi@...stfloor.org>
Subject: Re: 'global' rq->clock (was Re: Horrendous Audio Stutter - current
git)
On Fri, 2008-05-02 at 22:38 +0200, Guillaume Chazarain wrote:
> On Fri, May 2, 2008 at 9:56 PM, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> > Let me try and come up with something slightly less horrible
>
> Does this obsolete Ingo's "sched: make cpu_clock() globally synchronous"?
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=27ec4407790d075c325e1f4da0a19c56953cce23
>
> My laptop is UP, so I cannot test this :-(
It doesn't, I'm just throwing around code/ideas.
We should probably come up with some clock lib that builds the various
clocks: rq->clock and cpu_clock() from sched_clock() depending on some
architecture supplied hints.
We can toss most of this code on archs like power64, sparc64 and s390x
which have stable clocks. It just seems wrong to do all this on these
archs, but don't have much choice on x86.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists