linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-um@lists.infradead.org, Richard Weinberger <richard@nod.at>,
	intel-xe@lists.freedesktop.org,
	Linux DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Jul 21 [drivers/gpu/drm/xe/xe.ko]
Date: Mon, 21 Jul 2025 22:50:29 -0700	[thread overview]
Message-ID: <22f5d759-e79c-4231-bf4b-2e498543aa5b@infradead.org> (raw)
In-Reply-To: <esdm6jfdkdbaeaphyhtfsckiii2tptdpe6dffddp5sqyg2klhk@b5dtuayqqpht>

[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]

Hi,

On 7/21/25 6:38 PM, Lucas De Marchi wrote:
> 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.

It's a randconfig, attached. (#1046 is for 32-bit)
config-um64-drmxegt is for 64-bit.
using gcc (SUSE Linux) 15.1.1 20250714

> 
> -----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(&gt_reset_failure, 1);
> +    return IS_ENABLED(CONFIG_DEBUG_FS) && should_fail(&gt_reset_failure, 1);
>  }
>  
>  struct xe_gt *xe_gt_alloc(struct xe_tile *tile);
> -----8<-------

This fixes the problem for me. Thanks.

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>

> 
> thanks,
> Lucas De Marchi
> 
>>
>> ERROR: modpost: "gt_reset_failure" [drivers/gpu/drm/xe/xe.ko] undefined!


-- 
~Randy

[-- Attachment #2: config-r1046.gz --]
[-- Type: application/gzip, Size: 29476 bytes --]

[-- Attachment #3: config-um64-drmxegt.gz --]
[-- Type: application/gzip, Size: 31423 bytes --]

  reply	other threads:[~2025-07-22  5:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250721174126.75106f39@canb.auug.org.au>
2025-07-21 20:17 ` linux-next: Tree for Jul 21 [drivers/gpu/drm/xe/xe.ko] Randy Dunlap
2025-07-22  1:38   ` Lucas De Marchi
2025-07-22  5:50     ` Randy Dunlap [this message]
2025-07-22 13:26       ` Lucas De Marchi
2025-07-23 15:50         ` Lucas De Marchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22f5d759-e79c-4231-bf4b-2e498543aa5b@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=lucas.demarchi@intel.com \
    --cc=richard@nod.at \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).