[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <esdm6jfdkdbaeaphyhtfsckiii2tptdpe6dffddp5sqyg2klhk@b5dtuayqqpht>
Date: Mon, 21 Jul 2025 22:38:28 -0300
From: Lucas De Marchi <lucas.demarchi@...el.com>
To: Randy Dunlap <rdunlap@...radead.org>
CC: Stephen Rothwell <sfr@...b.auug.org.au>, Linux Next Mailing List
<linux-next@...r.kernel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, <linux-um@...ts.infradead.org>, "Richard
Weinberger" <richard@....at>, <intel-xe@...ts.freedesktop.org>, "Linux DRI
Development" <dri-devel@...ts.freedesktop.org>
Subject: Re: linux-next: Tree for Jul 21 [drivers/gpu/drm/xe/xe.ko]
On Mon, Jul 21, 2025 at 01:17:33PM -0700, Randy Dunlap wrote:
>
>
>On 7/21/25 12:41 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20250718:
>>
>
>on ARCH=um SUBARCH=i386, when
># CONFIG_DEBUG_FS is not set
can you share your entire config? I have all of the settings above, but
I can't reproduce it with gcc-13. Is this a regression from the previous
-next tag? I think the diff below should fix it, but I can't confirm on
my end nor I see how this would be a regression from a few days ago
only.
-----8<-------
diff --git a/drivers/gpu/drm/xe/xe_gt.h b/drivers/gpu/drm/xe/xe_gt.h
index e9ccab8aedbef..41880979f4ded 100644
--- a/drivers/gpu/drm/xe/xe_gt.h
+++ b/drivers/gpu/drm/xe/xe_gt.h
@@ -24,7 +24,7 @@
extern struct fault_attr gt_reset_failure;
static inline bool xe_fault_inject_gt_reset(void)
{
- return should_fail(>_reset_failure, 1);
+ return IS_ENABLED(CONFIG_DEBUG_FS) && should_fail(>_reset_failure, 1);
}
struct xe_gt *xe_gt_alloc(struct xe_tile *tile);
-----8<-------
thanks,
Lucas De Marchi
>
>ERROR: modpost: "gt_reset_failure" [drivers/gpu/drm/xe/xe.ko] undefined!
>
>--
>~Randy
>
Powered by blists - more mailing lists