From: Francois Dugast <francois.dugast@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Francois Dugast <francois.dugast@intel.com>
Subject: [Intel-xe] [PATCH v2 0/3] Use Xe assert macros instead of XE_WARN_ON macro
Date: Wed, 30 Aug 2023 12:37:19 +0000 [thread overview]
Message-ID: <20230830123722.6-1-francois.dugast@intel.com> (raw)
Use the assert macros introduced by Michal Wajdeczko:
https://patchwork.freedesktop.org/series/121549/
Some occurrences of XE_WARN_ON are still present
as they will require a bit more refactoring.
v2:
- Move XE_WARN_ON -> drm_warn to a separate patch (Matt Roper)
- Only convert the instances where the condition evaluation is not
strictly needed (Matt Roper and Thomas Hellström)
Francois Dugast (2):
drm/xe: Replace XE_WARN_ON with drm_warn when just printing string
drm/xe: Use Xe assert macros instead of XE_WARN_ON macro
Michal Wajdeczko (1):
drm/xe: Introduce Xe assert macros
drivers/gpu/drm/xe/xe_assert.h | 177 ++++++++++++++++++++
drivers/gpu/drm/xe/xe_bb.c | 8 +-
drivers/gpu/drm/xe/xe_bo.c | 67 ++++----
drivers/gpu/drm/xe/xe_bo_evict.c | 4 +-
drivers/gpu/drm/xe/xe_device.c | 6 +-
drivers/gpu/drm/xe/xe_exec.c | 2 +-
drivers/gpu/drm/xe/xe_execlist.c | 12 +-
drivers/gpu/drm/xe/xe_force_wake.c | 4 +-
drivers/gpu/drm/xe/xe_force_wake.h | 6 +-
drivers/gpu/drm/xe/xe_ggtt.c | 14 +-
drivers/gpu/drm/xe/xe_gt.c | 1 +
drivers/gpu/drm/xe/xe_gt_clock.c | 2 +-
drivers/gpu/drm/xe/xe_gt_debugfs.c | 7 +-
drivers/gpu/drm/xe/xe_gt_pagefault.c | 3 +-
drivers/gpu/drm/xe/xe_gt_tlb_invalidation.c | 12 +-
drivers/gpu/drm/xe/xe_guc.c | 24 +--
drivers/gpu/drm/xe/xe_guc_ads.c | 22 +--
drivers/gpu/drm/xe/xe_guc_ct.c | 31 ++--
drivers/gpu/drm/xe/xe_guc_log.c | 4 +-
drivers/gpu/drm/xe/xe_guc_pc.c | 2 +-
drivers/gpu/drm/xe/xe_guc_submit.c | 74 ++++----
drivers/gpu/drm/xe/xe_huc.c | 3 +-
drivers/gpu/drm/xe/xe_hw_engine.c | 11 +-
drivers/gpu/drm/xe/xe_lrc.c | 9 +-
drivers/gpu/drm/xe/xe_migrate.c | 31 ++--
drivers/gpu/drm/xe/xe_mocs.c | 2 +-
drivers/gpu/drm/xe/xe_pt.c | 14 +-
drivers/gpu/drm/xe/xe_ring_ops.c | 13 +-
drivers/gpu/drm/xe/xe_sched_job.c | 2 +-
drivers/gpu/drm/xe/xe_uc.c | 2 +-
drivers/gpu/drm/xe/xe_uc_fw.c | 16 +-
drivers/gpu/drm/xe/xe_vm.c | 74 ++++----
drivers/gpu/drm/xe/xe_vm.h | 2 +-
drivers/gpu/drm/xe/xe_vm_madvise.c | 2 +-
drivers/gpu/drm/xe/xe_wopcm.c | 18 +-
35 files changed, 449 insertions(+), 232 deletions(-)
create mode 100644 drivers/gpu/drm/xe/xe_assert.h
--
2.34.1
next reply other threads:[~2023-08-30 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 12:37 Francois Dugast [this message]
2023-08-30 12:37 ` [Intel-xe] [PATCH v2 1/3] drm/xe: Replace XE_WARN_ON with drm_warn when just printing a string Francois Dugast
2023-09-06 14:38 ` Rodrigo Vivi
2023-08-30 12:37 ` [Intel-xe] [PATCH v2 2/3] drm/xe: Introduce Xe assert macros Francois Dugast
2023-08-30 12:37 ` [Intel-xe] [PATCH v2 3/3] drm/xe: Use Xe assert macros instead of XE_WARN_ON macro Francois Dugast
2023-09-06 14:38 ` Rodrigo Vivi
2023-09-06 19:46 ` Matt Roper
2023-08-30 14:22 ` [Intel-xe] ✓ CI.Patch_applied: success for Use Xe assert macros instead of XE_WARN_ON macro (rev2) Patchwork
2023-08-30 14:22 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-08-30 14:23 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-08-30 14:29 ` [Intel-xe] ✗ CI.Build: 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=20230830123722.6-1-francois.dugast@intel.com \
--to=francois.dugast@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