From: Matthew Brost <matthew.brost@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: michal.mrozek@intel.com, francois.dugast@intel.com,
thomas.hellstrom@linux.intel.com,
himal.prasad.ghimiray@intel.com
Subject: [PATCH v3 0/2] Enhance SVM stats
Date: Tue, 3 Jun 2025 16:34:43 -0700 [thread overview]
Message-ID: <20250603233445.2304383-1-matthew.brost@intel.com> (raw)
Add ability to clear GT stats and add more SVM stats for profiling.
Scripts should be able to be built on top of stats to breakdown time
spent in parts of the SVM page fault handler, bandwidth of copy engine,
etc... Will help showing concrete performance improvements when
implementing SVM optimizations.
Open suggestions of more stats. Prefetch not considered - can be done in
a follow up.
v2:
- Include local changes missed in first rev
v3:
- More stats after putting together script to parse
Matthew Brost (2):
drm/xe: Add clear_stats GT debugfs
drm/xe: Add more SVM GT stats
drivers/gpu/drm/xe/xe_gt_debugfs.c | 22 ++
drivers/gpu/drm/xe/xe_gt_stats.c | 47 +++++
drivers/gpu/drm/xe/xe_gt_stats.h | 1 +
drivers/gpu/drm/xe/xe_gt_stats_types.h | 33 +++
drivers/gpu/drm/xe/xe_svm.c | 274 ++++++++++++++++++++++++-
5 files changed, 369 insertions(+), 8 deletions(-)
--
2.34.1
next reply other threads:[~2025-06-03 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 23:34 Matthew Brost [this message]
2025-06-03 23:34 ` [PATCH v3 1/2] drm/xe: Add clear_stats GT debugfs Matthew Brost
2025-06-27 16:24 ` Francois Dugast
2025-06-03 23:34 ` [PATCH v3 2/2] drm/xe: Add more SVM GT stats Matthew Brost
2025-06-04 10:24 ` Francois Dugast
2025-06-04 14:13 ` Matthew Brost
2025-06-27 16:29 ` Francois Dugast
2025-06-27 17:37 ` Matthew Brost
2025-06-03 23:38 ` ✓ CI.Patch_applied: success for Enhance SVM stats Patchwork
2025-06-03 23:38 ` ✗ CI.checkpatch: warning " Patchwork
2025-06-03 23:39 ` ✗ CI.KUnit: failure " 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=20250603233445.2304383-1-matthew.brost@intel.com \
--to=matthew.brost@intel.com \
--cc=francois.dugast@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.mrozek@intel.com \
--cc=thomas.hellstrom@linux.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