[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c5b80a7-5bf9-4752-a596-438924fdec9c@amd.com>
Date: Wed, 21 Feb 2024 15:07:20 +0100
From: Christian König <christian.koenig@....com>
To: Erhard Furtner <erhard_f@...lbox.org>
Cc: Bagas Sanjaya <bagasdotme@...il.com>,
Linux DRI Development <dri-devel@...ts.freedesktop.org>,
Huang Rui <ray.huang@....com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Karolina Stolarek <karolina.stolarek@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Andrew Morton <akpm@...ux-foundation.org>, Zi Yan <ziy@...dia.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: Running ttm_device_test leads to list_add corruption. prev->next
should be next (ffffffffc05cd428), but was 6b6b6b6b6b6b6b6b.
(prev=ffffa0b1a5c034f0) (kernel 6.7.5)
Am 20.02.24 um 18:43 schrieb Erhard Furtner:
> On Tue, 20 Feb 2024 14:50:04 +0100
> Christian König <christian.koenig@....com> wrote:
>
>> Yeah and that's probably the problem. The test is not supposed to be
>> compiled and executed on bare metal, but rather just as unit test
>> through user mode Linux.
>>
>> We probably don't check that correctly in the kconfig for some reason.
>> Can you provide your .config file?
>>
> Here's my v6.8-rc5 .config attached.
Thanks for that.
As long as nobody comes up with an approach how to run the test even
when other drivers want to interact with TTM the attached patch is my
best idea.
It basically disabled compiling the TTM tests as long as neither
compiling for UML or COMPILE_TEST are set.
Opinions?
Thanks,
Christian.
>
> Regards,
> Erhard
View attachment "0001-drm-ttm-tests-depend-on-UML-COMPILE_TEST.patch" of type "text/x-patch" (1604 bytes)
Powered by blists - more mailing lists