* [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list
@ 2019-04-02 9:19 wentalou
[not found] ` <1554196784-25674-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org>
0 siblings, 1 reply; 6+ messages in thread
From: wentalou @ 2019-04-02 9:19 UTC (permalink / raw)
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW; +Cc: wentalou
amdgpu_bo_restore_shadow would assign zero to r if succeeded.
r would remain zero if there is only one node in shadow_list.
current code would always return failure when r <= 0.
restart the timeout for each wait was a rather problematic bug as well.
The value of tmo SHOULD be changed, otherwise we wait tmo jiffies on each loop.
meanwhile, fix Call Trace by NULL of shadow->parent.
Change-Id: I7e836ec7ab6cd0f069aac24f88e454e906637541
Signed-off-by: Wentao Lou <Wentao.Lou@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 15 ++++++++++-----
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index c4c61e9..5a2dc44 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ -3183,7 +3183,7 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev)
/* No need to recover an evicted BO */
if (shadow->tbo.mem.mem_type != TTM_PL_TT ||
- shadow->parent->tbo.mem.mem_type != TTM_PL_VRAM)
+ shadow->parent == NULL || shadow->parent->tbo.mem.mem_type != TTM_PL_VRAM)
continue;
r = amdgpu_bo_restore_shadow(shadow, &next);
@@ -3191,11 +3191,16 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev)
break;
if (fence) {
- r = dma_fence_wait_timeout(fence, false, tmo);
+ tmo = dma_fence_wait_timeout(fence, false, tmo);
dma_fence_put(fence);
fence = next;
- if (r <= 0)
+ if (tmo == 0) {
+ r = -ETIMEDOUT;
break;
+ } else if (tmo < 0) {
+ r = tmo;
+ break;
+ }
} else {
fence = next;
}
@@ -3206,8 +3211,8 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev)
tmo = dma_fence_wait_timeout(fence, false, tmo);
dma_fence_put(fence);
- if (r <= 0 || tmo <= 0) {
- DRM_ERROR("recover vram bo from shadow failed\n");
+ if (r < 0 || tmo <= 0) {
+ DRM_ERROR("recover vram bo from shadow failed, tmo is %d\n", tmo);
return -EIO;
}
--
2.7.4
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply related [flat|nested] 6+ messages in thread[parent not found: <1554196784-25674-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org>]
* Re: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list [not found] ` <1554196784-25674-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org> @ 2019-04-02 10:36 ` Christian König [not found] ` <470b5b5e-385c-84b8-8706-40222209fa34-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 0 siblings, 1 reply; 6+ messages in thread From: Christian König @ 2019-04-02 10:36 UTC (permalink / raw) To: wentalou, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Am 02.04.19 um 11:19 schrieb wentalou: > amdgpu_bo_restore_shadow would assign zero to r if succeeded. > r would remain zero if there is only one node in shadow_list. > current code would always return failure when r <= 0. > restart the timeout for each wait was a rather problematic bug as well. > The value of tmo SHOULD be changed, otherwise we wait tmo jiffies on each loop. > meanwhile, fix Call Trace by NULL of shadow->parent. > > Change-Id: I7e836ec7ab6cd0f069aac24f88e454e906637541 > Signed-off-by: Wentao Lou <Wentao.Lou@amd.com> > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 15 ++++++++++----- > 1 file changed, 10 insertions(+), 5 deletions(-) > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > index c4c61e9..5a2dc44 100644 > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > @@ -3183,7 +3183,7 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > > /* No need to recover an evicted BO */ > if (shadow->tbo.mem.mem_type != TTM_PL_TT || > - shadow->parent->tbo.mem.mem_type != TTM_PL_VRAM) > + shadow->parent == NULL || shadow->parent->tbo.mem.mem_type != TTM_PL_VRAM) That doesn't looks like a good idea to me. Did you actually run into this issue? > continue; > > r = amdgpu_bo_restore_shadow(shadow, &next); > @@ -3191,11 +3191,16 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > break; > > if (fence) { > - r = dma_fence_wait_timeout(fence, false, tmo); > + tmo = dma_fence_wait_timeout(fence, false, tmo); > dma_fence_put(fence); > fence = next; > - if (r <= 0) > + if (tmo == 0) { > + r = -ETIMEDOUT; > break; > + } else if (tmo < 0) { > + r = tmo; > + break; > + } > } else { > fence = next; > } > @@ -3206,8 +3211,8 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > tmo = dma_fence_wait_timeout(fence, false, tmo); > dma_fence_put(fence); > > - if (r <= 0 || tmo <= 0) { > - DRM_ERROR("recover vram bo from shadow failed\n"); > + if (r < 0 || tmo <= 0) { > + DRM_ERROR("recover vram bo from shadow failed, tmo is %d\n", tmo); Maybe print both r and tmo in the message. Regards, Christian. > return -EIO; > } > _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <470b5b5e-385c-84b8-8706-40222209fa34-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]
* RE: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list [not found] ` <470b5b5e-385c-84b8-8706-40222209fa34-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> @ 2019-04-03 6:35 ` Lou, Wentao [not found] ` <MN2PR12MB328059309BE6D3A038FDF12A83570-rweVpJHSKToYX/8oZD8ObAdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org> 0 siblings, 1 reply; 6+ messages in thread From: Lou, Wentao @ 2019-04-03 6:35 UTC (permalink / raw) To: Koenig, Christian, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Hi Christian, Sometimes shadow->parent would be NULL in my testbed, but not reproduce today... Just sent out another patch following your advice. Thanks. BR, Wentao -----Original Message----- From: Christian König <ckoenig.leichtzumerken@gmail.com> Sent: Tuesday, April 2, 2019 6:36 PM To: Lou, Wentao <Wentao.Lou@amd.com>; amd-gfx@lists.freedesktop.org Subject: Re: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list Am 02.04.19 um 11:19 schrieb wentalou: > amdgpu_bo_restore_shadow would assign zero to r if succeeded. > r would remain zero if there is only one node in shadow_list. > current code would always return failure when r <= 0. > restart the timeout for each wait was a rather problematic bug as well. > The value of tmo SHOULD be changed, otherwise we wait tmo jiffies on each loop. > meanwhile, fix Call Trace by NULL of shadow->parent. > > Change-Id: I7e836ec7ab6cd0f069aac24f88e454e906637541 > Signed-off-by: Wentao Lou <Wentao.Lou@amd.com> > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 15 ++++++++++----- > 1 file changed, 10 insertions(+), 5 deletions(-) > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > index c4c61e9..5a2dc44 100644 > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > @@ -3183,7 +3183,7 @@ static int amdgpu_device_recover_vram(struct > amdgpu_device *adev) > > /* No need to recover an evicted BO */ > if (shadow->tbo.mem.mem_type != TTM_PL_TT || > - shadow->parent->tbo.mem.mem_type != TTM_PL_VRAM) > + shadow->parent == NULL || shadow->parent->tbo.mem.mem_type != > +TTM_PL_VRAM) That doesn't looks like a good idea to me. Did you actually run into this issue? > continue; > > r = amdgpu_bo_restore_shadow(shadow, &next); @@ -3191,11 +3191,16 > @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > break; > > if (fence) { > - r = dma_fence_wait_timeout(fence, false, tmo); > + tmo = dma_fence_wait_timeout(fence, false, tmo); > dma_fence_put(fence); > fence = next; > - if (r <= 0) > + if (tmo == 0) { > + r = -ETIMEDOUT; > break; > + } else if (tmo < 0) { > + r = tmo; > + break; > + } > } else { > fence = next; > } > @@ -3206,8 +3211,8 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > tmo = dma_fence_wait_timeout(fence, false, tmo); > dma_fence_put(fence); > > - if (r <= 0 || tmo <= 0) { > - DRM_ERROR("recover vram bo from shadow failed\n"); > + if (r < 0 || tmo <= 0) { > + DRM_ERROR("recover vram bo from shadow failed, tmo is %d\n", tmo); Maybe print both r and tmo in the message. Regards, Christian. > return -EIO; > } > _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
[parent not found: <MN2PR12MB328059309BE6D3A038FDF12A83570-rweVpJHSKToYX/8oZD8ObAdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>]
* Re: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list [not found] ` <MN2PR12MB328059309BE6D3A038FDF12A83570-rweVpJHSKToYX/8oZD8ObAdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org> @ 2019-04-03 7:03 ` Koenig, Christian 0 siblings, 0 replies; 6+ messages in thread From: Koenig, Christian @ 2019-04-03 7:03 UTC (permalink / raw) To: Lou, Wentao, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Mhm, that sounds like another bug to me which we need to investigate. Probably a race during freeing of shadow allocations. Christian. Am 03.04.19 um 08:35 schrieb Lou, Wentao: > Hi Christian, > > Sometimes shadow->parent would be NULL in my testbed, but not reproduce today... > Just sent out another patch following your advice. > Thanks. > > BR, > Wentao > > > -----Original Message----- > From: Christian König <ckoenig.leichtzumerken@gmail.com> > Sent: Tuesday, April 2, 2019 6:36 PM > To: Lou, Wentao <Wentao.Lou@amd.com>; amd-gfx@lists.freedesktop.org > Subject: Re: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list > > Am 02.04.19 um 11:19 schrieb wentalou: >> amdgpu_bo_restore_shadow would assign zero to r if succeeded. >> r would remain zero if there is only one node in shadow_list. >> current code would always return failure when r <= 0. >> restart the timeout for each wait was a rather problematic bug as well. >> The value of tmo SHOULD be changed, otherwise we wait tmo jiffies on each loop. >> meanwhile, fix Call Trace by NULL of shadow->parent. >> >> Change-Id: I7e836ec7ab6cd0f069aac24f88e454e906637541 >> Signed-off-by: Wentao Lou <Wentao.Lou@amd.com> >> --- >> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 15 ++++++++++----- >> 1 file changed, 10 insertions(+), 5 deletions(-) >> >> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c >> b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c >> index c4c61e9..5a2dc44 100644 >> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c >> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c >> @@ -3183,7 +3183,7 @@ static int amdgpu_device_recover_vram(struct >> amdgpu_device *adev) >> >> /* No need to recover an evicted BO */ >> if (shadow->tbo.mem.mem_type != TTM_PL_TT || >> - shadow->parent->tbo.mem.mem_type != TTM_PL_VRAM) >> + shadow->parent == NULL || shadow->parent->tbo.mem.mem_type != >> +TTM_PL_VRAM) > That doesn't looks like a good idea to me. Did you actually run into this issue? > >> continue; >> >> r = amdgpu_bo_restore_shadow(shadow, &next); @@ -3191,11 +3191,16 >> @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) >> break; >> >> if (fence) { >> - r = dma_fence_wait_timeout(fence, false, tmo); >> + tmo = dma_fence_wait_timeout(fence, false, tmo); >> dma_fence_put(fence); >> fence = next; >> - if (r <= 0) >> + if (tmo == 0) { >> + r = -ETIMEDOUT; >> break; >> + } else if (tmo < 0) { >> + r = tmo; >> + break; >> + } >> } else { >> fence = next; >> } >> @@ -3206,8 +3211,8 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) >> tmo = dma_fence_wait_timeout(fence, false, tmo); >> dma_fence_put(fence); >> >> - if (r <= 0 || tmo <= 0) { >> - DRM_ERROR("recover vram bo from shadow failed\n"); >> + if (r < 0 || tmo <= 0) { >> + DRM_ERROR("recover vram bo from shadow failed, tmo is %d\n", tmo); > Maybe print both r and tmo in the message. > > Regards, > Christian. > >> return -EIO; >> } >> _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list
@ 2019-04-03 6:33 wentalou
[not found] ` <1554273187-28657-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org>
0 siblings, 1 reply; 6+ messages in thread
From: wentalou @ 2019-04-03 6:33 UTC (permalink / raw)
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW; +Cc: wentalou
amdgpu_bo_restore_shadow would assign zero to r if succeeded.
r would remain zero if there is only one node in shadow_list.
current code would always return failure when r <= 0.
restart the timeout for each wait was a rather problematic bug as well.
The value of tmo SHOULD be changed, otherwise we wait tmo jiffies on each loop.
Change-Id: I7e836ec7ab6cd0f069aac24f88e454e906637541
Signed-off-by: Wentao Lou <Wentao.Lou@amd.com>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
index c4c61e9..fcb3d95 100644
--- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
+++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
@@ -3191,11 +3191,16 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev)
break;
if (fence) {
- r = dma_fence_wait_timeout(fence, false, tmo);
+ tmo = dma_fence_wait_timeout(fence, false, tmo);
dma_fence_put(fence);
fence = next;
- if (r <= 0)
+ if (tmo == 0) {
+ r = -ETIMEDOUT;
break;
+ } else if (tmo < 0) {
+ r = tmo;
+ break;
+ }
} else {
fence = next;
}
@@ -3206,8 +3211,8 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev)
tmo = dma_fence_wait_timeout(fence, false, tmo);
dma_fence_put(fence);
- if (r <= 0 || tmo <= 0) {
- DRM_ERROR("recover vram bo from shadow failed\n");
+ if (r < 0 || tmo <= 0) {
+ DRM_ERROR("recover vram bo from shadow failed, r is %ld, tmo is %ld\n", r, tmo);
return -EIO;
}
--
2.7.4
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
^ permalink raw reply related [flat|nested] 6+ messages in thread[parent not found: <1554273187-28657-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org>]
* Re: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list [not found] ` <1554273187-28657-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org> @ 2019-04-03 7:57 ` Christian König 0 siblings, 0 replies; 6+ messages in thread From: Christian König @ 2019-04-03 7:57 UTC (permalink / raw) To: wentalou, amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW Am 03.04.19 um 08:33 schrieb wentalou: > amdgpu_bo_restore_shadow would assign zero to r if succeeded. > r would remain zero if there is only one node in shadow_list. > current code would always return failure when r <= 0. > restart the timeout for each wait was a rather problematic bug as well. > The value of tmo SHOULD be changed, otherwise we wait tmo jiffies on each loop. > > Change-Id: I7e836ec7ab6cd0f069aac24f88e454e906637541 > Signed-off-by: Wentao Lou <Wentao.Lou@amd.com> Reviewed-by: Christian König <christian.koenig@amd.com> > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 13 +++++++++---- > 1 file changed, 9 insertions(+), 4 deletions(-) > > diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > index c4c61e9..fcb3d95 100644 > --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c > @@ -3191,11 +3191,16 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > break; > > if (fence) { > - r = dma_fence_wait_timeout(fence, false, tmo); > + tmo = dma_fence_wait_timeout(fence, false, tmo); > dma_fence_put(fence); > fence = next; > - if (r <= 0) > + if (tmo == 0) { > + r = -ETIMEDOUT; > break; > + } else if (tmo < 0) { > + r = tmo; > + break; > + } > } else { > fence = next; > } > @@ -3206,8 +3211,8 @@ static int amdgpu_device_recover_vram(struct amdgpu_device *adev) > tmo = dma_fence_wait_timeout(fence, false, tmo); > dma_fence_put(fence); > > - if (r <= 0 || tmo <= 0) { > - DRM_ERROR("recover vram bo from shadow failed\n"); > + if (r < 0 || tmo <= 0) { > + DRM_ERROR("recover vram bo from shadow failed, r is %ld, tmo is %ld\n", r, tmo); > return -EIO; > } > _______________________________________________ amd-gfx mailing list amd-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-04-03 7:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-04-02 9:19 [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list wentalou
[not found] ` <1554196784-25674-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org>
2019-04-02 10:36 ` Christian König
[not found] ` <470b5b5e-385c-84b8-8706-40222209fa34-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-04-03 6:35 ` Lou, Wentao
[not found] ` <MN2PR12MB328059309BE6D3A038FDF12A83570-rweVpJHSKToYX/8oZD8ObAdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-04-03 7:03 ` Koenig, Christian
-- strict thread matches above, loose matches on Subject: below --
2019-04-03 6:33 wentalou
[not found] ` <1554273187-28657-1-git-send-email-Wentao.Lou-5C7GfCeVMHo@public.gmane.org>
2019-04-03 7:57 ` Christian König
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox