Re: [PATCH 4/6] drm/amdkfd: GFP_NOIO while holding locks taken in MMU notifier

2018-05-14 Thread Oded Gabbay
Cool, thanks! On Mon, 14 May 2018, 19:07 Felix Kuehling wrote: > On 2018-05-11 03:59 AM, Oded Gabbay wrote: > > On Fri, Mar 23, 2018 at 10:32 PM, Felix Kuehling > wrote: > >> When an MMU notifier runs in memory reclaim context, it can deadlock >

Re: [PATCH 4/6] drm/amdkfd: GFP_NOIO while holding locks taken in MMU notifier

2018-05-14 Thread Felix Kuehling
On 2018-05-11 03:59 AM, Oded Gabbay wrote: > On Fri, Mar 23, 2018 at 10:32 PM, Felix Kuehling > wrote: >> When an MMU notifier runs in memory reclaim context, it can deadlock >> trying to take locks that are already held in the thread causing the >> memory reclaim. The

Re: [PATCH 4/6] drm/amdkfd: GFP_NOIO while holding locks taken in MMU notifier

2018-05-11 Thread Oded Gabbay
On Fri, Mar 23, 2018 at 10:32 PM, Felix Kuehling wrote: > When an MMU notifier runs in memory reclaim context, it can deadlock > trying to take locks that are already held in the thread causing the > memory reclaim. The solution is to avoid memory reclaim while holding >

[PATCH 4/6] drm/amdkfd: GFP_NOIO while holding locks taken in MMU notifier

2018-03-23 Thread Felix Kuehling
When an MMU notifier runs in memory reclaim context, it can deadlock trying to take locks that are already held in the thread causing the memory reclaim. The solution is to avoid memory reclaim while holding locks that are taken in MMU notifiers by using GFP_NOIO. This commit fixes memory