On Wed, Apr 03, 2024, Vineeth Pillai (Google) wrote: > Double scheduling is a concern with virtualization hosts where the host > schedules vcpus without knowing whats run by the vcpu and guest schedules > tasks without knowing where the vcpu is physically running. This causes > issues related to latencies, power consumption, resource utilization > etc. An ideal solution would be to have a cooperative scheduling > framework where the guest and host shares scheduling related information > and makes an educated scheduling decision to optimally handle the > workloads. As a first step, we are taking a stab at reducing latencies > for latency sensitive workloads in the guest. > > v1 RFC[1] was posted in December 2023. The main disagreement was in the > implementation where the patch was making scheduling policy decisions > in kvm and kvm is not the right place to do it. The suggestion was to > move the polcy decisions outside of kvm and let kvm only handle the > notifications needed to make the policy decisions. This patch series is > an iterative step towards implementing the feature as a layered > design where the policy could be implemented outside of kvm as a > kernel built-in, a kernel module or a bpf program. > > This design comprises mainly of 4 components: > > - pvsched driver: Implements the scheduling policies. Register with > host with a set of callbacks that hypervisor(kvm) can use to notify > vcpu events that the driver is interested in. The callback will be > passed in the address of shared memory so that the driver can get > scheduling information shared by the guest and also update the > scheduling policies set by the driver. > - kvm component: Selects the pvsched driver for a guest and notifies > the driver via callbacks for events that the driver is interested > in. Also interface with the guest in retreiving the shared memory > region for sharing the scheduling information. > - host kernel component: Implements the APIs for: > - pvsched driver for register/unregister to the host kernel, and > - hypervisor for assingning/unassigning driver for guests. > - guest component: Implements a framework for sharing the scheduling > information with the pvsched driver through kvm. Roughly summarazing an off-list discussion. - Discovery schedulers should be handled outside of KVM and the kernel, e.g. similar to how userspace uses PCI, VMBUS, etc. to enumerate devices to the guest. - "Negotiating" features/hooks should also be handled outside of the kernel, e.g. similar to how VirtIO devices negotiate features between host and guest. - Pushing PV scheduler entities to KVM should either be done through an exported API, e.g. if the scheduler is provided by a separate kernel module, or by a KVM or VM ioctl() (especially if the desire is to have per-VM schedulers). I think those were the main takeaways? Vineeth and Joel, please chime in on anything I've missed or misremembered. The other reason I'm bringing this discussion back on-list is that I (very) briefly discussed this with Paolo, and he pointed out the proposed rseq-based mechanism that would allow userspace to request an extended time slice[*], and that if that landed it would be easy-ish to reuse the interface for KVM's steal_time PV API. I see that you're both on that thread, so presumably you're already aware of the idea, but I wanted to bring it up here to make sure that we aren't trying to design something that's more complex than is needed. Specifically, if the guest has a generic way to request an extended time slice (or boost its priority?), would that address your use cases? Or rather, how close does it get you? E.g. the guest will have no way of requesting a larger time slice or boosting priority when an event is _pending_ but not yet receiveed by the guest, but is that actually problematic in practice? [*] https://lore.kernel.org/all/20231025235413.597287e1@xxxxxxxxxxxxxxxxxx
