On Thu, Mar 30, 2023 at 03:43:35PM -0700, David Dai wrote: > Hi, > > This patch series is a continuation of the talk Saravana gave at LPC 2022 > titled "CPUfreq/sched and VM guest workload problems" [1][2][3]. The gist > of the talk is that workloads running in a guest VM get terrible task > placement and DVFS behavior when compared to running the same workload in > the host. Effectively, no EAS for threads inside VMs. This would make power > and performance terrible just by running the workload in a VM even if we > assume there is zero virtualization overhead. > > We have been iterating over different options for communicating between > guest and host, ways of applying the information coming from the > guest/host, etc to figure out the best performance and power improvements > we could get. > > The patch series in its current state is NOT meant for landing in the > upstream kernel. We are sending this patch series to share the current > progress and data we have so far. The patch series is meant to be easy to > cherry-pick and test on various devices to see what performance and power > benefits this might give for others. > > With this series, a workload running in a VM gets the same task placement > and DVFS treatment as it would when running in the host. > > As expected, we see significant performance improvement and better > performance/power ratio. If anyone else wants to try this out for your VM > workloads and report findings, that'd be very much appreciated. > > The idea is to improve VM CPUfreq/sched behavior by: > - Having guest kernel to do accurate load tracking by taking host CPU > arch/type and frequency into account. > - Sharing vCPU run queue utilization information with the host so that the > host can do proper frequency scaling and task placement on the host side. So, not having actually been send many of the patches I've no idea what you've done... Please, eradicate this ridiculous idea of sending random people a random subset of a patch series. Either send all of it or none, this is a bloody nuisance. Having said that; my biggest worry is that you're making scheduler internals into an ABI. I would hate for this paravirt interface to tie us down.
