From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [PATCH v14 05/10] drm/xe/mmio: grab mem_access in xe_mmio_ioctl
Date: Mon, 17 Jul 2023 12:25:08 +0100 [thread overview]
Message-ID: <20230717112502.32379-17-matthew.auld@intel.com> (raw)
In-Reply-To: <20230717112502.32379-12-matthew.auld@intel.com>
Any kind of device memory access should first ensure the device is not
suspended, mmio included.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
---
drivers/gpu/drm/xe/xe_mmio.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_mmio.c b/drivers/gpu/drm/xe/xe_mmio.c
index 448b874c7a3c..8d0f07261bfd 100644
--- a/drivers/gpu/drm/xe/xe_mmio.c
+++ b/drivers/gpu/drm/xe/xe_mmio.c
@@ -483,6 +483,7 @@ int xe_mmio_ioctl(struct drm_device *dev, void *data,
*/
reg = XE_REG(args->addr);
+ xe_device_mem_access_get(xe);
xe_force_wake_get(gt_to_fw(gt), XE_FORCEWAKE_ALL);
if (args->flags & DRM_XE_MMIO_WRITE) {
@@ -526,6 +527,7 @@ int xe_mmio_ioctl(struct drm_device *dev, void *data,
exit:
xe_force_wake_put(gt_to_fw(gt), XE_FORCEWAKE_ALL);
+ xe_device_mem_access_put(xe);
return ret;
}
--
2.41.0
next prev parent reply other threads:[~2023-07-17 11:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 11:25 [Intel-xe] [PATCH v14 00/10] xe_device_mem_access fixes and related bits Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 01/10] drm/xe: fix xe_device_mem_access_get() races Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 02/10] drm/xe/vm: tidy up xe_runtime_pm usage Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 03/10] drm/xe/debugfs: grab mem_access around forcewake Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 04/10] drm/xe/guc_pc: add missing mem_access for freq_rpe_show Matthew Auld
2023-07-17 11:25 ` Matthew Auld [this message]
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 06/10] drm/xe: ensure correct access_put ordering Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 07/10] drm/xe: drop xe_device_mem_access_get() from guc_ct_send Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 08/10] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 09/10] drm/xe: drop xe_device_mem_access_get() from invalidation_vma Matthew Auld
2023-07-17 11:25 ` [Intel-xe] [PATCH v14 10/10] drm/xe: add lockdep annotation for xe_device_mem_access_get() Matthew Auld
2023-07-17 11:28 ` [Intel-xe] ✓ CI.Patch_applied: success for xe_device_mem_access fixes and related bits (rev4) Patchwork
2023-07-17 11:28 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-17 11:29 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-17 11:33 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-17 11:34 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-17 11:35 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-18 12:50 ` [Intel-xe] ✓ CI.Patch_applied: success for xe_device_mem_access fixes and related bits (rev6) Patchwork
2023-07-18 12:50 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-18 12:51 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-18 12:55 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-18 12:56 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-18 12:57 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-18 13:31 ` [Intel-xe] ○ CI.BAT: info " 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=20230717112502.32379-17-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