From: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH] fixup! fixup! drm/xe/pmu: Enable PMU interface
Date: Thu, 21 Sep 2023 17:06:37 +0530 [thread overview]
Message-ID: <20230921113637.386651-1-aravind.iddamsetty@linux.intel.com> (raw)
Signed-off-by: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
---
include/uapi/drm/xe_drm.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
index 6ab85c7fed36..d48d8e3c898c 100644
--- a/include/uapi/drm/xe_drm.h
+++ b/include/uapi/drm/xe_drm.h
@@ -1056,12 +1056,14 @@ struct drm_xe_vm_madvise {
/**
* DOC: XE PMU event config IDs
*
- * Check 'man perf_event_open' to use these ID's in 'struct perf_event_attr'
- * as part of perf_event_open syscall to read a particular event.
+ * Check 'man perf_event_open' to use the ID's XE_PMU_XXXX listed in xe_drm.h
+ * in 'struct perf_event_attr' as part of perf_event_open syscall to read a
+ * particular event.
*
* For example to open the XE_PMU_INTERRUPTS(0):
*
* .. code-block:: C
+ *
* struct perf_event_attr attr;
* long long count;
* int cpu = 0;
--
2.25.1
next reply other threads:[~2023-09-21 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 11:36 Aravind Iddamsetty [this message]
2023-09-21 12:27 ` [Intel-xe] [PATCH] fixup! fixup! drm/xe/pmu: Enable PMU interface Gustavo Sousa
2023-09-21 12:38 ` [Intel-xe] ✗ CI.Patch_applied: failure for " Patchwork
2023-09-22 5:04 ` [Intel-xe] ✓ CI.Patch_applied: success for fixup! fixup! drm/xe/pmu: Enable PMU interface (rev2) Patchwork
2023-09-22 5:04 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-22 5:05 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-22 5:12 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-22 5:12 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-22 5:14 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-22 5:48 ` [Intel-xe] ✓ CI.BAT: " 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=20230921113637.386651-1-aravind.iddamsetty@linux.intel.com \
--to=aravind.iddamsetty@linux.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