lkml.org 
[lkml]   [2017]   [Feb]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [patch 0/3] KVM CPU frequency change hypercalls
From
Date


On 03/02/2017 20:09, Radim Krcmar wrote:
> One reason why we have a kernel/userspace split is to allow sharing of
> CPU time. Each application then its state that the kernel keeps track
> of and saves/restores while time-multiplexing.
>
> Our frequency scaling interface goes against the idea -- guest kernel
> cannot schedule multiple userspaces on the same vCPU, because they could
> conflict by overriding frequency.
>
> i.e. our feature implies userspace tasks pinned to isolated vCPUs.

That's bad. This feature is broken by design unless it does proper
save/restore across preemption.

You don't need a hypercall. Add a cpufreq driver in DPDK that doesn't
use sysfs, and connect it to a daemon in the host through virtio-serial
or vsock.

Paolo

\
 
 \ /
  Last update: 2017-02-23 18:44    [W:1.213 / U:0.012 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site