Re: [PATCH] drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages

On 6/16/26 15:20, Greg KH wrote:
> On Tue, Jun 16, 2026 at 09:05:31AM -0400, Alex Deucher wrote:
>> From: Honglei Huang <[email protected]>

FWIW, that change in between landed in mainline as 342981fff32802
("drm/amdgpu: drop retry loop in amdgpu_hmm_range_get_pages"), so might
be a good idea to add this while applying:

commit 342981fff32802a819d6fc7cf3c9fedf9f3d9d60 upstream.

>> Since commit c08972f55594 ("drm/amdgpu: fix amdgpu_hmm_range_get_pages")
>> moved mmu_interval_read_begin() out of the per-chunk loop, the
>> captured notifier_seq is no longer refreshed across retries. As a
>> result, the existing -EBUSY retry path can never make progress:
>> [...]
>> No functional regression: the previous behaviour on -EBUSY was already
>> to fail with -EAGAIN after a 1s stall; we just skip the stall.>>
>> Fixes: c08972f55594 ("drm/amdgpu: fix amdgpu_hmm_range_get_pages")
> 
> This commit is not anywhere...

This is 962d684b5dc074 ("drm/amdgpu: fix amdgpu_hmm_range_get_pages")
[v7.1-rc6, v7.0.12], which recently landed in mainline a second time as
c08972f555945c.

Hope this gets things rolling (I just stumbled on a second report about
a regression which should be fixed by this, which is why I thought it
might be worth adding these details to the thread in the hope to get
this into 7.1.y and 7.0.y soon).

Ciao, Thorsten