[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Clarify vma lifetime

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Clarify vma lifetime URL : https://patchwork.freedesktop.org/series/99948/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_22235 Summary --- **SUCCESS** No

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Clarify vma lifetime

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Clarify vma lifetime URL : https://patchwork.freedesktop.org/series/99948/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] [PATCH] drm/i915: Clarify vma lifetime

2022-02-09 Thread Thomas Hellström
It's unclear what reference the initial vma kref refernce refers to. A vma can have multiple weak references, the object vma list, the vm's bound list and the GT's closed_list, and the initial vma reference can be put from lookups of all these lists. With the current implementation this means

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg1: Update DMC_DEBUG3 register

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/dg1: Update DMC_DEBUG3 register URL : https://patchwork.freedesktop.org/series/99942/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_22233_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Futher optimize plane updates (rev3)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Futher optimize plane updates (rev3) URL : https://patchwork.freedesktop.org/series/99149/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_22234 Summary ---

[Intel-gfx] [PATCH v2 5/5] drm/i915: Make pre-skl sprite plane registers unlocked

2022-02-09 Thread Ville Syrjala
From: Ville Syrjälä Drop the locks around sprite plane register writes. The lock isn't needed since each plane's register are neatly contained on their own cachelines. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_sprite.c | 45 - 1 file changed, 45

[Intel-gfx] [PATCH v2 4/5] drm/i915: Make most pre-skl primary plane registers unlocked

2022-02-09 Thread Ville Syrjala
From: Ville Syrjälä Drop the locks around most primary plane register writes. The lock isn't needed since each plane's register are neatly contained on their own cachelines. The one exception we have to make is DSPADDR/DSPSURF which is (ab)used to also trigger FBC nukes on pre-snb (since the

[Intel-gfx] [PATCH v2 3/5] drm/i915: Make cursor plane registers unlocked

2022-02-09 Thread Ville Syrjala
From: Ville Syrjälä Drop the locks around cursor plane register writes. The lock isn't needed since each plane's register are neatly contained on their own cachelines. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_cursor.c | 10 -- 1 file changed, 10 deletions(-)

[Intel-gfx] [PATCH v2 1/5] drm/i915: Optimize icl+ universal plane programming

2022-02-09 Thread Ville Syrjala
From: Ville Syrjälä On icl+ all plane registers are armed by PLANE_SURF, so we can move almost everything over into the update_noarm() hook. The PLANE_CTL write has to stay in the icl_update_arm() hook though as it still exhibits the somewhat annoying self-arming behaviour when the plane

[Intel-gfx] [PATCH v2 2/5] drm/i915: Make skl+ universal plane registers unlocked

2022-02-09 Thread Ville Syrjala
From: Ville Syrjälä Drop the locks around most universal plane register writes. The lock isn't needed since each plane's register are neatly contained on their own cachelines. Signed-off-by: Ville Syrjälä --- .../drm/i915/display/skl_universal_plane.c| 35 --- 1 file

[Intel-gfx] [PATCH v2 0/5] drm/i915: Futher optimize plane updates

2022-02-09 Thread Ville Syrjala
From: Ville Syrjälä Optimize icl+ plane updates by moving most register writes into the .update_noarm() hook. Also stop taking uncore.lock for plane register writes as well. Just a rebase. Ville Syrjälä (5): drm/i915: Optimize icl+ universal plane programming drm/i915: Make skl+ universal

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dg1: Update DMC_DEBUG3 register

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/dg1: Update DMC_DEBUG3 register URL : https://patchwork.freedesktop.org/series/99942/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_22233 Summary ---

Re: [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register

2022-02-09 Thread Liu, Chuansheng
> -Original Message- > From: Roper, Matthew D > Sent: Thursday, February 10, 2022 1:28 PM > To: Liu, Chuansheng > Cc: intel-gfx@lists.freedesktop.org; Gupta, Anshuman > ; De Marchi, Lucas > > Subject: Re: [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register > > On Thu, Feb 10, 2022 at

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/dg1: Update DMC_DEBUG3 register

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/dg1: Update DMC_DEBUG3 register URL : https://patchwork.freedesktop.org/series/99942/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register

2022-02-09 Thread Matt Roper
On Thu, Feb 10, 2022 at 01:05:01PM +0800, Chuansheng Liu wrote: > Current DMC_DEBUG3(_MMIO(0x101090)) address is for TGL, > it is not wrong for DG1. Just like commit 5bcc95ca382e > ("drm/i915/dg1: Update DMC_DEBUG register"), correct > this issue for DG1 platform to avoid wrong register > being

[Intel-gfx] [PATCH] drm/i915/dg1: Update DMC_DEBUG3 register

2022-02-09 Thread Chuansheng Liu
Current DMC_DEBUG3(_MMIO(0x101090)) address is for TGL, it is not wrong for DG1. Just like commit 5bcc95ca382e ("drm/i915/dg1: Update DMC_DEBUG register"), correct this issue for DG1 platform to avoid wrong register being read. BSpec: 49788 Signed-off-by: Chuansheng Liu ---

Re: [Intel-gfx] [PATCH v5 03/10] drm/i915/guc: Add DG2 registers for GuC error state capture.

2022-02-09 Thread Teres Alexis, Alan Previn
Apologies for the delayed response. I totally agree with the lpd vs hpg function separation. Thats what i initially implemented but when cross-referencing my logic with the execlist i realized DG2 steering registers for all Gens were in the same function so I thought of keeping it consistent but i

Re: [Intel-gfx] [PATCH 5/6] drm/rcar_du: changes to rcar-du driver resulting from drm_writeback_connector structure changes

2022-02-09 Thread Laurent Pinchart
Hi Abhinav, On Wed, Feb 09, 2022 at 05:40:29PM -0800, Abhinav Kumar wrote: > Hi Laurent > > Gentle reminder on this. I won't have time before next week I'm afraid. > On 2/6/2022 11:20 PM, Abhinav Kumar wrote: > > Hi Laurent > > > > On 2/6/2022 3:32 PM, Dmitry Baryshkov wrote: > >> On Wed, 2

[Intel-gfx] ✗ Fi.CI.IGT: failure for Bump DMC Version on ADL-P to v2.16 (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: Bump DMC Version on ADL-P to v2.16 (rev2) URL : https://patchwork.freedesktop.org/series/99938/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_22232_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for Bump DMC Version on ADL-P to v2.16 (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: Bump DMC Version on ADL-P to v2.16 (rev2) URL : https://patchwork.freedesktop.org/series/99938/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_22232 Summary ---

[Intel-gfx] [PATCH 1/1] drm/i915/dmc: Update DMC to v2.16 on ADL-P

2022-02-09 Thread Madhumitha Tolakanahalli Pradeep
Changes since v2.14: - Release Notes for v2.15 Fix for corruption issue when DC States are enabled. - Release Notes for v2.16 Fix for cases with flip queue and DC6v are enabled. Signed-off-by: Madhumitha Tolakanahalli Pradeep ---

[Intel-gfx] [PATCH 0/1] Bump DMC Version on ADL-P to v2.16

2022-02-09 Thread Madhumitha Tolakanahalli Pradeep
The following changes since commit eb8ea1b46893c42edbd516f971a93b4d097730ab: Merge branch 'v1.1.7' of https://github.com/irui- wang/linux_fw_vpu_v1.1.7 into main (2022-01-24 06:49:52 -0500) are available in the Git repository at: git://anongit.freedesktop.org/drm/drm-firmware adlp_dmc_v2.16

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dg2: Invalidate LSC L1 cache

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/dg2: Invalidate LSC L1 cache URL : https://patchwork.freedesktop.org/series/99926/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_9_full Summary ---

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Waiman Long
On 2/9/22 19:27, Namhyung Kim wrote: On Wed, Feb 9, 2022 at 12:17 PM Waiman Long wrote: On 2/9/22 14:45, Namhyung Kim wrote: On Wed, Feb 9, 2022 at 11:28 AM Mathieu Desnoyers wrote: - On Feb 9, 2022, at 2:22 PM, Namhyung Kim namhy...@kernel.org wrote: I'm also concerning dynamic

[Intel-gfx] ✗ Fi.CI.BAT: failure for Use drm_clflush* instead of clflush (rev8)

2022-02-09 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev8) URL : https://patchwork.freedesktop.org/series/99450/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_22231 Summary ---

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gem: Don't try to map and fence large scanout buffers (v6)

2022-02-09 Thread Kasireddy, Vivek
Hi Ville, > On Wed, Feb 09, 2022 at 01:47:01AM +, Kasireddy, Vivek wrote: > > Hi Ville, > > > > > > > > On Tue, Feb 08, 2022 at 05:10:42AM +, Kasireddy, Vivek wrote: > > > > Hi Tvrtko, Ville, > > > > > > > > > On 07/02/2022 13:24, Ville Syrjälä wrote: > > > > > > On Mon, Feb 07, 2022 at

Re: [Intel-gfx] [PATCH 5/6] drm/rcar_du: changes to rcar-du driver resulting from drm_writeback_connector structure changes

2022-02-09 Thread Abhinav Kumar
Hi Laurent Gentle reminder on this. Thanks Abhinav On 2/6/2022 11:20 PM, Abhinav Kumar wrote: Hi Laurent On 2/6/2022 3:32 PM, Dmitry Baryshkov wrote: On Wed, 2 Feb 2022 at 16:26, Laurent Pinchart wrote: Hi Jani, On Wed, Feb 02, 2022 at 03:15:03PM +0200, Jani Nikula wrote: On Wed, 02

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Use drm_clflush* instead of clflush (rev8)

2022-02-09 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev8) 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.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Use drm_clflush* instead of clflush (rev8)

2022-02-09 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev8) URL : https://patchwork.freedesktop.org/series/99450/ State : warning == Summary == $ dim checkpatch origin/drm-tip 3bb116c416b9 drm: Add arch arm64 for drm_clflush_virt_range -:27: WARNING:INCLUDE_LINUX: Use #include

[Intel-gfx] [PATCH v9 5/6] drm/i915/: Re-work clflush_write32

2022-02-09 Thread Michael Cheng
Use drm_clflush_virt_range instead of clflushopt and remove the memory barrier, since drm_clflush_virt_range takes care of that. Signed-off-by: Michael Cheng --- drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

[Intel-gfx] [PATCH v9 3/6] drm/i915/gt: Drop invalidate_csb_entries

2022-02-09 Thread Michael Cheng
Drop 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.

[Intel-gfx] [PATCH v9 6/6] drm/i915/gt: replace cache_clflush_range

2022-02-09 Thread Michael Cheng
Replace all occurance of cache_clflush_range with drm_clflush_virt_range. This will prevent compile errors on non-x86 platforms. Signed-off-by: Michael Cheng --- drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 12 ++-- drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 2 +-

[Intel-gfx] [PATCH v9 1/6] drm: Add arch arm64 for drm_clflush_virt_range

2022-02-09 Thread Michael Cheng
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. v3 (Michael Cheng): Remove ifdef for

[Intel-gfx] [PATCH v9 4/6] drm/i915/gt: Re-work reset_csb

2022-02-09 Thread Michael Cheng
Use 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.

[Intel-gfx] [PATCH v9 0/6] Use drm_clflush* instead of clflush

2022-02-09 Thread Michael Cheng
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.

[Intel-gfx] [PATCH v9 2/6] drm/i915/gt: Re-work intel_write_status_page

2022-02-09 Thread Michael Cheng
Re-work intel_write_status_page to use drm_clflush_virt_range. This will prevent compiler errors when building for non-x86 architectures. Signed-off-by: Michael Cheng --- drivers/gpu/drm/i915/gt/intel_engine.h | 13 - 1 file changed, 4 insertions(+), 9 deletions(-) diff --git

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dg2: Invalidate LSC L1 cache

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/dg2: Invalidate LSC L1 cache URL : https://patchwork.freedesktop.org/series/99926/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_9 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.BUILD: failure for Use drm_clflush* instead of clflush (rev7)

2022-02-09 Thread Patchwork
== Series Details == Series: Use drm_clflush* instead of clflush (rev7) URL : https://patchwork.freedesktop.org/series/99450/ State : failure == Summary == Applying: drm: Add arch arm64 for drm_clflush_virt_range Using index info to reconstruct a base tree... M

[Intel-gfx] [PATCH v8 5/6] drm/i915/: Re-work clflush_write32

2022-02-09 Thread Michael Cheng
Use drm_clflush_virt_range instead of clflushopt and remove the memory barrier, since drm_clflush_virt_range takes care of that. Signed-off-by: Michael Cheng --- drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git

[Intel-gfx] [PATCH v8 4/6] drm/i915/gt: Re-work reset_csb

2022-02-09 Thread Michael Cheng
Use 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.

[Intel-gfx] [PATCH v8 6/6] drm/i915/gt: replace cache_clflush_range

2022-02-09 Thread Michael Cheng
Replace all occurance of cache_clflush_range with drm_clflush_virt_range. This will prevent compile errors on non-x86 platforms. Signed-off-by: Michael Cheng --- drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 12 ++-- drivers/gpu/drm/i915/gt/intel_execlists_submission.c | 2 +-

[Intel-gfx] [PATCH v8 2/6] drm/i915/gt: Re-work intel_write_status_page

2022-02-09 Thread Michael Cheng
Re-work intel_write_status_page to use drm_clflush_virt_range. This will prevent compiler errors when building for non-x86 architectures. Signed-off-by: Michael Cheng --- drivers/gpu/drm/i915/gt/intel_engine.h | 13 - 1 file changed, 4 insertions(+), 9 deletions(-) diff --git

[Intel-gfx] [PATCH v8 3/6] drm/i915/gt: Drop invalidate_csb_entries

2022-02-09 Thread Michael Cheng
Drop 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.

[Intel-gfx] [PATCH v8 1/6] drm: Add arch arm64 for drm_clflush_virt_range

2022-02-09 Thread Michael Cheng
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. v3 (Michael Cheng): Remove ifdef for

[Intel-gfx] [PATCH v8 0/6] Use drm_clflush* instead of clflush

2022-02-09 Thread Michael Cheng
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.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dg2: Invalidate LSC L1 cache

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/dg2: Invalidate LSC L1 cache URL : https://patchwork.freedesktop.org/series/99926/ State : warning == Summary == $ dim checkpatch origin/drm-tip add021eabf06 drm/i915/dg2: Invalidate LSC L1 cache -:20: WARNING:LONG_LINE: line length of 131 exceeds 100

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Namhyung Kim
On Wed, Feb 9, 2022 at 1:09 AM Peter Zijlstra wrote: > > On Tue, Feb 08, 2022 at 10:41:56AM -0800, Namhyung Kim wrote: > > > Eventually I'm mostly interested in the contended locks only and I > > want to reduce the overhead in the fast path. By moving that, it'd be > > easy to track contended

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Namhyung Kim
On Wed, Feb 9, 2022 at 12:17 PM Waiman Long wrote: > > > On 2/9/22 14:45, Namhyung Kim wrote: > > On Wed, Feb 9, 2022 at 11:28 AM Mathieu Desnoyers > > wrote: > >> - On Feb 9, 2022, at 2:22 PM, Namhyung Kim namhy...@kernel.org wrote: > >>> I'm also concerning dynamic allocated locks in a

[Intel-gfx] [PATCH] drm/i915/dg2: Invalidate LSC L1 cache

2022-02-09 Thread Anusha Srivatsa
Set the chicken bit to invalidate LSC L1 operation due to UAV coherency barrier. Cc: Matt Roper Signed-off-by: Anusha Srivatsa --- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + drivers/gpu/drm/i915/gt/intel_workarounds.c | 7 +++ 2 files changed, 8 insertions(+) diff --git

[Intel-gfx] ✗ Fi.CI.BAT: failure for GuC HWCONFIG with documentation (rev4)

2022-02-09 Thread Patchwork
== Series Details == Series: GuC HWCONFIG with documentation (rev4) URL : https://patchwork.freedesktop.org/series/99787/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_8 Summary ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Check stolen memory size before calling drm_mm_init (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Check stolen memory size before calling drm_mm_init (rev2) URL : https://patchwork.freedesktop.org/series/99917/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_7_full

Re: [Intel-gfx] i915 Updates: ADL-P DMC v2.16

2022-02-09 Thread Josh Boyer
Pulled and pushed out. josh On Tue, Jan 25, 2022 at 7:50 PM Tolakanahalli Pradeep, Madhumitha wrote: > > Hi Ben, Josh, Kyle, > > The following changes since commit > eb8ea1b46893c42edbd516f971a93b4d097730ab: > > Merge branch 'v1.1.7' of https://github.com/irui- > wang/linux_fw_vpu_v1.1.7 into

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for GuC HWCONFIG with documentation (rev4)

2022-02-09 Thread Patchwork
== Series Details == Series: GuC HWCONFIG with documentation (rev4) URL : https://patchwork.freedesktop.org/series/99787/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for GuC HWCONFIG with documentation (rev4)

2022-02-09 Thread Patchwork
== Series Details == Series: GuC HWCONFIG with documentation (rev4) URL : https://patchwork.freedesktop.org/series/99787/ State : warning == Summary == $ dim checkpatch origin/drm-tip 2a4b80691a34 drm/i915/guc: Add fetch of hwconfig table -:79: WARNING:FILE_PATH_CHANGES: added, moved or

[Intel-gfx] [PATCH v4 1/4] drm/i915/guc: Add fetch of hwconfig table

2022-02-09 Thread Jordan Justen
From: John Harrison Implement support for fetching the hardware description table from the GuC. The call is made twice - once without a destination buffer to query the size and then a second time to fill in the buffer. Note that the table is only available on ADL-P and later platforms. Cc:

[Intel-gfx] [PATCH v4 3/4] drm/i915/uapi: Add struct drm_i915_query_hwconfig_blob_item

2022-02-09 Thread Jordan Justen
Also, document DRM_I915_QUERY_HWCONFIG_BLOB with this struct. v3: * Add various changes suggested by Tvrtko Cc: Daniel Vetter Signed-off-by: Jordan Justen Acked-by: Jon Bloomfield --- include/uapi/drm/i915_drm.h | 35 +++ 1 file changed, 35 insertions(+)

[Intel-gfx] [PATCH v4 2/4] drm/i915/uapi: Add query for hwconfig blob

2022-02-09 Thread Jordan Justen
From: Rodrigo Vivi The DRM_I915_QUERY_HWCONFIG_BLOB query item returns a blob of data which it receives from the GuC software. This blob provides some useful data about the hardware for drivers. Although the blob is not fully documented at this time, the basic format is an array of u32 values.

[Intel-gfx] [PATCH v4 4/4] drm/i915/guc: Verify hwconfig blob matches supported format

2022-02-09 Thread Jordan Justen
i915_drm.h now defines the format of the returned DRM_I915_QUERY_HWCONFIG_BLOB query item. Since i915 receives this from the black box GuC software, it should verify that the data matches that format before sending it to user-space. The verification makes a single simple pass through the blob

[Intel-gfx] [PATCH v4 0/4] GuC HWCONFIG with documentation

2022-02-09 Thread Jordan Justen
This is John/Rodrigo's 2 patches with some minor changes, and I added 2 patches. "drm/i915/uapi: Add query for hwconfig blob" was changed: * Rename DRM_I915_QUERY_HWCONFIG_TABLE to DRM_I915_QUERY_HWCONFIG_BLOB as requested by Joonas. * Reword commit message * I added Acked-by to this

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Check stolen memory size before calling drm_mm_init URL : https://patchwork.freedesktop.org/series/99917/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_6_full

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Check stolen memory size before calling drm_mm_init (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Check stolen memory size before calling drm_mm_init (rev2) URL : https://patchwork.freedesktop.org/series/99917/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_7

[Intel-gfx] [PATCH v2] drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-09 Thread José Roberto de Souza
From: Steve Carbonari Add check for zero usable stolen memory before calling drm_mm_init to support configurations where stolen memory exists but is fully reserved. Also skip memory test in such case. v2: - convert stolen_usable_size to u64 so build do not break depending on PHYS_ADDR_T_64BIT

[Intel-gfx] ✗ Fi.CI.BUILD: warning for drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Check stolen memory size before calling drm_mm_init URL : https://patchwork.freedesktop.org/series/99917/ State : warning == Summary == CALLscripts/checksyscalls.sh CALLscripts/atomic/check-atomics.sh CHK include/generated/compile.h CC

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Check stolen memory size before calling drm_mm_init URL : https://patchwork.freedesktop.org/series/99917/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_6

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Waiman Long
On 2/9/22 14:45, Namhyung Kim wrote: On Wed, Feb 9, 2022 at 11:28 AM Mathieu Desnoyers wrote: - On Feb 9, 2022, at 2:22 PM, Namhyung Kim namhy...@kernel.org wrote: I'm also concerning dynamic allocated locks in a data structure. If we keep the info in a hash table, we should delete it

Re: [Intel-gfx] [PATCH 09/10] drm/i915: Return both master and slave pipes from enabled_bigjoiner_pipes()

2022-02-09 Thread Ville Syrjälä
On Wed, Feb 09, 2022 at 12:00:26PM -0800, Navare, Manasi wrote: > On Thu, Feb 03, 2022 at 08:38:22PM +0200, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Return both the master and slave pipe bitmasks from > > enabled_bigjoiner_pipes(). We'll have use for both during > > readout soon. > >

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display/tgl+: Implement new PLL programming step (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/display/tgl+: Implement new PLL programming step (rev2) URL : https://patchwork.freedesktop.org/series/99867/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_5_full

Re: [Intel-gfx] [PATCH 09/10] drm/i915: Return both master and slave pipes from enabled_bigjoiner_pipes()

2022-02-09 Thread Navare, Manasi
On Thu, Feb 03, 2022 at 08:38:22PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Return both the master and slave pipe bitmasks from > enabled_bigjoiner_pipes(). We'll have use for both during > readout soon. > > Signed-off-by: Ville Syrjälä This looks good, can this be just combined

Re: [Intel-gfx] [PATCH 08/10] drm/i915: Use for_each_intel_crtc_in_pipe_mask() more

2022-02-09 Thread Navare, Manasi
On Thu, Feb 03, 2022 at 08:38:21PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Convert a few hand roller for_each_intel_crtc_in_pipe_mask() > to the real thing. > > Signed-off-by: Ville Syrjälä Reviewed-by: Manasi Navare Manasi > --- >

Re: [Intel-gfx] [PATCH v6 1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API

2022-02-09 Thread Wang, Zhi A
On 2/9/22 9:04 AM, Jani Nikula wrote: > On Wed, 09 Feb 2022, Christoph Hellwig wrote: >> On Tue, Feb 08, 2022 at 05:15:00PM +0200, Jani Nikula wrote: #ifdef CONFIG_DRM_I915_GVT + +#define D_BDW (1 << 0) +#define D_SKL (1 << 1) +#define D_KBL (1 << 2)

Re: [Intel-gfx] [PATCH 07/10] drm/i915: Convert for_each_intel_crtc_mask() to take a pipe mask instead

2022-02-09 Thread Navare, Manasi
On Thu, Feb 03, 2022 at 08:38:20PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Often using pipes is more convenient than crtc indices. > Convert the current for_each_intel_crtc_mask() to take a > pipe mask instead of a crtc index mask, and rename it to >

Re: [Intel-gfx] [PATCH v6 1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API

2022-02-09 Thread Wang, Zhi A
On 2/9/22 7:28 AM, Christoph Hellwig wrote: > On Tue, Feb 08, 2022 at 05:15:00PM +0200, Jani Nikula wrote: >>> #ifdef CONFIG_DRM_I915_GVT >>> + >>> +#define D_BDW (1 << 0) >>> +#define D_SKL (1 << 1) >>> +#define D_KBL (1 << 2) >>> +#define D_BXT (1 << 3) >>> +#define D_CFL

[Intel-gfx] [PATCH] drm/i915: Check stolen memory size before calling drm_mm_init

2022-02-09 Thread José Roberto de Souza
From: Steve Carbonari Add check for zero usable stolen memory before calling drm_mm_init to support configurations where stolen memory exists but is fully reserved. Also skip memory test in such case. Cc: Ville Syrjälä Cc: Daniele Ceraolo Spurio Signed-off-by: José Roberto de Souza

Re: [Intel-gfx] [PATCH v6 2/3] i915/gvt: Save the initial HW state snapshot in i915

2022-02-09 Thread Wang, Zhi A
On 2/9/22 7:32 AM, Christoph Hellwig wrote: > On Tue, Feb 08, 2022 at 06:11:50AM -0500, Zhi Wang wrote: >> +struct drm_i915_private *dev_priv = iter->i915; >> +u32 *mmio, i; >> + >> +for (i = offset; i < offset + size; i += 4) { >> +mmio = iter->data + i; >> +

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Namhyung Kim
On Wed, Feb 9, 2022 at 11:28 AM Mathieu Desnoyers wrote: > > - On Feb 9, 2022, at 2:22 PM, Namhyung Kim namhy...@kernel.org wrote: > > I'm also concerning dynamic allocated locks in a data structure. > > If we keep the info in a hash table, we should delete it when the > > lock is gone. I'm

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Waiman Long
On 2/9/22 14:17, Mathieu Desnoyers wrote: - On Feb 9, 2022, at 2:02 PM, Waiman Long long...@redhat.com wrote: On 2/9/22 13:29, Mathieu Desnoyers wrote: - On Feb 9, 2022, at 1:19 PM, Waiman Long long...@redhat.com wrote: On 2/9/22 04:09, Peter Zijlstra wrote: On Tue, Feb 08, 2022 at

Re: [Intel-gfx] [PATCH 05/12] drm/i915: Protect lockdep functions with #ifdef

2022-02-09 Thread Namhyung Kim
Hello, On Wed, Feb 9, 2022 at 8:27 AM Steven Rostedt wrote: > > On Wed, 09 Feb 2022 15:49:01 +0200 > Jani Nikula wrote: > > > > Because I want to use the lockdep annotation for other purposes. > > > But the workqueue lockdep_map was defined under LOCKDEP > > > only. Please see the description

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Namhyung Kim
Hello, On Wed, Feb 9, 2022 at 11:02 AM Waiman Long wrote: > > On 2/9/22 13:29, Mathieu Desnoyers wrote: > > - On Feb 9, 2022, at 1:19 PM, Waiman Long long...@redhat.com wrote: > > > >> On 2/9/22 04:09, Peter Zijlstra wrote: > >>> On Tue, Feb 08, 2022 at 10:41:56AM -0800, Namhyung Kim wrote:

Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/7] drm/i915: Move vblank waits out from IPS code

2022-02-09 Thread Ville Syrjälä
On Wed, Feb 09, 2022 at 05:36:17PM -, Patchwork wrote: > == Series Details == > > Series: series starting with [1/7] drm/i915: Move vblank waits out from IPS > code > URL : https://patchwork.freedesktop.org/series/99898/ > State : failure > > == Summary == > > CI Bug Log - changes from

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2) URL : https://patchwork.freedesktop.org/series/99853/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_3_full

Re: [Intel-gfx] [PATCH v3 0/4] GuC HWCONFIG with documentation

2022-02-09 Thread Bloomfield, Jon
Acked-by: Jon Bloomfield > -Original Message- > From: Intel-gfx On Behalf Of > Jordan Justen > Sent: Tuesday, February 8, 2022 1:05 PM > To: intel-gfx > Cc: dri-devel > Subject: [Intel-gfx] [PATCH v3 0/4] GuC HWCONFIG with documentation > > This is John/Rodrigo's 2 patches with some

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Waiman Long
On 2/9/22 13:29, Mathieu Desnoyers wrote: - On Feb 9, 2022, at 1:19 PM, Waiman Long long...@redhat.com wrote: On 2/9/22 04:09, Peter Zijlstra wrote: On Tue, Feb 08, 2022 at 10:41:56AM -0800, Namhyung Kim wrote: Eventually I'm mostly interested in the contended locks only and I want to

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: move the DRIVER_* macros to i915_driver.[ch] (rev3)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: move the DRIVER_* macros to i915_driver.[ch] (rev3) URL : https://patchwork.freedesktop.org/series/99671/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_2_full

Re: [Intel-gfx] [RFC 00/12] locking: Separate lock tracepoints from lockdep/lock_stat (v1)

2022-02-09 Thread Waiman Long
On 2/9/22 04:09, Peter Zijlstra wrote: On Tue, Feb 08, 2022 at 10:41:56AM -0800, Namhyung Kim wrote: Eventually I'm mostly interested in the contended locks only and I want to reduce the overhead in the fast path. By moving that, it'd be easy to track contended locks with timing by using two

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/7] drm/i915: Move vblank waits out from IPS code

2022-02-09 Thread Patchwork
== Series Details == Series: series starting with [1/7] drm/i915: Move vblank waits out from IPS code URL : https://patchwork.freedesktop.org/series/99898/ State : failure == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_1_full

[Intel-gfx] [PATCH] drm/i915/: fix noderef.cocci warnings

2022-02-09 Thread kernel test robot
From: kernel test robot drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c:1310:32-38: ERROR: application of sizeof to pointer drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c:1322:32-38: ERROR: application of sizeof to pointer sizeof when applied to a pointer typed expression gives the size of

Re: [Intel-gfx] [PATCH v6 4/6] drm/i915/: Re-work clflush_write32

2022-02-09 Thread kernel test robot
Hi Michael, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on drm-tip/drm-tip drm/drm-next v5.17-rc3] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display/tgl+: Implement new PLL programming step (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/display/tgl+: Implement new PLL programming step (rev2) URL : https://patchwork.freedesktop.org/series/99867/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_5

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/ttm: tweak priority hint selection

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/ttm: tweak priority hint selection URL : https://patchwork.freedesktop.org/series/99897/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207_full -> Patchwork_0_full Summary

Re: [Intel-gfx] [PATCH 7/7] drm/i915: Consolidate all pre plane update vblank waits

2022-02-09 Thread Murthy, Arun R
> -Original Message- > From: Intel-gfx On Behalf Of Ville > Syrjala > Sent: Wednesday, February 9, 2022 5:05 PM > To: intel-gfx@lists.freedesktop.org > Subject: [Intel-gfx] [PATCH 7/7] drm/i915: Consolidate all pre plane update > vblank waits > > From: Ville Syrjälä > > There are

Re: [Intel-gfx] [PATCH 05/12] drm/i915: Protect lockdep functions with #ifdef

2022-02-09 Thread Steven Rostedt
On Wed, 09 Feb 2022 15:49:01 +0200 Jani Nikula wrote: > > Because I want to use the lockdep annotation for other purposes. > > But the workqueue lockdep_map was defined under LOCKDEP > > only. Please see the description in the cover letter. > > > >

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display/tgl+: Implement new PLL programming step (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/display/tgl+: Implement new PLL programming step (rev2) URL : https://patchwork.freedesktop.org/series/99867/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display/tgl+: Implement new PLL programming step (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915/display/tgl+: Implement new PLL programming step (rev2) URL : https://patchwork.freedesktop.org/series/99867/ State : warning == Summary == $ dim checkpatch origin/drm-tip 1dc3174e835d drm/i915/display/tgl+: Implement new PLL programming step -:51:

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2) URL : https://patchwork.freedesktop.org/series/99853/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_3

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Futher optimize plane updates (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: Futher optimize plane updates (rev2) URL : https://patchwork.freedesktop.org/series/99149/ State : failure == Summary == Applying: drm/i915: Clean up pre-skl primary plane registers Using index info to reconstruct a base tree... M

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2) URL : https://patchwork.freedesktop.org/series/99853/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: move intel_hws_csb_write_index() out of i915_drv.h (rev2) URL : https://patchwork.freedesktop.org/series/99853/ State : warning == Summary == $ dim checkpatch origin/drm-tip 365790a1da63 drm/i915: move intel_hws_csb_write_index() out of i915_drv.h -:50:

Re: [Intel-gfx] [GVT PULL] gvt-fixes for drm-intel-fixes

2022-02-09 Thread Wang, Zhi A
Hi folks: Ping. This pull seems not got merged. Thanks, Zhi. -Original Message- From: Zhi Wang Sent: Saturday, January 15, 2022 12:46 PM To: Vivi, Rodrigo ; jani.nik...@linux.intel.com; joonas.lahti...@linux.intel.com Cc: intel-gvt-...@lists.freedesktop.org;

Re: [Intel-gfx] [PATCH 3/6] dma-buf: Warn about dma_fence_chain container rules v2

2022-02-09 Thread Christian König
Am 09.02.22 um 15:02 schrieb Thomas Hellström: On Fri, 2022-02-04 at 11:04 +0100, Christian König wrote: Chaining of dma_fence_chain objects is only allowed through the prev fence and not through the contained fence. Warn about that when we create a dma_fence_chain. v2: fix comment style

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: move the DRIVER_* macros to i915_driver.[ch] (rev3)

2022-02-09 Thread Patchwork
== Series Details == Series: drm/i915: move the DRIVER_* macros to i915_driver.[ch] (rev3) URL : https://patchwork.freedesktop.org/series/99671/ State : success == Summary == CI Bug Log - changes from CI_DRM_11207 -> Patchwork_2

  1   2   >