From: Matthew Auld <matthew.auld@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH v7 0/3] uAPI bits for small-bar
Date: Fri, 14 Jul 2023 15:48:15 +0100 [thread overview]
Message-ID: <20230714144814.574873-5-matthew.auld@intel.com> (raw)
The remaining small-bar bits. Add support for requesting CPU access for VRAM
buffers. Also expose this to userspace, along with various bits of related
accounting. Finally turn on small-bar support.
IGT: https://patchwork.freedesktop.org/series/115786/
Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/23781
v2: Various improvements suggested by José
v3: Add some kernel-doc (Gwan-gyeong)
v4: Small kernel-doc fix, also use the correct version of the struct
v5: Rebase on latest xe-next changes
v6: Rebase on the needed PL_TT -> PL_TT move fix, plus fix some other issues
reported by José when running actual workloads
v7: Rebase on latest xe-next changes
--
2.41.0
next reply other threads:[~2023-07-14 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 14:48 Matthew Auld [this message]
2023-07-14 14:48 ` [Intel-xe] [PATCH v7 1/3] drm/xe/bo: support tiered vram allocation for small-bar Matthew Auld
2023-07-14 14:48 ` [Intel-xe] [PATCH v7 2/3] drm/xe/uapi: add the userspace bits " Matthew Auld
2023-07-14 14:48 ` [Intel-xe] [PATCH v7 3/3] drm/xe: fully turn on small-bar support Matthew Auld
2023-07-14 14:50 ` [Intel-xe] ✓ CI.Patch_applied: success for uAPI bits for small-bar (rev8) Patchwork
2023-07-14 14:50 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-14 14:51 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-14 14:55 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-14 14:56 ` [Intel-xe] ✗ CI.Hooks: 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=20230714144814.574873-5-matthew.auld@intel.com \
--to=matthew.auld@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