Messages in this thread | | | Date | Fri, 17 Mar 2023 15:57:35 -0700 | Subject | Re: [Patch v3 0/7] Optimize clear dirty log | From | Sean Christopherson <> |
| |
On Fri, Feb 10, 2023, Vipin Sharma wrote: > This patch series has optimized control flow of clearing dirty log and > improved its performance by ~40% (2% more than v2). > > It also got rid of many variants of the handle_changed_spte family of > functions and converged logic to one handle_changed_spte() function. It > also remove tdp_mmu_set_spte_no_[acc_track|dirty_log] and various > booleans for controlling them. > > v3: > - Tried to do better job at writing commit messages.
LOL, that's the spirit!
Did a cursory glance, looks good. I'll do a more thorough pass next week and get it queued up if all goes well. No need for a v4 at this point, I'll fixup David's various nits when applying. I'll also add a link in patch 2 to the discussion about why we determined that bypassing __tdp_mmu_set_spte() is safe; that's critical information that isn't captured in the changelog.
| |