From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Fei Yang <fei.yang@intel.com>
Cc: Lihao Gu <lihao.gu@intel.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>,
DRI Devel <dri-devel@lists.freedesktop.org>,
Carl Zhang <carl.zhang@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Matt Roper <matthew.d.roper@intel.com>
Subject: [Intel-gfx] [PATCH v17 0/1] drm/i915: Allow user to set cache at BO creation
Date: Tue, 6 Jun 2023 12:00:41 +0200 [thread overview]
Message-ID: <20230606100042.482345-1-andi.shyti@linux.intel.com> (raw)
From: Fei Yang <fei.yang@intel.com>
This series introduce a new extension for GEM_CREATE,
1. end support for set caching ioctl [PATCH 1/2]
2. add set_pat extension for gem_create [PATCH 2/2]
v2: drop one patch that was merged separately
commit 341ad0e8e254 ("drm/i915/mtl: Add PTE encode function")
v3: rebased on https://patchwork.freedesktop.org/series/117082/
v4: fix missing unlock introduced in v3, and
solve a rebase conflict
v5: replace obj->cache_level with pat_set_by_user,
fix i915_cache_level_str() for legacy platforms.
v6: rebased on https://patchwork.freedesktop.org/series/117480/
v7: rebased on https://patchwork.freedesktop.org/series/117528/
v8: dropped the two dependent patches that has been merged
separately. Add IGT link and Tested-by (MESA).
v9: addressing comments (Andi)
v10: acked-by and tested-by MESA
v11: drop "end support for set caching ioctl" (merged)
remove tools/include/uapi/drm/i915_drm.h
v12: drop Bspec reference in comment. add to commit message instead
v13: sent to test with igt@gem_create@create-ext-set-pat
v14: sent to test with igt@gem_create@create-ext-set-pat
v15: update commit message with documentation note and t-b/a-b from
Media driver folks.
v16: limiting the extension to GEN12+
v17: limiting the extension to Meteor Lake
Test-with: 20230606095123.476130-2-andi.shyti@linux.intel.com
Fei Yang (1):
drm/i915: Allow user to set cache at BO creation
drivers/gpu/drm/i915/gem/i915_gem_create.c | 40 +++++++++++++++++++++
drivers/gpu/drm/i915/gem/i915_gem_object.c | 6 ++++
include/uapi/drm/i915_drm.h | 41 ++++++++++++++++++++++
3 files changed, 87 insertions(+)
--
2.40.1
next reply other threads:[~2023-06-06 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 10:00 Andi Shyti [this message]
2023-06-06 10:00 ` [Intel-gfx] [PATCH v17 1/1] drm/i915: Allow user to set cache at BO creation Andi Shyti
2023-06-06 10:10 ` Tvrtko Ursulin
2023-06-06 10:18 ` Andi Shyti
2023-06-06 11:12 ` Joonas Lahtinen
2023-06-06 11:14 ` Andi Shyti
2023-06-07 3:40 ` Zhang, Carl
2023-06-07 5:11 ` Andi Shyti
2023-06-07 5:21 ` Zhang, Carl
2023-06-09 9:59 ` Andi Shyti
2023-06-09 15:12 ` Yang, Fei
2023-06-11 14:43 ` Zhang, Carl
2023-06-07 15:01 ` Andi Shyti
2023-06-07 15:46 ` Andi Shyti
2023-06-06 14:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-06-06 14:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-06 14:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 3:23 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230606100042.482345-1-andi.shyti@linux.intel.com \
--to=andi.shyti@linux.intel.com \
--cc=carl.zhang@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=fei.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lihao.gu@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=tvrtko.ursulin@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