[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200612201926.kBKJQoqN020967@turing-police.cc.vt.edu>
Date: Wed, 20 Dec 2006 14:26:50 -0500
From: Valdis.Kletnieks@...edu
To: john stultz <johnstul@...ibm.com>
Cc: Andrew Morton <akpm@...l.org>, Andi Kleen <ak@...e.de>,
linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...e.hu
Subject: Re: [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
On Tue, 19 Dec 2006 20:20:39 EST, john stultz said:
> I didn't hear any objections (or really, any comments) on my
> last release, so as I mentioned then, I want to go ahead and push this
> to Andrew for a bit of testing in -mm. Hopefully targeting for
> inclusion in 2.6.21 or 2.6.22.
Am running it on a Dell Latitude D820 (Core2 T7200 cpu). I had to un-do
4 conflicting patches in -rc1-mm1 and then it applied and ran clean, I still
need to look at re-merging them:
hpet-avoid-warning-message-livelock.patch
clockevents-i386-hpet-driver.patch
get-rid-of-arch_have_xtime_lock.patch
x86_64-mm-amd-tsc-sync.patch
It *looks* like all the pieces are there except a few lines of Kconfig
magic to wire up the dynticks/NO_HZ stuff - or did I miss something crucial?
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists