[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f3a5b249-84d8-9ba3-9977-3557c82a7850@amd.com>
Date: Tue, 18 Oct 2022 02:10:45 +0530
From: Arunpravin Paneer Selvam <arunpravin.paneerselvam@....com>
To: Christian König <christian.koenig@....com>,
Dave Airlie <airlied@...il.com>,
Arthur Marsh <arthur.marsh@...ernode.on.net>
Cc: "Deucher, Alexander" <Alexander.Deucher@....com>,
daniel.vetter@...ll.ch, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: [git pull] drm fixes for 6.1-rc1
Hi Christian,
Looks like we have to exit the loop if there are no blocks to compare.
May be that's why the function returns false.
@Arthur Marsh Could you please test the attached patch.
Thanks,
Arun
On 10/17/2022 1:39 PM, Christian König wrote:
> Am 17.10.22 um 10:01 schrieb Dave Airlie:
>> On Mon, 17 Oct 2022 at 17:07, Christian König
>> <christian.koenig@....com> wrote:
>>> Hi Arun,
>>>
>>> the hw generation doesn't matter. This error message here:
>>>
>>> amdgpu: Move buffer fallback to memcpy unavailable
>>>
>>> indicates that the detection of linear buffers still doesn't work as
>>> expected or that we have a bug somewhere else.
>>>
>>> Maybe the limiting when SDMA moves are not available isn't working
>>> correctly?
>> It is a CAPE_VERDE, so maybe something with the SI UVD memory
>> limitations?
>
> Yeah, good point. Could be that we try to move something into the UVD
> memory window and that something isn't allocated linearly.
>
> Arun can you trace the allocation and make sure that all kernel
> allocations have the CONTIGUOUS flag set?
>
> Thanks,
> Christian.
>
>>
>> Dave.
>
View attachment "0001-drm-amdgpu-Fix-for-BO-move-issue.patch" of type "text/plain" (980 bytes)
Powered by blists - more mailing lists