<html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Hi Alejandro, yes I'm very aware of this issue, but unfortunately can't give an easy solution either. I'm working for over a year now on getting this fixed, but unfortunately it turned out that this problem is much bigger than initially thought. Setting the appropriate GFP flags for the job allocation is actually the trivial part. The really really hard thing is that we somehow need to add a lock to prevent the page tables from being evicted. And as you also figured out that lock can't be taken easily anywhere else. I've already wrote a prototype for this, but didn't had time to hammer it into shape for upstreaming yet. Regards, Christian. Am 27.11.19 um 15:55 schrieb Sierra Guiza, Alejandro (Alex): </div> <blockquote type="cite" cite="mid:SN6PR12MB26216A095D9839500242F489FD440@SN6PR12MB2621.namprd12.prod.outlook.com"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> <div class="WordSection1"> Hi Christian,<o:p></o:p> As you know, we’re working on the HMM enablement. Im working on the dGPU page table entries invalidation on the userptr mapping case. Currently, the MMU notifiers handle stops all user mode queues, schedule a delayed worker to re-validate userptr mappings and restart the queues. <o:p></o:p> Part of the HMM functionality, we need to invalidate the page table entries instead of stopping the queues. At the same time we need to move the revalidation of the userptr mappings into the page fault handler.<o:p></o:p> We’re seeing a deadlock warning after we try to invalidate the PTEs inside the MMU notifier handler. More specific, when we try to update the BOs to invalidate PTEs using amdgpu_vm_bo_update. This uses kmalloc on the amdgpu_job_alloc which seems to be causing this problem.<o:p></o:p> Based on <a id="OWAAMBC6F9A316D814AE993661FC111776926" href="mailto:Felix.Kuehling@amd.com" moz-do-not-send="true"> @Kuehling, Felix</a> comments, kmalloc without any special flags can cause memory reclaim. Doing that inside an MMU notifier is problematic, because an MMU notifier may be called inside a memory-reclaim operation itself. That would result in recursion. Also, reclaim shouldn't be done while holding a lock that can be taken in an MMU notifier for the same reason. If you cause a reclaim while holding that lock, then an MMU notifier called by the reclaim can deadlock trying to take the same lock.<o:p></o:p> Please let us know if you have any advice to enable this the right way<o:p></o:p> <o:p> </o:p> Thanks in advanced,<o:p></o:p> Alejandro<o:p></o:p> <o:p> </o:p> </div> </blockquote> </body> </html>