linux-kernel - Re: [PATCH 07/10] cpufreq: Add support for x86 cpuinfo auto loading

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 8 Dec 2011 05:01:50 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Dave Jones <davej@...hat.com>, Andi Kleen <andi@...stfloor.org>,
	linux-kernel@...r.kernel.org, kay.sievers@...y.org, trenn@...e.de,
	Andi Kleen <ak@...ux.intel.com>, hpa@...or.com
Subject: Re: [PATCH 07/10] cpufreq: Add support for x86 cpuinfo auto loading

On Wed, Dec 07, 2011 at 08:24:29PM -0500, Dave Jones wrote:
>  > AFAIK distros just load them all right?
> 
> In Fedora, we used to. In F16, we changed things so instead of a monstrous
> init script with nested if's and a whole bunch of hairy logic, we changed
> all the modules to be built-in's, and relied on the link-order in the cpufreq Makefile
> to satisfy the 'first to bind wins'.

This should continue working -- udev/modprobe will load them in link order

I'll keep it like it is now.

> Yes, ugly, but we didn't have this patchset ;-) 

I should have posted it earlier.

Just don't forget to change them back to =m once it goes in.

-Andi
-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/