[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a718181481f73f0210b55c0e8333b86f8f5f2052.camel@intel.com>
Date: Wed, 7 Aug 2024 05:39:12 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "pbonzini@...hat.com" <pbonzini@...hat.com>, "seanjc@...gle.com"
<seanjc@...gle.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dmatlack@...gle.com" <dmatlack@...gle.com>
Subject: Re: [PATCH v2] KVM: x86/mmu: Clean up function comments for dirty
logging APIs
On Fri, 2024-08-02 at 13:20 -0700, Sean Christopherson wrote:
> Rework the function comment for kvm_arch_mmu_enable_log_dirty_pt_masked()
> into the body of the function, as it has gotten a bit stale, is harder to
> read without the code context, and is the last source of warnings for W=1
> builds in KVM x86 due to using a kernel-doc comment without documenting
> all parameters.
>
> Opportunistically subsume the functions comments for
> kvm_mmu_write_protect_pt_masked() and kvm_mmu_clear_dirty_pt_masked(), as
> there is no value in regurgitating similar information at a higher level,
> and capturing the differences between write-protection and PML-based dirty
> logging is best done in a common location.
>
> No functional change intended.
>
> Cc: David Matlack <dmatlack@...gle.com>
> Signed-off-by: Sean Christopherson <seanjc@...gle.com>
>
Reviewed-by: Kai Huang <kai.huang@...el.com>
[...]
>
> - /* Now handle 4K PTEs. */
> + /*
> + * (Re)Enable dirty logging for all 4KiB SPTEs that map the GFNs in
> + * mask. If PML is enabled and the and the GFN doesn't need to be
^
double "and the"
Powered by blists - more mailing lists