On Tue, Aug 29, 2017 at 4:54 PM, Jérôme Glisse <jglisse@xxxxxxxxxx> wrote:
>
> Note this is barely tested. I intend to do more testing of next few days
> but i do not have access to all hardware that make use of the mmu_notifier
> API.
Thanks for doing this.
> First 2 patches convert existing call of mmu_notifier_invalidate_page()
> to mmu_notifier_invalidate_range() and bracket those call with call to
> mmu_notifier_invalidate_range_start()/end().
Ok, those two patches are a bit more complex than I was hoping for,
but not *too* bad.
And the final end result certainly looks nice:
> 16 files changed, 74 insertions(+), 214 deletions(-)
Yeah, removing all those invalidate_page() notifiers certainly makes
for a nice patch.
And I actually think you missed some more lines that can now be
removed: kvm_arch_mmu_notifier_invalidate_page() should no longer be
needed either, so you can remove all of those too (most of them are
empty inline functions, but x86 has one that actually does something.
So there's an added 30 or so dead lines that should be removed in the
kvm patch, I think.
But from a _very_ quick read-through this looks fine. But it obviously
needs testing.
People - *especially* the people who saw issues under KVM - can you
try out Jérôme's patch-series? I aded some people to the cc, the full
series is on lkml. Jérôme - do you have a git branch for people to
test that they could easily pull and try out?
Linus
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel
