All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Yan Zhao <yan.y.zhao@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Peter Xu <peterx@redhat.com>,
	Maxim Levitsky <mlevitsk@redhat.com>,
	 Binbin Wu <binbin.wu@linux.intel.com>,
	James Houghton <jthoughton@google.com>,
	 Pankaj Gupta <pankaj.gupta@amd.com>
Subject: Re: [PATCH v3 4/6] KVM: Check for empty mask of harvested dirty ring entries in caller
Date: Wed, 21 May 2025 07:55:20 -0700	[thread overview]
Message-ID: <aC3pWOUnMWvsxYWc@google.com> (raw)
In-Reply-To: <aC2Z2U/HR5wAay3s@yzhao56-desk.sh.intel.com>

On Wed, May 21, 2025, Yan Zhao wrote:
> On Fri, May 16, 2025 at 02:35:38PM -0700, Sean Christopherson wrote:
> > @@ -108,15 +105,24 @@ static inline bool kvm_dirty_gfn_harvested(struct kvm_dirty_gfn *gfn)
> >  int kvm_dirty_ring_reset(struct kvm *kvm, struct kvm_dirty_ring *ring,
> >  			 int *nr_entries_reset)
> >  {
> > +	/*
> > +	 * To minimize mmu_lock contention, batch resets for harvested entries
> > +	 * whose gfns are in the same slot, and are within N frame numbers of
> > +	 * each other, where N is the number of bits in an unsigned long.  For
> Suppose N is 64,
> 
> > +	 * simplicity, process the current set of entries when the next entry
> > +	 * can't be included in the batch.
> > +	 *
> > +	 * Track the current batch slot, the gfn offset into the slot for the
> > +	 * batch, and the bitmask of gfns that need to be reset (relative to
> > +	 * offset).  Note, the offset may be adjusted backwards, e.g. so that
> > +	 * a sequence of gfns X, X-1, ... X-N can be batched.
> X-N can't be batched, right?

Hah!  Yeah, off-by-one error.

  reply	other threads:[~2025-05-21 14:55 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 21:35 [PATCH v3 0/6] KVM: Dirty ring fixes and cleanups Sean Christopherson
2025-05-16 21:35 ` [PATCH v3 1/6] KVM: Bound the number of dirty ring entries in a single reset at INT_MAX Sean Christopherson
2025-05-20  6:51   ` Binbin Wu
2025-05-16 21:35 ` [PATCH v3 2/6] KVM: Bail from the dirty ring reset flow if a signal is pending Sean Christopherson
2025-05-20  6:53   ` Binbin Wu
2025-05-16 21:35 ` [PATCH v3 3/6] KVM: Conditionally reschedule when resetting the dirty ring Sean Christopherson
2025-05-16 21:35 ` [PATCH v3 4/6] KVM: Check for empty mask of harvested dirty ring entries in caller Sean Christopherson
2025-05-20  6:56   ` Binbin Wu
2025-05-21  9:16   ` Yan Zhao
2025-05-21 14:55     ` Sean Christopherson [this message]
2025-05-16 21:35 ` [PATCH v3 5/6] KVM: Use mask of harvested dirty ring entries to coalesce dirty ring resets Sean Christopherson
2025-05-20  6:58   ` Binbin Wu
2025-05-21  9:16   ` Yan Zhao
2025-05-21 14:54     ` Sean Christopherson
2025-05-21 19:45       ` Sean Christopherson
2025-05-22  1:04         ` Yan Zhao
2025-05-16 21:35 ` [PATCH v3 6/6] KVM: Assert that slots_lock is held when resetting per-vCPU dirty rings Sean Christopherson
2025-05-20  7:04   ` Binbin Wu
2025-05-20 19:12 ` [PATCH v3 0/6] KVM: Dirty ring fixes and cleanups Peter Xu
2025-05-20 23:16   ` Sean Christopherson
2025-05-20 23:51     ` Peter Xu
2025-05-21 14:50       ` Sean Christopherson
2025-05-21 15:24         ` Peter Xu
2025-05-21  9:21 ` Yan Zhao
2025-06-24 19:36 ` Sean Christopherson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aC3pWOUnMWvsxYWc@google.com \
    --to=seanjc@google.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=jthoughton@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=pankaj.gupta@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=yan.y.zhao@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.