Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Matthew Brost <matthew.brost@intel.com>,
	 Dafna Hirschfeld <dhirschfeld@habana.ai>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Alan Previn <alan.previn.teres.alexis@intel.com>,
	 Himanshu Somaiya <himanshu.somaiya@intel.com>
Subject: Re: [PATCH 3/4] drm/xe: Force wedged state and block GT reset upon any GPU hang
Date: Wed, 24 Apr 2024 22:31:55 +0530	[thread overview]
Message-ID: <668f4543-dab7-4d7f-a2b8-595e5ddad465@intel.com> (raw)
In-Reply-To: <Zij6Qh1rvGTOG3e6@intel.com>

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


On 24-04-2024 17:55, Rodrigo Vivi wrote:
> On Wed, Apr 24, 2024 at 08:50:45AM +0530, Ghimiray, Himal Prasad wrote:
>>                                                                                  
>>     Hi Rodrigo,
>>                                                                                  
>>     The debugfs entry introduced in [PATCH 4/4] of the series offers the same
>>     functionality as the modparams provided. Do you perceive any additional
>>     value in using this modparam?
>>                                                                                  
>>     The behavior of loading the module without using modparams and setting
>>     debugfs mode to 2 before executing the workload is identical to loading
>>     the driver module with the modparam xe_modparam.wedged_mode = 2.
> yes, they are.
> But there are situations where the hang could be happening at boot time.



Oh, I get it now! With this explanation,  patch LGTM

Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>


> That's what the modparam is for. SV teams wouldn't have a way to debug
> the hangs on boot. But in general the debugfs is enough for most of the
> cases and better because it is per device and not for all devices driven
> by the module.
>
>>                                                                                  
>>     BR
>>                                                                                  
>>     Himal
>>                                                                                  
>>      struct init_funcs {
>>             int (*init)(void);
>>             void (*exit)(void);
>>     diff --git a/drivers/gpu/drm/xe/xe_module.h b/drivers/gpu/drm/xe/xe_module.h
>>     index b369984f08ec..61a0d28a28c8 100644
>>     --- a/drivers/gpu/drm/xe/xe_module.h
>>     +++ b/drivers/gpu/drm/xe/xe_module.h
>>     @@ -21,6 +21,7 @@ struct xe_modparam {
>>      #ifdef CONFIG_PCI_IOV
>>             unsigned int max_vfs;
>>      #endif
>>     +       int wedged_mode;
>>      };
>>                                                                                  
>>      extern struct xe_modparam xe_modparam;
>>
>> References
>>
>>     Visible links
>>     1.mailto:matthew.brost@intel.com
>>     2.mailto:dhirschfeld@habana.ai
>>     3.mailto:lucas.demarchi@intel.com
>>     4.mailto:alan.previn.teres.alexis@intel.com
>>     5.mailto:himanshu.somaiya@intel.com
>>     6.mailto:lucas.demarchi@intel.com
>>     7.mailto:rodrigo.vivi@intel.com
>>     8.https://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n
>>     9.https://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n

[-- Attachment #2: Type: text/html, Size: 5999 bytes --]

  reply	other threads:[~2024-04-24 17:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 22:18 [PATCH 1/4] drm/xe: Introduce a simple wedged state Rodrigo Vivi
2024-04-23 22:18 ` [PATCH 2/4] drm/xe: declare wedged upon GuC load failure Rodrigo Vivi
2024-04-23 22:18 ` [PATCH 3/4] drm/xe: Force wedged state and block GT reset upon any GPU hang Rodrigo Vivi
2024-04-24  3:20   ` Ghimiray, Himal Prasad
2024-04-24 12:25     ` Rodrigo Vivi
2024-04-24 17:01       ` Ghimiray, Himal Prasad [this message]
2024-04-23 22:18 ` [PATCH 4/4] drm/xe: Introduce the wedged_mode debugfs Rodrigo Vivi
2024-04-24  3:29   ` Ghimiray, Himal Prasad
2024-04-23 22:29 ` ✓ CI.Patch_applied: success for series starting with [1/4] drm/xe: Introduce a simple wedged state Patchwork
2024-04-23 22:30 ` ✓ CI.checkpatch: " Patchwork
2024-04-23 22:31 ` ✓ CI.KUnit: " Patchwork
2024-04-23 22:52 ` ✓ CI.Build: " Patchwork
2024-04-23 22:55 ` ✓ CI.Hooks: " Patchwork
2024-04-23 22:56 ` ✓ CI.checksparse: " Patchwork
2024-04-23 23:50 ` ✓ CI.BAT: " Patchwork
2024-04-24 12:42 ` ✗ CI.FULL: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-04-09 22:15 [PATCH 1/4] " Rodrigo Vivi
2024-04-09 22:15 ` [PATCH 3/4] drm/xe: Force wedged state and block GT reset upon any GPU hang Rodrigo Vivi
2024-04-10 17:58   ` Matthew Brost
2024-04-16 17:19   ` Lucas De Marchi
2024-04-16 19:08     ` Rodrigo Vivi
2024-04-03 15:07 [PATCH 0/4] Introduce a wedged state Rodrigo Vivi
2024-04-03 15:07 ` [PATCH 3/4] drm/xe: Force wedged state and block GT reset upon any GPU hang Rodrigo Vivi
2024-04-04 17:52   ` Matthew Brost
2024-04-04 18:01     ` Rodrigo Vivi

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=668f4543-dab7-4d7f-a2b8-595e5ddad465@intel.com \
    --to=himal.prasad.ghimiray@intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=dhirschfeld@habana.ai \
    --cc=himanshu.somaiya@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    /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