Use drm_clflush* instead of clflush
Subsystems (3)
v7 cover Use drm_clflush* instead of clflush
This patch series re-work a few i915 functions to use drm_clflush_virt_range instead of calling clflush or clflushopt directly. This will prevent errors when building for non-x86 architectures.
v2: s/PAGE_SIZE/sizeof(value) for Re-work intel_write_status_page and added more patches to convert additional clflush/clflushopt to use drm_clflush*. (Michael Cheng)
v3: Drop invalidate_csb_entries and directly invoke drm_clflush_virt_ran
v4: Remove extra memory barriers
v5: s/cache_clflush_range/drm_clflush_virt_range
v6: Fix up "Drop invalidate_csb_entries" to use correct parameters. Also added in arm64 support for drm_clflush_virt_range.
v7: Re-order patches, and use correct macro for dcache flush for arm64.
Michael Cheng (6):
drm: Add arch arm64 for drm_clflush_virt_range
drm/i915/gt: Re-work intel_write_status_page
drm/i915/gt: Drop invalidate_csb_entries
drm/i915/gt: Re-work reset_csb
drm/i915/: Re-work clflush_write32
drm/i915/gt: replace cache_clflush_range
drivers/gpu/drm/drm_cache.c | 8 ++++++++ .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 8 +++----- drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 12 ++++++------ drivers/gpu/drm/i915/gt/intel_engine.h | 13 ++++--------- .../drm/i915/gt/intel_execlists_submission.c | 19 ++++++------------- drivers/gpu/drm/i915/gt/intel_gtt.c | 2 +- drivers/gpu/drm/i915/gt/intel_ppgtt.c | 2 +- .../gpu/drm/i915/gt/uc/intel_guc_submission.c | 2 +- 8 files changed, 30 insertions(+), 36 deletions(-)
Signature · 1 line
2.25.1
PATCH v7 1/6 drm: Add arch arm64 for drm_clflush_virt_range
Add arm64 support for drm_clflush_virt_range. dcache_clean_inval_poc performs a flush by first performing a clean, follow by an invalidation operation.
v2 (Michael Cheng): Use correct macro for cleaning and invalidation the
dcache.
--- drivers/gpu/drm/drm_cache.c | 8 ++++++++ 1 file changed, 8 insertions(+)
drivers/gpu/drm/drm_cache.c +8 -0
@@ -39,6 +39,10 @@/* A small bounce buffer that fits on the stack. */ #define MEMCPY_BOUNCE_SIZE 128 +#if defined(CONFIG_ARM64 ) +#include <asm/cacheflush.h> +#endif +#if defined(CONFIG_X86 )#include <asm/smp.h>
@@ -176,6 +180,10 @@ drm_clflush_virt_range(void *addr, unsigned long length)if (wbinvd_on_all_cpus ())pr_err ("Timed out waiting for cache flush\n" ); + +#elif defined(CONFIG_ARM64 ) +void *end = addr + length; +dcache_clean_inval_poc ((unsigned long )addr, (unsigned long )end);#else pr_err ("Architecture has no drm_cache.c support\n" );WARN_ON_ONCE (1 );
Signature · 1 line
2.25.1
Re: [PATCH v7 1/6] drm: Add arch arm64 for drm_clflush_virt_range
Quoted 17 lines · Michael Cheng
Add arm64 support for
drm_clflush_virt_range.dcache_clean_inval_pocperforms a flush by first performing a clean, follow by an invalidation operation.v2 (Michael Cheng): Use correct macro for cleaning and invalidation the
dcache.Signed-off-by Michael Cheng <[email protected]>--- drivers/gpu/drm/drm_cache.c | 8 ++++++++ 1 file changed, 8 insertions(+)drivers/gpu/drm/drm_cache.c +0
-0
drivers/gpu/drm/drm_cache.c line 45
Quoted 7 lines
drivers/gpu/drm/drm_cache.c +4
-0@@ -39,6 +39,10 @@/* A small bounce buffer that fits on the stack. */ #define MEMCPY_BOUNCE_SIZE 128 +#if defined(CONFIG_ARM64 ) +#include <asm/cacheflush.h> +#endif +
I think this likely should be a single, arch unconditional:
#include <linux/cacheflush.h>
Probably it just happens that some other include pulls in clflushopt for x86.
Regards,
Tvrtko
Quoted 14 lines
drivers/gpu/drm/drm_cache.c +4
-0#if defined(CONFIG_X86 )#include <asm/smp.h> @@ -176,6 +180,10 @@ drm_clflush_virt_range(void *addr, unsigned long length)if (wbinvd_on_all_cpus ())pr_err ("Timed out waiting for cache flush\n" ); + +#elif defined(CONFIG_ARM64 ) +void *end = addr + length; +dcache_clean_inval_poc ((unsigned long )addr, (unsigned long )end);#else pr_err ("Architecture has no drm_cache.c support\n" );WARN_ON_ONCE (1 );
PATCH v7 2/6 drm/i915/gt: Re-work intel_write_status_page
In reply to Michael ChengRe-work intel_write_status_page to use drm_clflush_virt_range. This will prevent compiler errors when building for non-x86 architectures.
--- drivers/gpu/drm/i915/gt/intel_engine.h | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-)
drivers/gpu/drm/i915/gt/intel_engine.h +4 -9
@@ -4,6 +4,7 @@#include <asm/cacheflush.h> #include <drm/drm_util.h> +#include <drm/drm_cache.h> #include <linux/hashtable.h> #include <linux/irq_work.h>
@@ -143,15 +144,9 @@ intel_write_status_page(struct intel_engine_cs *engine, int reg, u32 value)* of extra paranoia to try and ensure that the HWS takes the value * we give and that it doesn't end up trapped inside the CPU! */ -if (static_cpu_has (X86_FEATURE_CLFLUSH )) { -mb (); -clflush (&engine->status_page.addr[reg]); - engine->status_page.addr[reg] = value; -clflush (&engine->status_page.addr[reg]); -mb (); - }else { -WRITE_ONCE (engine->status_page.addr[reg], value); - } +drm_clflush_virt_range (&engine->status_page.addr[reg],sizeof (value)); +WRITE_ONCE (engine->status_page.addr[reg], value); +drm_clflush_virt_range (&engine->status_page.addr[reg],sizeof (value)); }/*
Signature · 1 line
2.25.1
PATCH v7 3/6 drm/i915/gt: Drop invalidate_csb_entries
In reply to Michael ChengDrop invalidate_csb_entries and directly call drm_clflush_virt_range. This allows for one less function call, and prevent complier errors when building for non-x86 architectures.
v2(Michael Cheng): Drop invalidate_csb_entries function and directly
invoke drm_clflush_virt_range. Thanks to Tvrtko for the sugguestion.
v3(Michael Cheng): Use correct parameters for drm_clflush_virt_range.
Thanks to Tvrtko for pointing this out.
--- drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-)
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +3 -9
@@ -1646,12 +1646,6 @@ cancel_port_requests(struct intel_engine_execlists * const execlists,return inactive; } -static void invalidate_csb_entries (const u64 *first,const u64 *last) -{ -clflush ((void *)first); -clflush ((void *)last); -} -/* * Starting with Gen12, the status has a new format: *
@@ -1999,7 +1993,7 @@ process_csb(struct intel_engine_cs *engine, struct i915_request **inactive)* the wash as hardware, working or not, will need to do the * invalidation before. */ -invalidate_csb_entries (&buf[0 ], &buf[num_entries -1 ]); +drm_clflush_virt_range (&buf[0 ], num_entries *sizeof (buf[0 ]));/* * We assume that any event reflects a change in context flow
@@ -2783,8 +2777,8 @@ static void reset_csb_pointers(struct intel_engine_cs *engine)/* Check that the GPU does indeed update the CSB entries! */ memset (execlists->csb_status,-1 , (reset_value +1 ) *sizeof (u64)); -invalidate_csb_entries (&execlists->csb_status[0 ], - &execlists->csb_status[reset_value]); +drm_clflush_virt_range (&execlists->csb_status[0 ], + execlists->csb_size *sizeof (execlists->csb_status[0 ]));/* Once more for luck and our trusty paranoia */ ENGINE_WRITE(engine, RING_CONTEXT_STATUS_PTR,
Signature · 1 line
2.25.1
PATCH v7 4/6 drm/i915/gt: Re-work reset_csb
In reply to Michael ChengUse drm_clflush_virt_range instead of directly invoking clflush. This will prevent compiler errors when building for non-x86 architectures.
v2(Michael Cheng): Remove extra clflush
v3(Michael Cheng): Remove memory barrier since drm_clflush_virt_range
takes care of it.
--- drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +2 -3
@@ -2944,9 +2944,8 @@ reset_csb(struct intel_engine_cs *engine, struct i915_request **inactive) {struct intel_engine_execlists *const execlists = &engine->execlists; -mb ();/* paranoia: read the CSB pointers from after the reset */ -clflush (execlists->csb_write); -mb (); +drm_clflush_virt_range (execlists->csb_write, +sizeof (execlists->csb_write)); inactive =process_csb (engine, inactive);/* drain preemption events */
Signature · 1 line
2.25.1
PATCH v7 5/6 drm/i915/: Re-work clflush_write32
In reply to Michael ChengUse drm_clflush_virt_range instead of clflushopt and remove the memory barrier, since drm_clflush_virt_range takes care of that.
--- drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c +3 -5
@@ -1332,10 +1332,8 @@ static void *reloc_vaddr(struct i915_vma *vma,static void clflush_write32 (u32 *addr,u32 value,unsigned int flushes) {if (unlikely (flushes & (CLFLUSH_BEFORE |CLFLUSH_AFTER ))) { -if (flushes &CLFLUSH_BEFORE ) { -clflushopt (addr); -mb (); - } +if (flushes &CLFLUSH_BEFORE ) +drm_clflush_virt_range (addr,sizeof (addr)); *addr = value;
@@ -1347,7 +1345,7 @@ static void clflush_write32(u32 *addr, u32 value, unsigned int flushes)* to ensure ordering of clflush wrt to the system. */ if (flushes &CLFLUSH_AFTER ) -clflushopt (addr); +drm_clflush_virt_range (addr,sizeof (addr)); }else *addr = value; }
Signature · 1 line
2.25.1
PATCH v7 6/6 drm/i915/gt: replace cache_clflush_range
In reply to Michael ChengReplace all occurance of cache_clflush_range with drm_clflush_virt_range. This will prevent compile errors on non-x86 platforms.
--- drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 12 ++++++------ drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 2 +- drivers/gpu/drm/i915/gt/intel_gtt.c | 2 +- drivers/gpu/drm/i915/gt/intel_ppgtt.c | 2 +- drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/gt/gen8_ppgtt.c +6 -6
@@ -444,11 +444,11 @@ gen8_ppgtt_insert_pte(struct i915_ppgtt *ppgtt, pd = pdp->entry[gen8_pd_index (idx,2 )]; } -clflush_cache_range (vaddr,PAGE_SIZE ); +drm_clflush_virt_range (vaddr,PAGE_SIZE ); vaddr =px_vaddr (i915_pt_entry (pd,gen8_pd_index (idx,1 ))); } }while (1 ); -clflush_cache_range (vaddr,PAGE_SIZE ); +drm_clflush_virt_range (vaddr,PAGE_SIZE );return idx; }
@@ -532,7 +532,7 @@ static void gen8_ppgtt_insert_huge(struct i915_address_space *vm, } }while (rem >= page_size && index <I915_PDES ); -clflush_cache_range (vaddr,PAGE_SIZE ); +drm_clflush_virt_range (vaddr,PAGE_SIZE );/* * Is it safe to mark the 2M block as 64K? -- Either we have
@@ -548,7 +548,7 @@ static void gen8_ppgtt_insert_huge(struct i915_address_space *vm, I915_GTT_PAGE_SIZE_2M)))) { vaddr =px_vaddr (pd); vaddr[maybe_64K] |=GEN8_PDE_IPS_64K ; -clflush_cache_range (vaddr,PAGE_SIZE ); +drm_clflush_virt_range (vaddr,PAGE_SIZE ); page_size =I915_GTT_PAGE_SIZE_64K ;/*
@@ -569,7 +569,7 @@ static void gen8_ppgtt_insert_huge(struct i915_address_space *vm,for (i =1 ; i < index; i +=16 )memset64 (vaddr + i, encode,15 ); -clflush_cache_range (vaddr,PAGE_SIZE ); +drm_clflush_virt_range (vaddr,PAGE_SIZE ); } }
@@ -617,7 +617,7 @@ static void gen8_ppgtt_insert_entry(struct i915_address_space *vm, vaddr =px_vaddr (i915_pt_entry (pd,gen8_pd_index (idx,1 ))); vaddr[gen8_pd_index (idx,0 )] =gen8_pte_encode (addr, level, flags); -clflush_cache_range (&vaddr[gen8_pd_index (idx,0 )],sizeof (*vaddr)); +drm_clflush_virt_range (&vaddr[gen8_pd_index (idx,0 )],sizeof (*vaddr)); }static int gen8_init_scratch (struct i915_address_space *vm)
drivers/gpu/drm/i915/gt/intel_execlists_submission.c +1 -1
@@ -2822,7 +2822,7 @@ static void execlists_sanitize(struct intel_engine_cs *engine)sanitize_hwsp (engine);/* And scrub the dirty cachelines for the HWSP */ -clflush_cache_range (engine->status_page.addr,PAGE_SIZE ); +drm_clflush_virt_range (engine->status_page.addr,PAGE_SIZE );intel_engine_reset_pinned_contexts (engine); }
drivers/gpu/drm/i915/gt/intel_gtt.c +1 -1
@@ -255,7 +255,7 @@ fill_page_dma(struct drm_i915_gem_object *p, const u64 val, unsigned int count)void *vaddr =__px_vaddr (p);memset64 (vaddr, val, count); -clflush_cache_range (vaddr,PAGE_SIZE ); +drm_clflush_virt_range (vaddr,PAGE_SIZE ); }static void poison_scratch_page (struct drm_i915_gem_object *scratch)
drivers/gpu/drm/i915/gt/intel_ppgtt.c +1 -1
@@ -90,7 +90,7 @@ write_dma_entry(struct drm_i915_gem_object * const pdma,u64 *const vaddr =__px_vaddr (pdma); vaddr[idx] = encoded_entry; -clflush_cache_range (&vaddr[idx],sizeof (u64)); +drm_clflush_virt_range (&vaddr[idx],sizeof (u64)); }void
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c +1 -1
@@ -3573,7 +3573,7 @@ static void guc_sanitize(struct intel_engine_cs *engine)sanitize_hwsp (engine);/* And scrub the dirty cachelines for the HWSP */ -clflush_cache_range (engine->status_page.addr,PAGE_SIZE ); +drm_clflush_virt_range (engine->status_page.addr,PAGE_SIZE );intel_engine_reset_pinned_contexts (engine); }
Signature · 1 line
2.25.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev6)
In reply to Michael Cheng== Series Details ==
== Series Details ==
Series: Use drm_clflush* instead of clflush (rev6)
URL : https://patchwork.freedesktop.org/series/99450/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 46bf608d395e drm: Add arch arm64 for drm_clflush_virt_range -:24: WARNING:INCLUDE_LINUX: Use #include <linux/cacheflush.h> instead of <asm/cacheflush.h> #24: FILE: drivers/gpu/drm/drm_cache.c:43: +#include <asm/cacheflush.h>
-:37: WARNING:LINE_SPACING: Missing a blank line after declarations #37: FILE: drivers/gpu/drm/drm_cache.c:184:
+ void *end = addr + length;
+ dcache_clean_inval_poc((unsigned long)addr, (unsigned long)end);
total: 0 errors, 2 warnings, 0 checks, 20 lines checked af1ddd5cfab1 drm/i915/gt: Re-work intel_write_status_page 2cd8842cdb4f drm/i915/gt: Drop invalidate_csb_entries
-:52: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #52: FILE: drivers/gpu/drm/i915/gt/intel_execlists_submission.c:2781:
+ drm_clflush_virt_range(&execlists->csb_status[0],
+ execlists->csb_size * sizeof(execlists->csb_status[0]));
total: 0 errors, 0 warnings, 1 checks, 30 lines checked 5027b028fdc4 drm/i915/gt: Re-work reset_csb
-:28: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis #28: FILE: drivers/gpu/drm/i915/gt/intel_execlists_submission.c:2948:
+ drm_clflush_virt_range(execlists->csb_write,
+ sizeof(execlists->csb_write));
total: 0 errors, 0 warnings, 1 checks, 11 lines checked315ba5405322 drm/i915/: Re-work clflush_write321808b1f8eb7a drm/i915/gt: replace cache_clflush_range
-:6: WARNING:TYPO_SPELLING: 'occurance' may be misspelled - perhaps 'occurrence'? #6:
Replace all occurance of cache_clflush_range with
^^^^^^^^^
total: 0 errors, 1 warnings, 0 checks, 77 lines checked
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use drm_clflush* instead of clflush (rev6)
In reply to Michael Cheng== Series Details ==
== Series Details ==
Series: Use drm_clflush* instead of clflush (rev6)
URL : https://patchwork.freedesktop.org/series/99450/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for Use drm_clflush* instead of clflush (rev6)
In reply to Michael Cheng== Series Details ==
== Series Details ==
Series: Use drm_clflush* instead of clflush (rev6)
URL : https://patchwork.freedesktop.org/series/99450/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11205 -> Patchwork_22218
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_22218 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_22218, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/index.html
Participating hosts (46 -> 42)
------------------------------
Missing (4): fi-kbl-soraka fi-bsw-cyan shard-tglu fi-pnv-d510
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22218:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@hangcheck:
- fi-rkl-guc: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/fi-rkl-guc/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/fi-rkl-guc/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_22218 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@debugfs_test@read_all_entries:
- fi-cfl-8109u: [PASS][3] -> [DMESG-WARN][4] ([i915#262] / [i915#295])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/fi-cfl-8109u/igt@debugfs_test@read_all_entries.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/fi-cfl-8109u/igt@debugfs_test@read_all_entries.html
* igt@gem_exec_suspend@basic-s3@smem:
- fi-skl-6600u: [PASS][5] -> [INCOMPLETE][6] ([i915#4547])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/fi-skl-6600u/igt@gem_exec_suspend@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/fi-skl-6600u/igt@gem_exec_suspend@[email protected]
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [PASS][7] -> [DMESG-WARN][8] ([i915#4269])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/fi-cml-u2/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/fi-cml-u2/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-b:
- fi-cfl-8109u: [PASS][9] -> [DMESG-WARN][10] ([i915#295]) +14 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/fi-cfl-8109u/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/fi-cfl-8109u/igt@[email protected]
#### Warnings ####
* igt@debugfs_test@read_all_entries:
- fi-apl-guc: [DMESG-WARN][11] -> [DMESG-WARN][12] ([i915#1610])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/fi-apl-guc/igt@debugfs_test@read_all_entries.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/fi-apl-guc/igt@debugfs_test@read_all_entries.html
* igt@i915_selftest@live@hangcheck:
- bat-dg1-5: [DMESG-FAIL][13] ([i915#4957]) -> [DMESG-FAIL][14] ([i915#4494] / [i915#4957])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11205/bat-dg1-5/igt@i915_selftest@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/bat-dg1-5/igt@i915_selftest@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[i915#1610]: https://gitlab.freedesktop.org/drm/intel/issues/1610
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#295]: https://gitlab.freedesktop.org/drm/intel/issues/295
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4547]: https://gitlab.freedesktop.org/drm/intel/issues/4547
[i915#4897]: https://gitlab.freedesktop.org/drm/intel/issues/4897
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
Build changes
-------------
* Linux: CI_DRM_11205 -> Patchwork_22218
CI-20190529: 20190529
CI_DRM_11205: 9999c764a7571bebed03bec481d6fffcb23144fe @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6341: a96674e747ea2f2431bbf8813156adc44ec3162a @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22218: 1808b1f8eb7aedff2794e6f003f3bf2809cb012c @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
1808b1f8eb7a drm/i915/gt: replace cache_clflush_range 315ba5405322 drm/i915/: Re-work clflush_write32 5027b028fdc4 drm/i915/gt: Re-work reset_csb 2cd8842cdb4f drm/i915/gt: Drop invalidate_csb_entries af1ddd5cfab1 drm/i915/gt: Re-work intel_write_status_page 46bf608d395e drm: Add arch arm64 for drm_clflush_virt_range
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22218/index.html