On Mon, Apr 02, 2007 at 02:10:29PM +0200, Andi Kleen wrote:
On Monday 02 April 2007 13:38, Alexey Dobriyan wrote:
They will be used by cpuid driver and powernow-k8 cpufreq driver.
With these changes powernow-k8 driver could run correctly on OpenVZ kernels
with virtual cpus enabled
Both powernow-k8 and cpuid attempt to schedule
to the target CPU so they should already run there. But it is some other
CPU,
but when they ask your _on_cpu() functions they suddenly get a real CPU?
Where is the difference between these levels of virtualness?
*_on_cpu functions do
On Tue, Apr 03, 2007 at 03:42:50PM +0200, Andi Kleen wrote:
Both powernow-k8 and cpuid attempt to schedule
to the target CPU so they should already run there. But it is some other
CPU,
but when they ask your _on_cpu() functions they suddenly get a real CPU?
Where is the difference
On Monday 02 April 2007 13:38, Alexey Dobriyan wrote:
They will be used by cpuid driver and powernow-k8 cpufreq driver.
With these changes powernow-k8 driver could run correctly on OpenVZ kernels
with virtual cpus enabled (SCHED_VCPU).
This means openvz has multiple virtual CPU levels? One
Andi Kleen wrote:
On Monday 02 April 2007 13:38, Alexey Dobriyan wrote:
They will be used by cpuid driver and powernow-k8 cpufreq driver.
With these changes powernow-k8 driver could run correctly on OpenVZ kernels
with virtual cpus enabled (SCHED_VCPU).
This means openvz has multiple virtual
