linux-kernel - [RFC] CPUFreq PowerOP integration, Issues/TODO 3/3

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

Date:	Thu, 14 Sep 2006 18:52:33 +0400
From:	"Eugeny S. Mints" <eugeny.mints@...il.com>
To:	pm list <linux-pm@...ts.osdl.org>
CC:	Matthew Locke <matt@...adgs.com>,
	Amit Kucheria <amit.kucheria@...ia.com>,
	Igor Stoppa <igor.stoppa@...ia.com>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: [RFC] CPUFreq PowerOP integration, Issues/TODO 3/3

- speedstep-centrino.c and speedstep-centrino-pm_core.c are no longer relevant
to CPUFreq - need to be moved out of cpufreq folder
- drivers/acpi/processor_perflib.c: needs cleanup. Now it is used by PM Core
but is compiled under CONFIG_CPU_FREQ and contains CPUFreq dependent code
- cpufreq.c code needs fixing to handle creation of operating points at
arbitrary moment ( to function properly on empty points list). For the time
being it is assumed that initialization order is: acpi, pm core, powerop, points
registration, cpufreq core
- cpufreq statistics is broken
- hotplug/sysdev_driver needs investigation
- pm core needs hotplug support
- example of dependent operating point registration module
- is any functionality affected by removing flags export from legacy cpufreq
driver?
- suspend/resume

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