From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [PATCH v15 04/10] drm/xe/guc_pc: add missing mem_access for freq_rpe_show
Date: Wed, 19 Jul 2023 09:38:06 +0100 [thread overview]
Message-ID: <20230719083801.182123-16-matthew.auld@intel.com> (raw)
In-Reply-To: <20230719083801.182123-12-matthew.auld@intel.com>
The mem_access is meant to cover any kind of device level memory access,
mmio included.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Anshuman Gupta <anshuman.gupta@intel.com>
Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
---
drivers/gpu/drm/xe/xe_guc_pc.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_guc_pc.c b/drivers/gpu/drm/xe/xe_guc_pc.c
index 03dfbde29fe5..0927cb669603 100644
--- a/drivers/gpu/drm/xe/xe_guc_pc.c
+++ b/drivers/gpu/drm/xe/xe_guc_pc.c
@@ -422,8 +422,12 @@ static ssize_t freq_rpe_show(struct device *dev,
struct device_attribute *attr, char *buf)
{
struct xe_guc_pc *pc = dev_to_pc(dev);
+ struct xe_gt *gt = pc_to_gt(pc);
+ struct xe_device *xe = gt_to_xe(gt);
+ xe_device_mem_access_get(xe);
pc_update_rp_values(pc);
+ xe_device_mem_access_put(xe);
return sysfs_emit(buf, "%d\n", pc->rpe_freq);
}
static DEVICE_ATTR_RO(freq_rpe);
--
2.41.0
next prev parent reply other threads:[~2023-07-19 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 8:38 [Intel-xe] [PATCH v15 00/10] xe_device_mem_access fixes and related bits Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 01/10] drm/xe: fix xe_device_mem_access_get() races Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 02/10] drm/xe/vm: tidy up xe_runtime_pm usage Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 03/10] drm/xe/debugfs: grab mem_access around forcewake Matthew Auld
2023-07-19 8:38 ` Matthew Auld [this message]
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 05/10] drm/xe/mmio: grab mem_access in xe_mmio_ioctl Matthew Auld
2023-07-28 21:05 ` Matt Roper
2023-07-31 18:44 ` Rodrigo Vivi
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 06/10] drm/xe: ensure correct access_put ordering Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 07/10] drm/xe: drop xe_device_mem_access_get() from guc_ct_send Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 08/10] drm/xe/ggtt: prime ggtt->lock against FS_RECLAIM Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 09/10] drm/xe: drop xe_device_mem_access_get() from invalidation_vma Matthew Auld
2023-07-19 8:38 ` [Intel-xe] [PATCH v15 10/10] drm/xe: add lockdep annotation for xe_device_mem_access_get() Matthew Auld
2023-07-19 9:31 ` [Intel-xe] ✓ CI.Patch_applied: success for xe_device_mem_access fixes and related bits (rev7) Patchwork
2023-07-19 9:31 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-19 9:32 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-19 9:36 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-19 9:36 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-19 9:38 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-07-19 10:13 ` [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=20230719083801.182123-16-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