linux-kernel - Re: + clocksource-increase-initcall-priority.patch added to -mm tree

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1160294812.22911.8.camel@localhost.localdomain>
Date:	Sun, 08 Oct 2006 10:06:52 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	akpm@...l.org
Cc:	dwalker@...sta.com, johnstul@...ibm.com, mingo@...e.hu,
	zippel@...ux-m68k.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: + clocksource-increase-initcall-priority.patch added to -mm
	tree

On Fri, 2006-10-06 at 18:53 -0700, akpm@...l.org wrote:
> Since it's likely that this interface would get used during bootup I moved all
> the clocksource registration into the postcore initcall.  This also eliminated
> some clocksource shuffling during bootup.

We had the init call in postcore already. John moved it to module init
to eliminate trouble with unsynced / unstable TSCs, IIRC.

John, can you please comment on this.

	tglx
 


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