On Thu, 31 Jan 2019 11:10:06 -0500 Jerome Glisse <jglisse@xxxxxxxxxx> wrote: > Andrew what is your plan for this ? I had a discussion with Peter Xu > and Andrea about change_pte() and kvm. Today the change_pte() kvm > optimization is effectively disabled because of invalidate_range > calls. With a minimal couple lines patch on top of this patchset > we can bring back the kvm change_pte optimization and we can also > optimize some other cases like for instance when write protecting > after fork (but i am not sure this is something qemu does often so > it might not help for real kvm workload). > > I will be posting a the extra patch as an RFC, but in the meantime > i wanted to know what was the status for this. The various drm patches appear to be headed for collisions with drm tree development so we'll need to figure out how to handle that and in what order things happen. It's quite unclear from the v4 patchset's changelogs that this has anything to do with KVM and "the change_pte() kvm optimization" hasn't been described anywhere(?). So.. I expect the thing to do here is to get everything finished, get the changelogs completed with this new information and do a resend. Can we omit the drm and rdma patches for now? Feed them in via the subsystem maintainers when the dust has settled?
