linux-kernel - Re: [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 20 Dec 2006 11:47:57 -0800
From:	john stultz <johnstul@...ibm.com>
To:	Valdis.Kletnieks@...edu
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 Wed, 2006-12-20 at 14:26 -0500, Valdis.Kletnieks@...edu wrote:
> 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:

Doh. Oh right, I should have checked against -mm for conflicts.

> 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?

Yea, I will rework the patches ontop of -mm.

thanks
-john


-
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/