Re: [PATCH] drm/etnaviv: switch devcoredump allocations to GFP_NOWAIT

2024-05-21 Thread Daniel Vetter
On Fri, May 17, 2024 at 10:18:50AM +0200, Philipp Zabel wrote: > On Do, 2024-05-16 at 19:20 +0200, Lucas Stach wrote: > > Am Freitag, dem 26.01.2024 um 17:46 +0100 schrieb Lucas Stach: > > > The etnaviv devcoredump is created in the GPU reset path, which > > > must make forward progress to avoid st

Re: [PATCH] drm/etnaviv: switch devcoredump allocations to GFP_NOWAIT

2024-05-17 Thread Philipp Zabel
On Do, 2024-05-16 at 19:20 +0200, Lucas Stach wrote: > Am Freitag, dem 26.01.2024 um 17:46 +0100 schrieb Lucas Stach: > > The etnaviv devcoredump is created in the GPU reset path, which > > must make forward progress to avoid stalling memory reclaim on > > unsignalled dma fences. The currently used

Re: [PATCH] drm/etnaviv: switch devcoredump allocations to GFP_NOWAIT

2024-05-16 Thread Lucas Stach
Am Freitag, dem 26.01.2024 um 17:46 +0100 schrieb Lucas Stach: > The etnaviv devcoredump is created in the GPU reset path, which > must make forward progress to avoid stalling memory reclaim on > unsignalled dma fences. The currently used __GFP_NORETRY does not > prohibit sleeping on direct reclaim

[PATCH] drm/etnaviv: switch devcoredump allocations to GFP_NOWAIT

2024-01-26 Thread Lucas Stach
The etnaviv devcoredump is created in the GPU reset path, which must make forward progress to avoid stalling memory reclaim on unsignalled dma fences. The currently used __GFP_NORETRY does not prohibit sleeping on direct reclaim, breaking the forward progress guarantee. Switch to GFP_NOWAIT, which