On 8/15/22 14:28, Christian König wrote: >>>> Maybe it was discussed privately? In this case I will be happy to get >>>> more info from you about the root of the problem so I could start to >>>> look at how to fix it properly. It's not apparent where the problem is >>>> to a TTM newbie like me. >>>> >>> Well this is completely unfixable. See the whole purpose of TTM is to >>> allow tracing where what is mapped of a buffer object. >>> >>> If you circumvent that and increase the page reference yourself than >>> that whole functionality can't work correctly any more. >> Are you suggesting that the problem is that TTM doesn't see the KVM page >> faults/mappings? > > Yes, and no. It's one of the issues, but there is more behind that (e.g. > what happens when TTM switches from pages to local memory for backing a > BO). If KVM page fault could reach TTM, then it should be able to relocate BO. I see now where is the problem, thanks. Although, I'm wondering whether it already works somehow.. I'll try to play with the the AMDGPU shrinker and see what will happen on guest mapping of a relocated BO. > Another question is why is KVM accessing the page structure in the first > place? The VMA is mapped with VM_PFNMAP and VM_IO, KVM should never ever > touch any of those pages. https://elixir.bootlin.com/linux/v5.19/source/virt/kvm/kvm_main.c#L2549 -- Best regards, Dmitry
