Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

Am 2022-12-10 um 09:12 schrieb Christian König: Am 10.12.22 um 07:15 schrieb Felix Kuehling: On 2022-11-25 05:21, Christian König wrote: We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all those workaround

Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

Am 10.12.22 um 07:15 schrieb Felix Kuehling: On 2022-11-25 05:21, Christian König wrote: We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all those workarounds and generalize this for GTT as well. This fixes

Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

On 2022-11-25 05:21, Christian König wrote: We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all those workarounds and generalize this for GTT as well. This fixes ENOMEM issues with runaway applications which

Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

Am 25.11.22 um 19:18 schrieb Alex Deucher: On Fri, Nov 25, 2022 at 5:21 AM Christian König wrote: We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all those workarounds and generalize this for GTT as well.

Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

Hi Christian, Looks good to me. Reviewed-by: Arunpravin Paneer Selvam for the series. Regards, Arun. On 11/25/2022 3:51 PM, Christian König wrote: We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all thos

Re: [PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

On Fri, Nov 25, 2022 at 5:21 AM Christian König wrote: > > We already fallback to a dummy BO with no backing store when we > allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. > > Drop all those workarounds and generalize this for GTT as well. This > fixes ENOMEM issues with runaw

[PATCH 1/9] drm/amdgpu: generally allow over-commit during BO allocation

We already fallback to a dummy BO with no backing store when we allocate GDS,GWS and OA resources and to GTT when we allocate VRAM. Drop all those workarounds and generalize this for GTT as well. This fixes ENOMEM issues with runaway applications which try to allocate/free GTT in a loop and are ot