linux-kernel - Re: [git pull] drm fixes for 6.1-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 18 Oct 2022 11:58:06 +1030
From:   Arthur Marsh <arthur.marsh@...ernode.on.net>
To:     Arunpravin Paneer Selvam <arunpravin.paneerselvam@....com>,
        Christian König <christian.koenig@....com>,
        Dave Airlie <airlied@...il.com>
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

Thanks Arunpravin, your patch applied to the 6.1-rc1 code built a kernel that loaded the amdgpu module on my pc with Cape Verde GPU card with no problems.

Regards,

Arthur. 

On 18 October 2022 7:10:45 am ACDT, Arunpravin Paneer Selvam <arunpravin.paneerselvam@....com> wrote:
>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.
>> 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.