search for: acpi_processor_preregister_perform

...depending on them), thus > preventing them from loading successfully. I think what you are suggesting is that to write a driver in drivers/cpufreq/ that gets either started before the other ones (if built-in) or if as a module gets loaded from xencommons. That driver would then make the call to acpi_processor_preregister_performance(), acpi_processor_register_performance() and acpi_processor_notify_smm(). It would function as a cpufreq-scaling driver but in reality all calls to it from cpufreq gov-* drivers would end up with nop. Dave, would you be Ok with a driver like that in your tree? > >> for that is we want...

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that