[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071207175754.GB19173@elte.hu>
Date: Fri, 7 Dec 2007 18:57:54 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Guillaume Chazarain <guichaz@...oo.fr>
Cc: stefano.brivio@...imi.it, Nick Piggin <nickpiggin@...oo.com.au>,
Robert Love <rml@...h9.net>, linux-kernel@...r.kernel.org,
Dave Jones <davej@...hat.com>,
"Rafael J. Wysocki" <rjw@...k.pl>, Michael Buesch <mb@...sch.de>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Len Brown <lenb@...nel.org>
Subject: Re: [PATCH] scheduler: fix x86 regression in native_sched_clock
* Guillaume Chazarain <guichaz@...oo.fr> wrote:
> Le Fri, 7 Dec 2007 15:54:18 +0100,
> Ingo Molnar <mingo@...e.hu> a écrit :
>
> > This is a version that
> > is supposed fix all known aspects of TSC and frequency-change
> > weirdnesses.
>
> Tested it with frequency changes, the clock is as smooth as I like it
> :-)
ok, great :-)
> The only remaining sched_clock user in need of conversion seems to be
> lockdep.
yeah - for CONFIG_LOCKSTAT - but that needs to be done even more
carefully, due to rq->lock being lockdep-checked. We can perhaps try a
lock-less cpu_clock() version - other CPUs are not supposed to update
rq->clock.
> Great work.
thanks. I do get the impression that most of this can/should wait until
2.6.25. The patches look quite dangerous.
Ingo
--
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