Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [CI HAX v2] drm/xe: Disable panic_on_warn for testing purposes
Date: Thu,  2 Nov 2023 15:31:27 +0100	[thread overview]
Message-ID: <20231102143127.2692-1-thomas.hellstrom@linux.intel.com> (raw)

Turn off panic_on_warn and also force a checkpatch.pl error.

Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
---
 drivers/gpu/drm/xe/xe_device.c | 3 ++-
 kernel/panic.c                 | 1 +
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
index 8341acf66e5f..bc69d83d5498 100644
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@ -278,7 +278,8 @@ int xe_device_probe(struct xe_device *xe)
 	u8 id;
 
 	xe_pat_init_early(xe);
-
+	if(true)
+		panic_on_warn = 0;
 	xe->info.mem_region_mask = 1;
 	err = xe_display_init_nommio(xe);
 	if (err)
diff --git a/kernel/panic.c b/kernel/panic.c
index bc59531848e4..1c8057027f20 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -59,6 +59,7 @@ static int pause_on_oops_flag;
 static DEFINE_SPINLOCK(pause_on_oops_lock);
 bool crash_kexec_post_notifiers;
 int panic_on_warn __read_mostly;
+EXPORT_SYMBOL_GPL(panic_on_warn);
 unsigned long panic_on_taint;
 bool panic_on_taint_nousertaint = false;
 static unsigned int warn_limit __read_mostly;
-- 
2.41.0


             reply	other threads:[~2023-11-02 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 14:31 Thomas Hellström [this message]
2023-11-02 15:09 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Disable panic_on_warn for testing purposes (rev2) Patchwork
2023-11-02 15:09 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-11-02 15:10 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-11-02 15:17 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-02 15:18 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-02 15:19 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-08  8:27 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-11-08  9:55 ` [Intel-xe] ✓ CI.Patch_applied: success for drm/xe: Disable panic_on_warn for testing purposes (rev3) Patchwork
2023-11-08  9:55 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-11-08  9:57 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-11-08 10:04 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-08 10:04 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-11-08 10:06 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-11-08 10:43 ` [Intel-xe] ✓ CI.BAT: " Patchwork

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=20231102143127.2692-1-thomas.hellstrom@linux.intel.com \
    --to=thomas.hellstrom@linux.intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    /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