linux-kernel - Re: [PATCH] cpufreq/intel_pstate: Change to disallow module build

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]

Message-ID: <CAOh2x=mhtFsEJx57GTASAq+p4Ri-fvTmnkxZJzgifJ=3yTawXw@mail.gmail.com>
Date:	Thu, 14 Feb 2013 21:40:43 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	dirk.brandewie@...il.com
Cc:	davej@...hat.com, rjw@...k.pl, linux-kernel@...r.kernel.org,
	cpufreq@...r.kernel.org
Subject: Re: [PATCH] cpufreq/intel_pstate: Change to disallow module build

On Thu, Feb 14, 2013 at 1:44 AM,  <dirk.brandewie@...il.com> wrote:
> From: Dirk Brandewie <dirk.brandewie@...il.com>
>
> Load order is important in order for intel_pstate to take over as the
> default scaling driver from acpi-cpufreq.
>
> If both are built-in acpi-cpufreq uses late_initcall() and
> intel_pstate uses device_initcall() so it will be able to register as
> the scaling before acpi-cpufreq for the processors supported by
> intel_pstate.
>
> If acpi-cpufreq is built as a module then intel_pstate still gets
> first option to become the scaling driver.
>
> Signed-off-by: Dirk Brandewie <dirk.brandewie@...il.com>

Acked-by: Viresh Kumar <viresh.kumar@...aro.org>
--
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/