From: Andi Shyti <andi.shyti@linux.intel.com>
To: fei.yang@intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation
Date: Tue, 23 May 2023 10:37:22 +0200 [thread overview]
Message-ID: <ZGx7Quf+ArHnXOR0@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230519051103.3404990-1-fei.yang@intel.com>
Hi Fei,
finally... pushed in drm-intel-gt-next! :)
Andi
On Thu, May 18, 2023 at 10:11:01PM -0700, fei.yang@intel.com wrote:
> 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
>
> Fei Yang (2):
> drm/i915/mtl: end support for set caching ioctl
> drm/i915: Allow user to set cache at BO creation
>
> drivers/gpu/drm/i915/gem/i915_gem_create.c | 36 +++++++++++++++++++
> drivers/gpu/drm/i915/gem/i915_gem_domain.c | 3 ++
> drivers/gpu/drm/i915/gem/i915_gem_object.c | 6 ++++
> drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 9 ++++-
> include/uapi/drm/i915_drm.h | 42 ++++++++++++++++++++++
> tools/include/uapi/drm/i915_drm.h | 42 ++++++++++++++++++++++
> 6 files changed, 137 insertions(+), 1 deletion(-)
>
> --
> 2.25.1
next prev parent reply other threads:[~2023-05-23 8:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 5:11 [Intel-gfx] [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-19 5:11 ` [Intel-gfx] [PATCH v10 1/2] drm/i915/mtl: end support for set caching ioctl fei.yang
2023-05-19 5:11 ` [Intel-gfx] [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-21 4:30 ` Jordan Justen
2023-05-25 11:42 ` [Intel-gfx] Extension detection by enumeration vs attempt to use extension (Was: Re: [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation) Joonas Lahtinen
2023-05-22 11:52 ` [Intel-gfx] [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation Andi Shyti
2023-05-22 15:25 ` Jordan Justen
2023-05-22 15:30 ` Andi Shyti
2023-05-19 5:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Allow user to set cache at BO creation (rev10) Patchwork
2023-05-19 6:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-19 10:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-23 8:37 ` Andi Shyti [this message]
2023-05-24 11:56 ` [Intel-gfx] [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation Tvrtko Ursulin
2023-05-24 12:05 ` Tvrtko Ursulin
2023-05-24 12:19 ` Andi Shyti
2023-05-24 12:30 ` Andi Shyti
2023-05-24 12:52 ` Tvrtko Ursulin
2023-05-24 12:34 ` Tvrtko Ursulin
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=ZGx7Quf+ArHnXOR0@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fei.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@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