On Sun, Mar 06, 2022, Shivam Kumar wrote: > Update the kvm_run structure with a brief description of dirty > quota members and how dirty quota throttling works. This should be squashed with patch 1. I actually had to look ahead to this patch because I forgot the details since I last reviewed this :-) > Suggested-by: Shaju Abraham <shaju.abraham@xxxxxxxxxxx> > Suggested-by: Manish Mishra <manish.mishra@xxxxxxxxxxx> > Co-developed-by: Anurag Madnawat <anurag.madnawat@xxxxxxxxxxx> > Signed-off-by: Anurag Madnawat <anurag.madnawat@xxxxxxxxxxx> > Signed-off-by: Shivam Kumar <shivam.kumar1@xxxxxxxxxxx> > --- > Documentation/virt/kvm/api.rst | 28 ++++++++++++++++++++++++++++ > 1 file changed, 28 insertions(+) > > diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst > index 9f3172376ec3..50e001473b1f 100644 > --- a/Documentation/virt/kvm/api.rst > +++ b/Documentation/virt/kvm/api.rst > @@ -6125,6 +6125,23 @@ array field represents return values. The userspace should update the return > values of SBI call before resuming the VCPU. For more details on RISC-V SBI > spec refer, https://github.com/riscv/riscv-sbi-doc. > > +:: > + > + /* KVM_EXIT_DIRTY_QUOTA_EXHAUSTED */ > + struct { > + __u64 count; > + __u64 quota; > + } dirty_quota_exit; > +If exit reason is KVM_EXIT_DIRTY_QUOTA_EXHAUSTED, it indicates that the VCPU has > +exhausted its dirty quota. The 'dirty_quota_exit' member of kvm_run structure > +makes the following information available to the userspace: > + 'count' field: the current count of pages dirtied by the VCPU, > + 'quota' field: the observed dirty quota just before the exit to userspace. > +The userspace can design a strategy to allocate the overall scope of dirtying > +for the VM among the vcpus. Based on the strategy and the current state of dirty > +quota throttling, the userspace can make a decision to either update (increase) > +the quota or to put the VCPU to sleep for some time. > + > :: > > /* Fix the size of the union. */ > @@ -6159,6 +6176,17 @@ values in kvm_run even if the corresponding bit in kvm_dirty_regs is not set. > > :: > > + /* > + * Number of pages the vCPU is allowed to have dirtied over its entire > + * lifetime. KVM_RUN exits with KVM_EXIT_DIRTY_QUOTA_EXHAUSTED if the quota > + * is reached/exceeded. > + */ > + __u64 dirty_quota; > +Please note that this quota cannot be strictly enforced if PML is enabled, and > +the VCPU may end up dirtying pages more than its quota. The difference however > +is bounded by the PML buffer size. If you want to be pedantic, I doubt KVM can strictly enforce the quota even if PML is disabled. E.g. I can all but guarantee that it's possible to dirty multiple pages during a single exit. Probably also worth spelling out PML and genericizing things. Maybe Please note that enforcing the quota is best effort, as the guest may dirty multiple pages before KVM can recheck the quota. However, unless KVM is using a hardware-based dirty ring buffer, e.g. Intel's Page Modification Logging, KVM will detect quota exhaustion within a handful of dirtied page. If a hardware ring buffer is used, the overrun is bounded by the size of the buffer (512 entries for PML).
