All of 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 11/11] drm/xe: Disable panic_on_warn for testing purposes
Date: Tue, 31 Oct 2023 15:21:33 +0100	[thread overview]
Message-ID: <20231031142133.17129-11-thomas.hellstrom@linux.intel.com> (raw)
In-Reply-To: <20231031142133.17129-1-thomas.hellstrom@linux.intel.com>

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

diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
index 8341acf66e5f..5374c548b61d 100644
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@ -278,7 +278,7 @@ int xe_device_probe(struct xe_device *xe)
 	u8 id;
 
 	xe_pat_init_early(xe);
-
+	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


  parent reply	other threads:[~2023-10-31 14:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 14:21 [Intel-xe] [CI 01/11] drm/gpuvm: convert WARN() to drm_WARN() variants Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 02/11] drm/gpuvm: add common dma-resv per struct drm_gpuvm Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 03/11] drm/xe: Adjust to "drm/gpuvm: add common dma-resv per struct drm_gpuvm" Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 04/11] drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 05/11] drm/xe: Adjust to commit "drm/gpuvm: add drm_gpuvm_flags to drm_gpuvm" Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 06/11] drm/gpuvm: add an abstraction for a VM / BO combination Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 07/11] drm/xe: Adjust to commit "drm/gpuvm: add an abstraction for a VM/BO combination" Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 08/11] drm/gpuvm: track/lock/validate external/evicted objects Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 09/11] drm/xe: Adapt to GPUVM tracking of external / evicted objects Thomas Hellström
2023-10-31 14:21 ` [Intel-xe] [CI 10/11] drm/xe: Use DRM_GPUVM_RESV_PROTECTED for gpuvm Thomas Hellström
2023-10-31 14:21 ` Thomas Hellström [this message]
2023-10-31 16:05 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [CI,01/11] drm/gpuvm: convert WARN() to drm_WARN() variants Patchwork
2023-10-31 16:06 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-10-31 16:07 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-10-31 16:14 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-10-31 16:14 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-10-31 16:16 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-10-31 16:56 ` [Intel-xe] ✗ CI.BAT: failure " 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=20231031142133.17129-11-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.