From: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: paulo.r.zanoni@intel.com, chris.p.wilson@intel.com,
thomas.hellstrom@intel.com, matthew.auld@intel.com,
daniel.vetter@intel.com, christian.koenig@amd.com
Subject: [Intel-gfx] [PATCH v6 0/3] drm/doc/rfc: i915 VM_BIND feature design + uapi
Date: Fri, 24 Jun 2022 10:49:33 -0700 [thread overview]
Message-ID: <20220624174936.1065-1-niranjana.vishwanathapura@intel.com> (raw)
This is the i915 driver VM_BIND feature design RFC patch series along
with the required uapi definition and description of intended use cases.
v2: Reduce the scope to simple Mesa use case.
Remove all compute related uapi, vm_bind/unbind queue support and
only support a timeline out fence instead of an in/out timeline
fence array.
v3: Expand documentation on dma-resv usage, TLB flushing, execbuf3 and
VM_UNBIND. Add FENCE_VALID and TLB_FLUSH flags.
v4: Remove I915_GEM_VM_BIND_TLB_FLUSH flag and add additional
uapi documentation for vm_bind/unbind.
v5: Update TLB flushing documentation.
Add version support to stage implementation.
v6: Define and use drm_i915_gem_timeline_fence structure for
execbuf3 and vm_bind/unbind timeline fences.
Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Niranjana Vishwanathapura (3):
drm/doc/rfc: VM_BIND feature design document
drm/i915: Update i915 uapi documentation
drm/doc/rfc: VM_BIND uapi definition
Documentation/gpu/rfc/i915_vm_bind.h | 286 +++++++++++++++++++++++++
Documentation/gpu/rfc/i915_vm_bind.rst | 246 +++++++++++++++++++++
Documentation/gpu/rfc/index.rst | 4 +
include/uapi/drm/i915_drm.h | 205 ++++++++++++++----
4 files changed, 696 insertions(+), 45 deletions(-)
create mode 100644 Documentation/gpu/rfc/i915_vm_bind.h
create mode 100644 Documentation/gpu/rfc/i915_vm_bind.rst
--
2.21.0.rc0.32.g243a4c7e27
next reply other threads:[~2022-06-24 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 17:49 Niranjana Vishwanathapura [this message]
2022-06-24 17:49 ` [Intel-gfx] [PATCH v6 1/3] drm/doc/rfc: VM_BIND feature design document Niranjana Vishwanathapura
2022-06-24 19:31 ` Daniel Vetter
2022-06-24 17:49 ` [Intel-gfx] [PATCH v6 2/3] drm/i915: Update i915 uapi documentation Niranjana Vishwanathapura
2022-06-24 19:38 ` Daniel Vetter
2022-06-25 19:08 ` Niranjana Vishwanathapura
2022-06-24 17:49 ` [Intel-gfx] [PATCH v6 3/3] drm/doc/rfc: VM_BIND uapi definition Niranjana Vishwanathapura
2022-06-24 20:07 ` Daniel Vetter
2022-06-25 19:02 ` Niranjana Vishwanathapura
2022-06-26 1:08 ` Niranjana Vishwanathapura
2022-06-27 9:07 ` Daniel Vetter
2022-06-27 8:55 ` Daniel Vetter
2022-06-30 6:21 ` Niranjana Vishwanathapura
2022-06-24 18:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/doc/rfc: i915 VM_BIND feature design + uapi Patchwork
2022-06-24 18:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-06-24 18:31 ` [Intel-gfx] ✗ Fi.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=20220624174936.1065-1-niranjana.vishwanathapura@intel.com \
--to=niranjana.vishwanathapura@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=thomas.hellstrom@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;
as well as URLs for NNTP newsgroup(s).