All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: fei.yang@intel.com, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 0/5] drm/i915: Allow user to set cache at BO creation
Date: Wed, 26 Apr 2023 11:38:11 +0100	[thread overview]
Message-ID: <c7cb1466-e698-ff3f-0572-4693c4b0025c@linux.intel.com> (raw)
In-Reply-To: <20230426062423.320519-1-fei.yang@intel.com>


On 26/04/2023 07:24, fei.yang@intel.com wrote:
> From: Fei Yang <fei.yang@intel.com>
> 
> The first three patches in this series are taken from
> https://patchwork.freedesktop.org/series/116868/
> These patches are included here because the last patch
> has dependency on the pat_index refactor.
> 
> This series is focusing on uAPI changes,
> 1. end support for set caching ioctl [PATCH 4/5]
> 2. add set_pat extension for gem_create [PATCH 5/5]
> 
> v2: drop one patch that was merged separately
>      341ad0e8e254 drm/i915/mtl: Add PTE encode function

Are the re-sends for stabilizing the series, or focusing on merge?

If the latter then opens are:

1) Link to Mesa MR reviewed and ready to merge.

2) IGT reviewed.

3) I raised an open that get/set_caching should not "lie" but return an 
error if set pat extension has been used. I don't see a good reason not 
to do that.

+ Joonas on this one.

4) Refactoring as done is not very pretty and I proposed an idea for a 
nicer approach. Feasible or not, open for discussion.

At a push I can look past that and someone can attempt to tidy the 
driver later.

But without 1-3 we cannot merge this.

Regards,

Tvrtko

> 
> Fei Yang (5):
>    drm/i915: preparation for using PAT index
>    drm/i915: use pat_index instead of cache_level
>    drm/i915: make sure correct pte encode is used
>    drm/i915/mtl: end support for set caching ioctl
>    drm/i915: Allow user to set cache at BO creation
> 
>   drivers/gpu/drm/i915/display/intel_dpt.c      | 12 +--
>   drivers/gpu/drm/i915/gem/i915_gem_create.c    | 36 +++++++++
>   drivers/gpu/drm/i915/gem/i915_gem_domain.c    | 30 +++----
>   .../gpu/drm/i915/gem/i915_gem_execbuffer.c    | 10 ++-
>   drivers/gpu/drm/i915/gem/i915_gem_mman.c      |  3 +-
>   drivers/gpu/drm/i915/gem/i915_gem_object.c    | 67 +++++++++++++++-
>   drivers/gpu/drm/i915/gem/i915_gem_object.h    |  8 ++
>   .../gpu/drm/i915/gem/i915_gem_object_types.h  | 26 +++++-
>   drivers/gpu/drm/i915/gem/i915_gem_shmem.c     |  9 ++-
>   drivers/gpu/drm/i915/gem/i915_gem_shrinker.c  |  2 -
>   drivers/gpu/drm/i915/gem/i915_gem_stolen.c    |  4 +-
>   drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c  | 16 ++--
>   .../gpu/drm/i915/gem/selftests/huge_pages.c   |  2 +-
>   .../drm/i915/gem/selftests/i915_gem_migrate.c |  2 +-
>   .../drm/i915/gem/selftests/i915_gem_mman.c    |  2 +-
>   drivers/gpu/drm/i915/gt/gen6_ppgtt.c          | 10 ++-
>   drivers/gpu/drm/i915/gt/gen8_ppgtt.c          | 73 +++++++++--------
>   drivers/gpu/drm/i915/gt/gen8_ppgtt.h          |  3 +-
>   drivers/gpu/drm/i915/gt/intel_ggtt.c          | 76 +++++++++---------
>   drivers/gpu/drm/i915/gt/intel_gtt.h           | 20 +++--
>   drivers/gpu/drm/i915/gt/intel_migrate.c       | 47 ++++++-----
>   drivers/gpu/drm/i915/gt/intel_migrate.h       | 13 ++-
>   drivers/gpu/drm/i915/gt/intel_ppgtt.c         |  6 +-
>   drivers/gpu/drm/i915/gt/selftest_migrate.c    | 47 +++++------
>   drivers/gpu/drm/i915/gt/selftest_reset.c      |  8 +-
>   drivers/gpu/drm/i915/gt/selftest_timeline.c   |  2 +-
>   drivers/gpu/drm/i915/gt/selftest_tlb.c        |  4 +-
>   drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c      | 10 ++-
>   drivers/gpu/drm/i915/i915_debugfs.c           | 55 ++++++++++---
>   drivers/gpu/drm/i915/i915_gem.c               | 16 +++-
>   drivers/gpu/drm/i915/i915_gpu_error.c         |  8 +-
>   drivers/gpu/drm/i915/i915_pci.c               | 79 ++++++++++++++++---
>   drivers/gpu/drm/i915/i915_vma.c               | 16 ++--
>   drivers/gpu/drm/i915/i915_vma.h               |  2 +-
>   drivers/gpu/drm/i915/i915_vma_types.h         |  2 -
>   drivers/gpu/drm/i915/intel_device_info.h      |  5 ++
>   drivers/gpu/drm/i915/selftests/i915_gem.c     |  5 +-
>   .../gpu/drm/i915/selftests/i915_gem_evict.c   |  4 +-
>   drivers/gpu/drm/i915/selftests/i915_gem_gtt.c | 15 ++--
>   .../drm/i915/selftests/intel_memory_region.c  |  4 +-
>   .../gpu/drm/i915/selftests/mock_gem_device.c  |  9 +++
>   drivers/gpu/drm/i915/selftests/mock_gtt.c     |  8 +-
>   include/uapi/drm/i915_drm.h                   | 36 +++++++++
>   tools/include/uapi/drm/i915_drm.h             | 36 +++++++++
>   44 files changed, 605 insertions(+), 243 deletions(-)
> 

  parent reply	other threads:[~2023-04-26 10:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  6:24 [Intel-gfx] [PATCH v2 0/5] drm/i915: Allow user to set cache at BO creation fei.yang
2023-04-26  6:24 ` fei.yang
2023-04-26  6:24 ` [Intel-gfx] [PATCH v2 1/5] drm/i915: preparation for using PAT index fei.yang
2023-04-26  6:24   ` fei.yang
2023-04-26  6:24 ` [Intel-gfx] [PATCH v2 2/5] drm/i915: use pat_index instead of cache_level fei.yang
2023-04-26  6:24   ` fei.yang
2023-04-26  6:24 ` [Intel-gfx] [PATCH v2 3/5] drm/i915: make sure correct pte encode is used fei.yang
2023-04-26  6:24   ` fei.yang
2023-04-26  6:24 ` [Intel-gfx] [PATCH v2 4/5] drm/i915/mtl: end support for set caching ioctl fei.yang
2023-04-26  6:24   ` fei.yang
2023-04-26  6:24 ` [Intel-gfx] [PATCH v2 5/5] drm/i915: Allow user to set cache at BO creation fei.yang
2023-04-26  6:24   ` fei.yang
2023-04-26  7:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Allow user to set cache at BO creation (rev2) Patchwork
2023-04-26  7:53 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-04-26 10:38 ` Tvrtko Ursulin [this message]
2023-04-26 15:41   ` [Intel-gfx] [PATCH v2 0/5] drm/i915: Allow user to set cache at BO creation Yang, Fei
2023-04-27 14:33     ` Tvrtko Ursulin
2023-04-27 16:07       ` Yang, Fei
2023-04-28  9:43         ` Tvrtko Ursulin
2023-04-28 19:51           ` Yang, Fei

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=c7cb1466-e698-ff3f-0572-4693c4b0025c@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fei.yang@intel.com \
    --cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.