Re: [Intel-gfx] [PATCH v2 1/3] drm/i915/selftests: Rename librapl library to libpower

> -Original Message- > From: Tauro, Riana > Sent: Monday, November 7, 2022 10:23 AM > To: intel-gfx@lists.freedesktop.org > Cc: Tauro, Riana ; Gupta, Anshuman > ; Dixit, Ashutosh ; > Tangudu, Tilak ; Nilawar, Badal > > Subject: [PATCH v2 1/3] drm/i915/selftests: Rename librapl library t

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dsc: Refactor dsc gen checks

== Series Details == Series: drm/i915/dsc: Refactor dsc gen checks URL : https://patchwork.freedesktop.org/series/110744/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_110744v1_full Summary ---

[Intel-gfx] [PULL] gvt-next

Hi, Here's current accumulated changes in gvt-next. Sorry that I delayed to refresh them on time for upstream...It contains mostly kernel doc, typo fixes and small code cleanups, as details below. btw, one gvt change for next https://patchwork.freedesktop.org/patch/58/ is still pending, I nee

[Intel-gfx] [PULL] gvt-fixes

Hi, Here's two fixes from Sean for 6.1 kernel, which is to fix kvm reference in gvt. No regression found in our test. Thanks! --- The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc: Linux 6.1-rc4 (2022-11-06 15:07:11 -0800) are available in the Git repository at: h

Re: [Intel-gfx] [PATCH 1/4] drm/i915/panelreplay: dpcd register definition for panelreplay

On Thu, 10 Nov 2022, Animesh Manna wrote: > DPCD register definition added to check and enable panel replay > capability of the sink. This patch is not i915 specific like the subject claims. Please always Cc: dri-devel for drm changes. BR, Jani. > > Cc: Jouni Högander > Signed-off-by: Animesh

Re: [Intel-gfx] [PATCH 3/4] drm/i915/panelreplay: Initializaton and compute config for panel replay

On Thu, 10 Nov 2022, Animesh Manna wrote: > As panel replay feature similar to PSR feature of EDP panel, so currently > utilized existing psr framework for panel replay. > > Cc: Jouni Högander > Signed-off-by: Animesh Manna > --- > .../drm/i915/display/intel_display_types.h| 15 +++ > d

[Intel-gfx] [PATCH 0/3] add track_remove_slot and remove track_flush_slot

This series is based on Sean's series https://lore.kernel.org/all/20221110014821.1548347-1-sea...@google.com/, which allows KVM internal user of page track not to rely on the page track hook .track_flush_slot. Page track hook track_flush_slot is for notification of slot flush and is called when a

[Intel-gfx] [PATCH 1/3] KVM: x86: add a new page track hook track_remove_slot

Page track hook track_remove_slot is used to notify users that a slot has been removed and is called when a slot DELETE/MOVE is about to be completed. Users of this hook can drop write protections in the removed slot. Note: Since KVM_MR_MOVE currently never actually happens in KVM/QEMU, and has n

[Intel-gfx] [PATCH 2/3] drm/i915/gvt: switch from track_flush_slot to track_remove_slot

KVMGT only cares about when a slot is indeed removed. So switch to use track_remove_slot which is called when a slot is removed. Cc: Zhenyu Wang Suggested-by: Sean Christopherson Signed-off-by: Yan Zhao --- drivers/gpu/drm/i915/gvt/kvmgt.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletio

[Intel-gfx] [PATCH 3/3] KVM: x86: Remove the unused page track hook track_flush_slot

There's no users of hook track_remove_slot any more and no external page tracker user cares about slot flush. So remove this hook. Cc: Zhenyu Wang Suggested-by: Sean Christopherson Signed-off-by: Yan Zhao --- arch/x86/include/asm/kvm_page_track.h | 11 --- arch/x86/kvm/mmu/page_track.c

[Intel-gfx] ✗ Fi.CI.BUILD: failure for add track_remove_slot and remove track_flush_slot

== Series Details == Series: add track_remove_slot and remove track_flush_slot URL : https://patchwork.freedesktop.org/series/110801/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/110801/revisions/1/mbox/ not applied Applying: KVM: x86: add a new

[Intel-gfx] [PATCH v2 0/3] add track_remove_slot and remove track_flush_slot

This series is based on Sean's series https://lore.kernel.org/all/20221110014821.1548347-1-sea...@google.com/, which allows KVM internal user of page track not to rely on the page track hook .track_flush_slot. Page track hook track_flush_slot is for notification of slot flush and is called when a

[Intel-gfx] [PATCH v2 1/3] KVM: x86: add a new page track hook track_remove_slot

Page track hook track_remove_slot is used to notify users that a slot has been removed and is called when a slot DELETE/MOVE is about to be completed. Users of this hook can drop write protections in the removed slot. Note: Since KVM_MR_MOVE currently never actually happens in KVM/QEMU, and has n

[Intel-gfx] [PATCH v2 2/3] drm/i915/gvt: switch from track_flush_slot to track_remove_slot

KVMGT only cares about when a slot is indeed removed. So switch to use track_remove_slot which is called when a slot is removed. Cc: Zhenyu Wang Suggested-by: Sean Christopherson Signed-off-by: Yan Zhao --- drivers/gpu/drm/i915/gvt/kvmgt.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletio

[Intel-gfx] [PATCH v2 3/3] KVM: x86: Remove the unused page track hook track_flush_slot

There's no users of hook track_remove_slot any more and no external page tracker user cares about slot flush. So remove this hook. Cc: Zhenyu Wang Suggested-by: Sean Christopherson Signed-off-by: Yan Zhao --- arch/x86/include/asm/kvm_page_track.h | 11 --- arch/x86/kvm/mmu/page_track.c

[Intel-gfx] [PATCH 0/4] drm/i915: Per-device display tracepoints

From: Ville Syrjälä Resurrect my old patch to include the device name in the display tracepoints. Seems like a good with discrete GPUs being a thing. Ville Syrjälä (4): drm/i915: Pass intel_plane to plane tracepoints drm/i915: Print plane name in fbc tracepoints drm/i915: Pass i915 to fron

[Intel-gfx] [PATCH 1/4] drm/i915: Pass intel_plane to plane tracepoints

From: Ville Syrjälä Pass intel_plane rather than drm_plane to the plane tracepoints. Matches what we do eg. with the fbc tracepoints. Using the same type for everything will help with digging out the device name from the plane in the future. Signed-off-by: Ville Syrjälä --- .../gpu/drm/i915/di

[Intel-gfx] [PATCH 3/4] drm/i915: Pass i915 to frontbuffer tracepoints

From: Ville Syrjälä Pass the device to the frontbuffer tracpoints. Will be used later to include the device name in the tracpoints. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/display/intel_display_trace.h | 10 ++ drivers/gpu/drm/i915/display/intel_frontbuffer.c | 4 ++--

[Intel-gfx] [PATCH 2/4] drm/i915: Print plane name in fbc tracepoints

From: Ville Syrjälä Print the name of the plane in the fbc tracepoints. As the pipe<->plane assignment can vary on old hw it's probably more helpful to see both the plane and the pipe names together. Signed-off-by: Ville Syrjälä --- .../drm/i915/display/intel_display_trace.h| 21 ++

[Intel-gfx] [PATCH 4/4] drm/i915: Add device name to display tracepoints

From: Ville Syrjälä Include dev_name() in the tracpoints so one can filter based on the device. Example: echo 'dev==":00:02.0"' > events/i915/intel_cpu_fifo_underrun/filter v2: Reduce the magic macros, rebase Signed-off-by: Ville Syrjälä --- .../drm/i915/display/intel_display_trace.h

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Thu, Nov 10, 2022 at 11:49:19PM +0200, Ville Syrjälä wrote: > On Thu, Nov 10, 2022 at 09:55:55PM +0200, Imre Deak wrote: > > On Thu, Nov 10, 2022 at 09:11:20PM +0200, Ville Syrjälä wrote: > > > On Tue, Nov 08, 2022 at 05:18:23PM +0200, Imre Deak wrote: > > > > Since the intel_display_power_domai

[Intel-gfx] ✗ Fi.CI.BUILD: failure for add track_remove_slot and remove track_flush_slot (rev2)

== Series Details == Series: add track_remove_slot and remove track_flush_slot (rev2) URL : https://patchwork.freedesktop.org/series/110801/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/110801/revisions/2/mbox/ not applied Applying: KVM: x86: ad

Re: [Intel-gfx] [PATCH v1 1/6] dma-buf: Move dma_buf_mmap_internal() to dynamic locking specification

Am 10.11.22 um 21:13 schrieb Dmitry Osipenko: All dma-buf functions has been moved to dynamic locking specification The dma_buf_mmap_internal() was missed out by accident. Take reservation lock around file mapping operation to adhere the common locking convention. Reported-by: Daniel Vetter Sig

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Per-device display tracepoints

== Series Details == Series: drm/i915: Per-device display tracepoints URL : https://patchwork.freedesktop.org/series/110807/ State : warning == Summary == Error: dim checkpatch failed c586ca99d701 drm/i915: Pass intel_plane to plane tracepoints 8969e95b9f31 drm/i915: Print plane name in fbc tr

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Per-device display tracepoints

== Series Details == Series: drm/i915: Per-device display tracepoints URL : https://patchwork.freedesktop.org/series/110807/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12370 -> Patchwork_110807v1 Summary --- **FAI

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 02:37:13PM +0200, Imre Deak wrote: > On Thu, Nov 10, 2022 at 11:49:19PM +0200, Ville Syrjälä wrote: > > On Thu, Nov 10, 2022 at 09:55:55PM +0200, Imre Deak wrote: > > > On Thu, Nov 10, 2022 at 09:11:20PM +0200, Ville Syrjälä wrote: > > > > On Tue, Nov 08, 2022 at 05:18:23PM

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 03:43:54PM +0200, Ville Syrjälä wrote: > On Fri, Nov 11, 2022 at 02:37:13PM +0200, Imre Deak wrote: > > On Thu, Nov 10, 2022 at 11:49:19PM +0200, Ville Syrjälä wrote: > > > On Thu, Nov 10, 2022 at 09:55:55PM +0200, Imre Deak wrote: > > > > On Thu, Nov 10, 2022 at 09:11:20PM

[Intel-gfx] [PATCH v3 18/18] drm/i915: Do state check for color management changes

From: Ville Syrjälä In order to validate LUT programming more thoroughly let's do a state check for all color management updates as well. Not sure we really want this outside CI. It is rather heavy and color management updates could become rather common with all the HDR/etc. stuff happening. May

Re: [Intel-gfx] [PATCH v2 01/18] drm/i915: Clean up legacy palette defines

On Thu, 10 Nov 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > Use consistent bit definitions for the legacy gamma LUT. We just > define these alongside the pre-ilk register definitions and point > to those from the ilk+ defines. > > Also use the these appropriately in the LUT entry pack/unp

Re: [Intel-gfx] [PATCH v2 02/18] drm/i915: Clean up 10bit precision palette defines

On Thu, 10 Nov 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > Use consistent bit definitions for the 10bit precision palette bits. > We just define these alongside the ilk/snb register definitions and > point to those from the ivb+ defines. > > Also use the these appropriately in the LUT en

Re: [Intel-gfx] [PATCH v2 03/18] drm/i915: Clean up 12.4bit precision palette defines

On Thu, 10 Nov 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > Use consistent bit definitions for the 12.4bit precision palette bits. > We just define these alongside the ilk/snb register definitions and > point to those from the icl+ superfine segment defines (and we also > already pointed

Re: [Intel-gfx] [PATCH v2 05/18] drm/i915: Reorder 12.4 lut udw vs. ldw functions

On Thu, 10 Nov 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > Satisfy my ocd and define ilk_lut_12p4_ldw() before ilk_lut_12p4_udw(). > That is the order all the other similar functions use. > > Signed-off-by: Ville Syrjälä Reviewed-by: Jani Nikula > --- > drivers/gpu/drm/i915/display/

Re: [Intel-gfx] [PATCH v2 04/18] drm/i915: Clean up chv CGM (de)gamma defines

On Thu, 10 Nov 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > Add the missing ldw vs. udw information to the CGM (de)gamma > bit definitions to make it a bit easier to see which should > be used where. > > Also use the these appropriately in the LUT entry pack/unpack > functions. > > Signed

Re: [Intel-gfx] [PATCH 0/3] Add _PICK_EVEN_RANGES

On Fri, 21 Oct 2022, Lucas De Marchi wrote: > On Wed, Oct 12, 2022 at 12:05:31PM -0700, Lucas De Marchi wrote: >>On Wed, Oct 12, 2022 at 11:51:48AM +0300, Jani Nikula wrote: >>>On Tue, 11 Oct 2022, Lucas De Marchi wrote: Add a new macro, _PICK_EVEN_RANGES, that supports using 2 address ra

Re: [Intel-gfx] [PATCH v2 0/4] drm/i915: header cleanups, cont'd

On Wed, 09 Nov 2022, Lucas De Marchi wrote: > On Wed, Nov 09, 2022 at 05:35:18PM +0200, Jani Nikula wrote: >>The remaining patches from [1], rebased. >> >>I also realized this conflicts with what Lucas is doing so I'd like to >>get feedback. > > if you are talking about > https://patchwork.freedes

Re: [Intel-gfx] ✓ Fi.CI.BAT: success for Add selftest for slpc tile interaction (rev4)

On 11/10/2022 1:06 AM, Patchwork wrote: *Patch Details* *Series:* Add selftest for slpc tile interaction (rev4) *URL:* https://patchwork.freedesktop.org/series/110248/ *State:*success *Details:* https://intel-gfx-ci.01.org/tre

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Finish (de)gamma readout (rev3)

== Series Details == Series: drm/i915: Finish (de)gamma readout (rev3) URL : https://patchwork.freedesktop.org/series/79614/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12370 -> Patchwork_79614v3 Summary --- **FAIL

Re: [Intel-gfx] [PATCH 0/4] drm/i915: Per-device display tracepoints

On Fri, 11 Nov 2022, Ville Syrjala wrote: > From: Ville Syrjälä > > Resurrect my old patch to include the device name in the display > tracepoints. Seems like a good with discrete GPUs being a thing. FWIW, on the series, Acked-by: Jani Nikula > > Ville Syrjälä (4): > drm/i915: Pass intel_

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 03:52:08PM +0200, Ville Syrjälä wrote: > On Fri, Nov 11, 2022 at 03:43:54PM +0200, Ville Syrjälä wrote: > > On Fri, Nov 11, 2022 at 02:37:13PM +0200, Imre Deak wrote: > > > On Thu, Nov 10, 2022 at 11:49:19PM +0200, Ville Syrjälä wrote: > > > > On Thu, Nov 10, 2022 at 09:55:5

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Simplify internal helper function signature

== Series Details == Series: drm/i915: Simplify internal helper function signature URL : https://patchwork.freedesktop.org/series/110753/ State : success == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_110753v1_full S

[Intel-gfx] [PATCH i-g-t 0/8] Vendor agnostic gputop

From: Tvrtko Ursulin This is a pile of patches which implements a rudimentary vendor agnostic gputop tool based of the new DRM spec as documented in Documentation/gpu/drm-usage-stats.rst. First part of the series is code refactoring which should be reasonably stable. I've tested it all while wor

[Intel-gfx] [PATCH i-g-t 1/8] lib: Extract igt_drm_clients from intel_gpu_top

From: Tvrtko Ursulin Extract some code into a new library to prepare for further work towards making a vendor agnostic gputop tool. Signed-off-by: Tvrtko Ursulin --- lib/igt_drm_clients.c | 432 ++ lib/igt_drm_clients.h | 85 +++ lib/meson.build | 8

[Intel-gfx] [PATCH i-g-t 3/8] libdrmclients: Record client drm minor

From: Tvrtko Ursulin Prepare for supporting clients belonging to multiple DRM cards by storing the DRM minor in the client record. Signed-off-by: Tvrtko Ursulin --- lib/igt_drm_clients.c | 22 ++ lib/igt_drm_clients.h | 1 + 2 files changed, 15 insertions(+), 8 deletions(-

[Intel-gfx] [PATCH i-g-t 2/8] libdrmfdinfo: Allow specifying custom engine map

From: Tvrtko Ursulin Instead of hard coding the engine names, allow a map of names to indices to either be passed in or it gets auto-detected (less efficient) while parsing. --- lib/igt_drm_clients.c | 18 +--- lib/igt_drm_clients.h | 3 ++- lib/igt_drm_fdinfo.c| 48

[Intel-gfx] [PATCH i-g-t 4/8] libdrmclient: Support multiple DRM cards

From: Tvrtko Ursulin Require DRM minor match during client lookup. Signed-off-by: Tvrtko Ursulin --- lib/igt_drm_clients.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/lib/igt_drm_clients.c b/lib/igt_drm_clients.c index c23a3fae9793..e11c8b18188f 100644 --

[Intel-gfx] [PATCH i-g-t 7/8] libdrmclient: Enforce client status sort order in the library

From: Tvrtko Ursulin Some libdrmclient operations require that inactive clients are last in the list. Rather than relying on callers of the library sort routine to implement their comparison callbacks correctly, enforce this order directly in the library and let callers comparison callbacks conce

[Intel-gfx] [PATCH i-g-t 5/8] libdrmfdinfo: Track largest engine index

From: Tvrtko Ursulin Prep code for incoming work. Signed-off-by: Tvrtko Ursulin --- lib/igt_drm_fdinfo.c | 2 ++ lib/igt_drm_fdinfo.h | 1 + 2 files changed, 3 insertions(+) diff --git a/lib/igt_drm_fdinfo.c b/lib/igt_drm_fdinfo.c index 68c89ad2c17e..b850d2210ae7 100644 --- a/lib/igt_drm_fdin

[Intel-gfx] [PATCH i-g-t 6/8] libdrmclient/intel_gpu_top: Decouple hardcoded engine assumptions

From: Tvrtko Ursulin Intel_gpu_top gets it's main engine configuration data via PMU probe and uses that for per client view as well. Furthemore code so far assumed only clients belonging from a single DRM card would be tracked in a single clients list. Break this inter-dependency by moving the e

[Intel-gfx] [PATCH i-g-t 8/8] gputop: Basic vendor agnostic GPU top tool

From: Tvrtko Ursulin Rudimentary vendor agnostic example of how lib_igt_drm_clients can be used to display a sorted by card and usage list of processes using GPUs. Borrows a bit of code from intel_gpu_top but for now omits the fancy features like interactive functionality, card selection, client

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: ELD precompute and readout (rev4)

== Series Details == Series: drm/i915: ELD precompute and readout (rev4) URL : https://patchwork.freedesktop.org/series/109592/ State : success == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_109592v4_full Summary ---

Re: [Intel-gfx] [PATCH] drm/i915/ttm: never purge busy objects

On Mon, Nov 07, 2022 at 01:30:27PM +, Matthew Auld wrote: In i915_gem_madvise_ioctl() we immediately purge the object is not currently used, like when the mm.pages are NULL. With shmem the pages might still be hanging around or are perhaps swapped out. Similarly with ttm we might still have

Re: [Intel-gfx] [PATCH v2 01/18] drm/i915: Clean up legacy palette defines

On Fri, Nov 11, 2022 at 05:09:37PM +0200, Jani Nikula wrote: > On Thu, 10 Nov 2022, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Use consistent bit definitions for the legacy gamma LUT. We just > > define these alongside the pre-ilk register definitions and point > > to those from the ilk

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 05:47:05PM +0200, Imre Deak wrote: > On Fri, Nov 11, 2022 at 03:52:08PM +0200, Ville Syrjälä wrote: > > On Fri, Nov 11, 2022 at 03:43:54PM +0200, Ville Syrjälä wrote: > > > On Fri, Nov 11, 2022 at 02:37:13PM +0200, Imre Deak wrote: > > > > On Thu, Nov 10, 2022 at 11:49:19PM

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Per-device display tracepoints (rev2)

== Series Details == Series: drm/i915: Per-device display tracepoints (rev2) URL : https://patchwork.freedesktop.org/series/110807/ State : warning == Summary == Error: dim checkpatch failed 57ffee5e5bd2 drm/i915: Pass intel_plane to plane tracepoints bf87f6d30e3d drm/i915: Print plane name in

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 08:30:41PM +0200, Ville Syrjälä wrote: > On Fri, Nov 11, 2022 at 05:47:05PM +0200, Imre Deak wrote: > > On Fri, Nov 11, 2022 at 03:52:08PM +0200, Ville Syrjälä wrote: > > > On Fri, Nov 11, 2022 at 03:43:54PM +0200, Ville Syrjälä wrote: > > > > On Fri, Nov 11, 2022 at 02:37:1

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Per-device display tracepoints (rev2)

== Series Details == Series: drm/i915: Per-device display tracepoints (rev2) URL : https://patchwork.freedesktop.org/series/110807/ State : success == Summary == CI Bug Log - changes from CI_DRM_12371 -> Patchwork_110807v2 Summary ---

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 08:56:16PM +0200, Imre Deak wrote: > On Fri, Nov 11, 2022 at 08:30:41PM +0200, Ville Syrjälä wrote: > > On Fri, Nov 11, 2022 at 05:47:05PM +0200, Imre Deak wrote: > > > On Fri, Nov 11, 2022 at 03:52:08PM +0200, Ville Syrjälä wrote: > > > > On Fri, Nov 11, 2022 at 03:43:54PM

[Intel-gfx] [PATCH] drm/i915/display: Add missing checks for cdclk crawling

cdclk_sanitize() function was written assuming vco was a signed integer. vco gets assigned to -1 (essentially ~0) for the case where PLL might be enabled and vco is not a frequency that will ever get used. In such a scenario the right thing to do is disable the PLL and re-enable it again with a val

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Finish (de)gamma readout (rev4)

== Series Details == Series: drm/i915: Finish (de)gamma readout (rev4) URL : https://patchwork.freedesktop.org/series/79614/ State : warning == Summary == Error: dim checkpatch failed 014e74f2af51 drm/i915: Clean up legacy palette defines f61b7422bca8 drm/i915: Clean up 10bit precision palette

Re: [Intel-gfx] [PATCH] drm/i915/display: Add missing checks for cdclk crawling

On Fri, Nov 11, 2022 at 11:26:02AM -0800, Anusha Srivatsa wrote: > cdclk_sanitize() function was written assuming vco was a signed integer. > vco gets assigned to -1 (essentially ~0) for the case where PLL > might be enabled and vco is not a frequency that will ever > get used. In such a scenario t

[Intel-gfx] ✓ Fi.CI.IGT: success for Panel replay phase1 implementation (rev4)

== Series Details == Series: Panel replay phase1 implementation (rev4) URL : https://patchwork.freedesktop.org/series/94470/ State : success == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_94470v4_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Finish (de)gamma readout (rev4)

== Series Details == Series: drm/i915: Finish (de)gamma readout (rev4) URL : https://patchwork.freedesktop.org/series/79614/ State : success == Summary == CI Bug Log - changes from CI_DRM_12371 -> Patchwork_79614v4 Summary --- **SUCC

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Add missing checks for cdclk crawling (rev2)

== Series Details == Series: drm/i915/display: Add missing checks for cdclk crawling (rev2) URL : https://patchwork.freedesktop.org/series/110734/ State : success == Summary == CI Bug Log - changes from CI_DRM_12371 -> Patchwork_110734v2 Su

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: enable GuC GGTT invalidation from the start

== Series Details == Series: drm/i915/guc: enable GuC GGTT invalidation from the start URL : https://patchwork.freedesktop.org/series/110772/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_110772v1_full ===

Re: [Intel-gfx] [PATCH v1 0/6] Move dma_buf_mmap_internal() to dynamic locking specification

On 11/10/22 23:13, Dmitry Osipenko wrote: > Hello, > > Recently, dma-buf got a common locking convention for importers and > exporters. All the dma-buf functions were moved to the new locking > convention, apart from the dma_buf_mmap_internal() that was missed out > by accident. This series moves

Re: [Intel-gfx] [PATCH v3 1/9] drm/i915: Allocate power domain set wakerefs dynamically

On Fri, Nov 11, 2022 at 09:23:59PM +0200, Ville Syrjälä wrote: > On Fri, Nov 11, 2022 at 08:56:16PM +0200, Imre Deak wrote: > > On Fri, Nov 11, 2022 at 08:30:41PM +0200, Ville Syrjälä wrote: > > > On Fri, Nov 11, 2022 at 05:47:05PM +0200, Imre Deak wrote: > > > > On Fri, Nov 11, 2022 at 03:52:08PM

[Intel-gfx] ✗ Fi.CI.IGT: failure for Move dma_buf_mmap_internal() to dynamic locking specification

== Series Details == Series: Move dma_buf_mmap_internal() to dynamic locking specification URL : https://patchwork.freedesktop.org/series/110777/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_110777v1_full ===

[Intel-gfx] [PATCH 0/7] DYNAMIC_DEBUG fixups for rc

hi Jason, Greg, DRM-folk, drm.debug-on-dyndbg has a regression due to a chicken-&-egg problem; drm.debug is applied to enable dyndbg callsites before the dependent modules' callsites are available to be enabled. My "fixes" are unready, so lets just mark it BROKEN for now. Meanwhile, heres some o

[Intel-gfx] [PATCH 1/7] drm: mark drm.debug-on-dyndbg as BROKEN for now

drm.debug-on-dyndbg has a regression, due to a chicken-egg initialization problem: 1- modprobe i915 i915 needs drm.ko, which is loaded 1st 2- "modprobe drm drm.debug=0x1ff" (virtual/implied) drm.debug is set post-initialization, from boot-args etc 3- `modprobe i915` finishes W/O drm.debug

[Intel-gfx] [PATCH 2/7] drm_print: fixup improve stale comment

Cited commit uses stale macro name, fix this. And improve the explanation. When DRM_USE_DYNAMIC_DEBUG=y, DECLARE_DYNDBG_CLASSMAP() does the mapping of DRM_UT_* onto BITs in drm.debug. While this is still using the drm_debug_category enum to do the mapping, its doing so somewhat indirectly, with

[Intel-gfx] [PATCH 4/7] test-dyndbg: show that DEBUG enables prdbgs at compiletime

Dyndbg is required to enable prdbgs at compile-time if DEBUG is defined. Show this works; add the defn to test_dynamic_debug.c, and manually inspect/verify its effect at module load: [ 15.292810] dyndbg: module:test_dynamic_debug attached 4 classes [ 15.293189] dyndbg: 32 debug prints in mod

[Intel-gfx] [PATCH 5/7] dyndbg: fix readback value on LEVEL_NAMES interfaces

Since sysfs knobs should generally read-back what was just written (unless theres a good reason to do otherwise), this result (using test_dynamic_debug.ko) is suboptimal: echo L3 > p_level_names cat p_level_names 4 Fix this with a -1 offset in LEVEL_NAMES readback. NOTE: Calling this a BU

[Intel-gfx] [PATCH 6/7] dyndbg: clone DECLARE_DYNDBG_CLASSMAP to REFERENCE_DYNDBG_CLASSMAP

DECLARE_DYNDBG_CLASSMAPs job is to allow modules to declare the debug classes/categories they want dyndbg to >control. Its args name the class-names, and the sysfs interface style (usually a class-bitmap). A separate module_param_cb wires the sysfs node to the classmap. In DRM, multiple modules d

[Intel-gfx] [PATCH 3/7] test-dyndbg: fixup CLASSMAP usage error

more careful reading of test output reveals: lib/test_dynamic_debug.c:103 [test_dynamic_debug]do_cats =pmf "doing categories\n" lib/test_dynamic_debug.c:105 [test_dynamic_debug]do_cats =p "LOW msg\n" class:MID lib/test_dynamic_debug.c:106 [test_dynamic_debug]do_cats =p "MID msg\n" class:HI lib/t

[Intel-gfx] [PATCH 7/7] dyndbg: replace classmap list with a vector

Classmaps are stored/linked in a section/array, but are each added to the module's ddebug_table.maps list-head. This is unnecessary; even when ddebug_attach_classmap() is handling the builtin section (with classmaps for multiple builtin modules), its contents are ordered, so a module's possibly mu

[Intel-gfx] [PATCH] drm/i915: disable DMC idle states for Intel UHD Graphics 620

Some machines with Intel UHD Graphics 620 (8086:5917) such as Dell Latitude 7490 are unable to wake from sleep. Disable DMC for Intel UHD Graphics 620. Link: https://gitlab.freedesktop.org/drm/intel/-/issues/7339 Signed-off-by: Steven 'Steve' Kendall --- drivers/gpu/drm/i915/i915_pci.c | 14

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: add the GSC CS to the GuC capture list

== Series Details == Series: drm/i915/guc: add the GSC CS to the GuC capture list URL : https://patchwork.freedesktop.org/series/110779/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_110779v1_full Su

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: disable DMC idle states for Intel UHD Graphics 620

== Series Details == Series: drm/i915: disable DMC idle states for Intel UHD Graphics 620 URL : https://patchwork.freedesktop.org/series/110830/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12371 -> Patchwork_110830v1 Summ

Re: [Intel-gfx] [PATCH v2 1/3] KVM: x86: add a new page track hook track_remove_slot

On Fri, Nov 11, 2022 at 06:19:15PM +, Sean Christopherson wrote: > TL;DR: I'm going to try to add more aggressive patches for this into my > series to > clean up the KVM side of things, along with many more patches to clean up the > page > track APIs. > > I'll post patches next week if thing

Re: [Intel-gfx] [PATCH v2 2/3] drm/i915/gvt: switch from track_flush_slot to track_remove_slot

On Fri, Nov 11, 2022 at 05:07:35PM +, Sean Christopherson wrote: > On Fri, Nov 11, 2022, Yan Zhao wrote: > > KVMGT only cares about when a slot is indeed removed. > > So switch to use track_remove_slot which is called when a slot is removed. > > This should capture the original motivation, i.e

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/huc: fix leak of debug object in huc load fence on driver unload

== Series Details == Series: drm/i915/huc: fix leak of debug object in huc load fence on driver unload URL : https://patchwork.freedesktop.org/series/110783/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12369_full -> Patchwork_110783v1_full ==