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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 17 Oct 2022 10:09:54 +0200
From:   Christian König <christian.koenig@....com>
To:     Dave Airlie <airlied@...il.com>
Cc:     Arunpravin Paneer Selvam <arunpravin.paneerselvam@....com>,
        Arthur Marsh <arthur.marsh@...ernode.on.net>,
        "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

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.