From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH] drm/xe: Check pat.ops before dumping PAT settings
Date: Fri, 5 Apr 2024 16:36:25 +0200 [thread overview]
Message-ID: <20240405143625.935-1-michal.wajdeczko@intel.com> (raw)
We may leave pat.ops unset when running on brand new platform or
when running as a VF. While the former is unlikely, the latter
is valid (future) use case and will cause NPD when someone will
try to dump PAT settings by debugfs.
It's better to check pointer to pat.ops instead of specific .dump
hook, as we have this hook always defined for every .ops variant.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/xe_pat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_pat.c b/drivers/gpu/drm/xe/xe_pat.c
index 66d8e3dd8237..f0031c2e9818 100644
--- a/drivers/gpu/drm/xe/xe_pat.c
+++ b/drivers/gpu/drm/xe/xe_pat.c
@@ -447,7 +447,7 @@ void xe_pat_dump(struct xe_gt *gt, struct drm_printer *p)
{
struct xe_device *xe = gt_to_xe(gt);
- if (!xe->pat.ops->dump)
+ if (!xe->pat.ops)
return;
xe->pat.ops->dump(gt, p);
--
2.43.0
next reply other threads:[~2024-04-05 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 14:36 Michal Wajdeczko [this message]
2024-04-05 17:21 ` ✓ CI.Patch_applied: success for drm/xe: Check pat.ops before dumping PAT settings Patchwork
2024-04-05 17:21 ` ✓ CI.checkpatch: " Patchwork
2024-04-05 17:22 ` ✓ CI.KUnit: " Patchwork
2024-04-05 17:34 ` ✓ CI.Build: " Patchwork
2024-04-05 17:37 ` ✓ CI.Hooks: " Patchwork
2024-04-05 17:39 ` ✓ CI.checksparse: " Patchwork
2024-04-05 18:03 ` ✓ CI.BAT: " Patchwork
2024-04-08 7:23 ` [PATCH] " Piotr Piórkowski
2024-04-08 9:06 ` Michal Wajdeczko
2024-04-08 11:48 ` Piotr Piórkowski
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=20240405143625.935-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@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