From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [PATCH v13 03/10] drm/xe/debugfs: grab mem_access around forcewake
Date: Thu, 13 Jul 2023 14:22:48 +0100 [thread overview]
Message-ID: <20230713132244.459605-15-matthew.auld@intel.com> (raw)
In-Reply-To: <20230713132244.459605-12-matthew.auld@intel.com>
We need keep the device awake when performing any kind of mmio operation.
Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/279
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/gpu/drm/xe/xe_debugfs.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_debugfs.c b/drivers/gpu/drm/xe/xe_debugfs.c
index 7827a785b020..047341d5689a 100644
--- a/drivers/gpu/drm/xe/xe_debugfs.c
+++ b/drivers/gpu/drm/xe/xe_debugfs.c
@@ -70,6 +70,8 @@ static int forcewake_open(struct inode *inode, struct file *file)
struct xe_gt *gt;
u8 id;
+ xe_device_mem_access_get(xe);
+
for_each_gt(gt, xe, id)
XE_WARN_ON(xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL));
@@ -85,6 +87,8 @@ static int forcewake_release(struct inode *inode, struct file *file)
for_each_gt(gt, xe, id)
XE_WARN_ON(xe_force_wake_put(gt_to_fw(gt), XE_FORCEWAKE_ALL));
+ xe_device_mem_access_put(xe);
+
return 0;
}
--
2.41.0
next prev parent reply other threads:[~2023-07-13 13:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:22 [Intel-xe] [PATCH v13 00/10] xe_device_mem_access fixes and related bits Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 01/10] drm/xe: fix xe_device_mem_access_get() races Matthew Auld
2023-07-14 13:04 ` Gupta, Anshuman
2023-07-14 15:34 ` Rodrigo Vivi
2023-07-17 10:53 ` Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 02/10] drm/xe/vm: tidy up xe_runtime_pm usage Matthew Auld
2023-07-13 13:22 ` Matthew Auld [this message]
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 04/10] drm/xe/guc_pc: add missing mem_access for freq_rpe_show Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 05/10] drm/xe/mmio: grab mem_access in xe_mmio_ioctl Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 06/10] drm/xe: ensure correct access_put ordering Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 07/10] drm/xe: drop xe_device_mem_access_get() from guc_ct_send Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 08/10] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 09/10] drm/xe: drop xe_device_mem_access_get() from invalidation_vma Matthew Auld
2023-07-13 13:22 ` [Intel-xe] [PATCH v13 10/10] drm/xe: add lockdep annotation for xe_device_mem_access_get() Matthew Auld
2023-07-14 15:40 ` Rodrigo Vivi
2023-07-13 15:29 ` [Intel-xe] ✓ CI.Patch_applied: success for xe_device_mem_access fixes and related bits (rev3) Patchwork
2023-07-13 15:30 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-13 15:31 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-13 15:35 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-13 15:35 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-13 15:36 ` [Intel-xe] ✓ CI.checksparse: " 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=20230713132244.459605-15-matthew.auld@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--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