From: Pallavi Mishra <pallavi.mishra@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH v2 0/3] drm/xe: CLOS Based Cache Reservation support
Date: Wed, 10 Jan 2024 05:27:55 +0530 [thread overview]
Message-ID: <20240109235758.1432987-1-pallavi.mishra@intel.com> (raw)
Xe API supports an optional extension for allowing Apps to reserve
portions of the GPU Caches for exclusive use. This allows the App
to separate latency/bandwidth sensitive workloads from all other
workloads.
PVC and XE2 expose control over each Cache through the Class of Service (CLOS)
feature. CLOS allows to define which portions of a cache may be
used for a given allocation through a set of Waymask controls grouped
into multiple sets.
For each CLOS set, and supported cache, there is a Waymask to configure
the Ways in that cache that may be used to cache memory requests for that
CLOS.
Clients must specify a PAT index in the same region mapped to previously
reserved CLOS level
TODO:
- Need to add sysfs for setting limits
- Need to handle BO host cache type
v2 (Brian)
- split into smaller patches
- Address review comments in xe_clos.c
- Change implementation of xe_pat_index_clos_check()
Pallavi Mishra (3):
drm/xe/uapi: CLOS uapi support
drm/xe: Introduce xe_clos.c
drm/xe: Add CLOS specific initializations
drivers/gpu/drm/xe/Makefile | 1 +
drivers/gpu/drm/xe/xe_clos.c | 264 +++++++++++++++++++++++++++
drivers/gpu/drm/xe/xe_clos.h | 31 ++++
drivers/gpu/drm/xe/xe_device.c | 15 ++
drivers/gpu/drm/xe/xe_device_types.h | 22 +++
drivers/gpu/drm/xe/xe_pat.c | 36 ++++
drivers/gpu/drm/xe/xe_pat.h | 9 +
drivers/gpu/drm/xe/xe_pci.c | 4 +
drivers/gpu/drm/xe/xe_vm.c | 12 ++
include/uapi/drm/xe_drm.h | 71 +++++++
10 files changed, 465 insertions(+)
create mode 100644 drivers/gpu/drm/xe/xe_clos.c
create mode 100644 drivers/gpu/drm/xe/xe_clos.h
--
2.25.1
next reply other threads:[~2024-01-09 23:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 23:57 Pallavi Mishra [this message]
2024-01-09 23:57 ` [PATCH v2 1/3] drm/xe/uapi: CLOS uapi support Pallavi Mishra
2024-01-12 1:04 ` Welty, Brian
2024-01-09 23:57 ` [PATCH v2 2/3] drm/xe: Introduce xe_clos.c Pallavi Mishra
2024-01-12 0:41 ` Welty, Brian
2024-01-12 18:44 ` Mishra, Pallavi
2024-01-09 23:57 ` [PATCH v2 3/3] drm/xe: Add CLOS specific initializations Pallavi Mishra
2024-01-12 1:02 ` Welty, Brian
2024-01-12 18:59 ` Mishra, Pallavi
2024-01-12 19:46 ` Welty, Brian
2024-01-16 18:49 ` Mishra, Pallavi
2024-01-10 1:49 ` ✓ CI.Patch_applied: success for drm/xe: CLOS Based Cache Reservation support Patchwork
2024-01-10 1:49 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-10 1:50 ` ✓ CI.KUnit: success " Patchwork
2024-01-10 1:58 ` ✓ CI.Build: " Patchwork
2024-01-10 1:58 ` ✗ CI.Hooks: failure " Patchwork
2024-01-10 1:59 ` ✓ CI.checksparse: success " Patchwork
2024-01-10 2:35 ` ✗ CI.BAT: 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=20240109235758.1432987-1-pallavi.mishra@intel.com \
--to=pallavi.mishra@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