Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v8 00/15] PAT and cache coherency support
Date: Tue,  7 Nov 2023 11:48:01 +0000	[thread overview]
Message-ID: <20231107114816.190793-1-matthew.auld@intel.com> (raw)

Series implements the IGT side of things needed to support the new Xe uapi
here:
https://patchwork.freedesktop.org/series/123027/

Branch with the IGT changes:
https://gitlab.freedesktop.org/mwa/igt-gpu-tools/-/commits/xe-pat-index

Branch with the KMD changes:
https://gitlab.freedesktop.org/mwa/kernel/-/tree/xe-pat-index?ref_type=heads

v2:
  - Various tweaks and improvements.
  - Rebase on Xe2 additions.
  - Handle compressed wt on Xe2 + some other xe2 specific pat_index modes.
v3:
  - Various fixes and improvements.
v4:
  - Various improvements. Rebase
v5:
  - Some more improvements, including testing some xelpg modes.
v6:
  - Some more minor improvements.
v7:
  - Account for dropping coh_mode.
  - Add store-dword mode for the xe_pat tests to ensure we run on every engine
    (randomised over runs).
v8:
  - Couple minor fixes, like unbreaking api_intel_allocator@default-alignment

-- 
2.41.0

             reply	other threads:[~2023-11-07 11:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 11:48 Matthew Auld [this message]
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 01/15] drm-uapi/xe_drm: sync to get pat and coherency bits Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 02/15] lib/igt_fb: mark buffers as SCANOUT Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 03/15] lib/igt_draw: " Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 04/15] lib/xe: support explicit cpu_caching gem_create Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 05/15] tests/xe/mmap: add some tests for explicit cpu_caching Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 06/15] lib/intel_pat: add helpers for common pat_index modes Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 07/15] lib/allocator: add get_offset_pat_index() helper Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 08/15] lib/intel_blt: support pat_index Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 09/15] lib/intel_buf: " Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 10/15] lib/xe_ioctl: update vm_bind to account for pat_index Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 11/15] lib/intel_allocator: treat default_alignment as the minimum Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 12/15] lib/intel_blt: tidy up alignment usage Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 13/15] lib/intel_batchbuffer: extend to include optional alignment Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 14/15] tests/xe: add some vm_bind pat_index tests Matthew Auld
2023-11-07 11:48 ` [igt-dev] [PATCH i-g-t v8 15/15] tests/intel-ci/xe: add pat and caching related tests Matthew Auld
2023-11-07 12:55 ` [igt-dev] ✓ Fi.CI.BAT: success for PAT and cache coherency support (rev8) Patchwork
2023-11-07 13:26 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-11-08  2:19 ` [igt-dev] ✓ Fi.CI.IGT: success " 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=20231107114816.190793-1-matthew.auld@intel.com \
    --to=matthew.auld@intel.com \
    --cc=igt-dev@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