Re: [Intel-gfx] [PATCH v2 11/11] iommufd: Allow iommufd to supply /dev/vfio/vfio

On 2022/11/11 12:16, Yi Liu wrote: On 2022/11/8 08:52, Jason Gunthorpe wrote: If the VFIO container is compiled out, give a kconfig option for iommufd to provide the miscdev node with the same name and permissions as vfio uses. The compatibility node supports the same ioctls as VFIO and

[Intel-gfx] ✓ Fi.CI.BAT: success 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 : success == Summary == CI Bug Log - changes from CI_DRM_12369 -> Patchwork_110783v1

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

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

[Intel-gfx] ✓ Fi.CI.BAT: success 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 : success == Summary == CI Bug Log - changes from CI_DRM_12369 -> Patchwork_110779v1 Summary

[Intel-gfx] ✓ Fi.CI.BAT: success 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 : success == Summary == CI Bug Log - changes from CI_DRM_12369 -> Patchwork_110777v1

[Intel-gfx] ✓ Fi.CI.BAT: success 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 : success == Summary == CI Bug Log - changes from CI_DRM_12369 -> Patchwork_110772v1

[Intel-gfx] ✗ Fi.CI.BAT: failure for Fix live busy stats selftest failure (rev2)

== Series Details == Series: Fix live busy stats selftest failure (rev2) URL : https://patchwork.freedesktop.org/series/110557/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12369 -> Patchwork_110557v2 Summary ---

Re: [Intel-gfx] [PATCH 0/2] drm/i915/gvt: Fix for KVM refcounting bug

On 2022.11.11 00:22:23 +, Sean Christopherson wrote: > Bug fix and cleanup related to KVM refcounting. Found by inspection while > attempting to clean up KVM's page-tracker APIs. > > Compile tested only! > > Sean Christopherson (2): > drm/i915/gvt: Get reference to KVM iff attachment to

[Intel-gfx] ✗ Fi.CI.SPARSE: warning 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 : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. -

[Intel-gfx] ✗ Fi.CI.IGT: failure for linux-next: build failure after merge of the drm-misc tree

== Series Details == Series: linux-next: build failure after merge of the drm-misc tree URL : https://patchwork.freedesktop.org/series/110730/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_110730v1_full

Re: [Intel-gfx] [PATCH v4 1/1] drm/i915/guc/slpc: Add selftest for slpc tile-tile interaction

On 11/9/2022 3:25 AM, Riana Tauro wrote: Run a workload on tiles simultaneously by requesting for RP0 frequency. Pcode can however limit the frequency being granted due to throttling reasons. This test checks if there is any throttling but does not fail if RP0 is not granted due to throttle

[Intel-gfx] ✓ Fi.CI.BAT: 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 -> Patchwork_94470v4 Summary ---

[Intel-gfx] ✗ Fi.CI.SPARSE: warning 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 : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH v2 11/11] iommufd: Allow iommufd to supply /dev/vfio/vfio

On 2022/11/8 08:52, Jason Gunthorpe wrote: If the VFIO container is compiled out, give a kconfig option for iommufd to provide the miscdev node with the same name and permissions as vfio uses. The compatibility node supports the same ioctls as VFIO and automatically enables the VFIO

Re: [Intel-gfx] [PATCH v2 09/11] vfio: Move container related MODULE_ALIAS statements into container.c

On 2022/11/8 08:52, Jason Gunthorpe wrote: The miscdev is in container.c, so should these related MODULE_ALIAS statements. This is necessary for the next patch to be able to fully disable /dev/vfio/vfio. Fixes: cdc71fe4ecbf ("vfio: Move container code into drivers/vfio/container.c")

Re: [Intel-gfx] [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices

On 2022/11/8 08:52, Jason Gunthorpe wrote: This creates the iommufd_device for the physical VFIO drivers. These are all the drivers that are calling vfio_register_group_dev() and expect the type1 code to setup a real iommu_domain against their parent struct device. The design gives the driver a

[Intel-gfx] ✗ Fi.CI.BUILD: failure for Connect VFIO to IOMMUFD (rev5)

== Series Details == Series: Connect VFIO to IOMMUFD (rev5) URL : https://patchwork.freedesktop.org/series/110133/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/110133/revisions/5/mbox/ not applied Applying: vfio: Move vfio_device driver

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix live busy stats selftest failure (rev2)

== Series Details == Series: Fix live busy stats selftest failure (rev2) URL : https://patchwork.freedesktop.org/series/110557/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH v1 5/6] media: videobuf2: Assert held reservation lock for dma-buf mmapping

On Fri, Nov 11, 2022 at 5:15 AM Dmitry Osipenko wrote: > > When userspace mmaps dma-buf's fd, the dma-buf reservation lock must be > held. Add locking sanity checks to the dma-buf mmaping callbacks to ensure > that the locking assumptions won't regress in the future. > > Suggested-by: Daniel

[Intel-gfx] ✓ Fi.CI.BAT: 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 -> Patchwork_109592v4 Summary ---

Re: [Intel-gfx] [PATCH v1] drm/i915/gt: Add sysfs RAPL PL1 interface

On 11/9/2022 6:37 AM, Dixit, Ashutosh wrote: On Thu, 03 Nov 2022 05:37:23 -0700, Sujaritha Sundaresan wrote: Hi Suja, Adding the rapl_pl1_freq_mhz sysfs attribute. Signed-off-by: Sujaritha Sundaresan Cc: Ashutosh Dixit --- drivers/gpu/drm/i915/gt/intel_gt_sysfs_pm.c | 20 ++

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Panel replay phase1 implementation (rev4)

== Series Details == Series: Panel replay phase1 implementation (rev4) URL : https://patchwork.freedesktop.org/series/94470/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Panel replay phase1 implementation (rev4)

== Series Details == Series: Panel replay phase1 implementation (rev4) URL : https://patchwork.freedesktop.org/series/94470/ State : warning == Summary == Error: dim checkpatch failed 03d1576a6e6b drm/i915/panelreplay: dpcd register definition for panelreplay 474dba49884a

[Intel-gfx] ✗ Fi.CI.IGT: failure for Fix timeout handling when retiring requests

== Series Details == Series: Fix timeout handling when retiring requests URL : https://patchwork.freedesktop.org/series/110729/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_110729v1_full Summary

Re: [Intel-gfx] [PATCH v2 00/11] Connect VFIO to IOMMUFD

On 11/7/22 7:52 PM, Jason Gunthorpe wrote: > This series provides an alternative container layer for VFIO implemented > using iommufd. This is optional, if CONFIG_IOMMUFD is not set then it will > not be compiled in. > > At this point iommufd can be injected by passing in a iommfd FD to >

Re: [Intel-gfx] [PATCH 2/2] drm/i915/gvt: Unconditionally put reference to KVM when detaching vGPU

> From: Sean Christopherson > Sent: Friday, November 11, 2022 8:22 AM > > Always put the KVM reference when closing a vCPU device, as > intel_vgpu_open_device() succeeds if and only if the KVM pointer is > valid and a reference to KVM is acquired. And if that doesn't hold true, > the call to

Re: [Intel-gfx] [PATCH 1/2] drm/i915/gvt: Get reference to KVM iff attachment to VM is successful

> From: Sean Christopherson > Sent: Friday, November 11, 2022 8:22 AM > > Get a reference to KVM if and only if a vGPU is successfully attached to > the VM to avoid leaking a reference if there's no available vGPU. On > open_device() failure, vfio_device_open() doesn't invoke close_device(). >

[Intel-gfx] ✗ Fi.CI.SPARSE: warning 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 : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning 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 : warning == Summary == Error: dim checkpatch failed dd5b3afe38e7 drm/i915/audio: Don't program the hardware ELD buffer on ilk+ 663c2d197a11 drm/i915/audio:

[Intel-gfx] ✓ Fi.CI.BAT: 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 -> Patchwork_110753v1 Summary

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm: Analog TV Improvements (rev9)

== Series Details == Series: drm: Analog TV Improvements (rev9) URL : https://patchwork.freedesktop.org/series/107892/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12369 -> Patchwork_107892v9 Summary ---

[Intel-gfx] ✓ Fi.CI.IGT: success for DRM scheduling cgroup controller (rev2)

== Series Details == Series: DRM scheduling cgroup controller (rev2) URL : https://patchwork.freedesktop.org/series/109902/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_109902v2_full Summary

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm: Analog TV Improvements (rev9)

== Series Details == Series: drm: Analog TV Improvements (rev9) URL : https://patchwork.freedesktop.org/series/107892/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: Analog TV Improvements (rev9)

== Series Details == Series: drm: Analog TV Improvements (rev9) URL : https://patchwork.freedesktop.org/series/107892/ State : warning == Summary == Error: dim checkpatch failed 7592c541f416 drm/tests: Add Kunit Helpers -:33: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does

[Intel-gfx] [PATCH] drm/i915/huc: fix leak of debug object in huc load fence on driver unload

The fence is always initialized in huc_init_early, but the cleanup in huc_fini is only being run if HuC is enabled. This causes a leaking of the debug object when HuC is disabled/not supported, which can in turn trigger a warning if we try to register a new debug offset at the same address on

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3)

== Series Details == Series: series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3) URL : https://patchwork.freedesktop.org/series/110646/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_110646v3_full

[Intel-gfx] [PATCH] drm/i915/guc: add the GSC CS to the GuC capture list

For the GSC engine we only want to capture the instance regs. Signed-off-by: Daniele Ceraolo Spurio Cc: Alan Previn --- drivers/gpu/drm/i915/gt/uc/intel_guc_capture.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_capture.c

Re: [Intel-gfx] [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices

> From: Jason Gunthorpe > Sent: Friday, November 11, 2022 1:21 AM > > On Thu, Nov 10, 2022 at 03:11:16AM +, Tian, Kevin wrote: > > > From: Jason Gunthorpe > > > Sent: Tuesday, November 8, 2022 8:53 AM > > > > > > + > > > +int vfio_iommufd_bind(struct vfio_device *vdev, struct iommufd_ctx >

[Intel-gfx] ✓ Fi.CI.BAT: success 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 : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_110744v1 Summary ---

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: header cleanups, cont'd

== Series Details == Series: drm/i915: header cleanups, cont'd URL : https://patchwork.freedesktop.org/series/110716/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_110716v1_full Summary ---

Re: [Intel-gfx] [PATCH v8 17/24] drm/probe-helper: Provide a TV get_modes helper

Hi Maxime, On 11/10/22 08:07, Maxime Ripard wrote: > From: Noralf Trønnes > > Most of the TV connectors will need a similar get_modes implementation > that will, depending on the drivers' capabilities, register the 480i and > 576i modes. > > That implementation will also need to set the

Re: [Intel-gfx] [PATCH v8 16/24] drm/modes: Introduce more named modes

Hi Maxime, On 11/10/22 08:07, Maxime Ripard wrote: > Now that we can easily extend the named modes list, let's add a few more > analog TV modes that were used in the wild, and some unit tests to make > sure it works as intended. > > Tested-by: Mateusz Kwiatkowski > Signed-off-by: Maxime Ripard

Re: [Intel-gfx] [PATCH v8 12/24] drm/connector: Add a function to lookup a TV mode by its name

Hi Maxime, On 11/10/22 08:07, Maxime Ripard wrote: > As part of the command line parsing rework coming in the next patches, > we'll need to lookup drm_connector_tv_mode values by their name, already > defined in drm_tv_mode_enum_list. > > In order to avoid any code duplication, let's do a

Re: [Intel-gfx] [PATCH v8 06/24] drm/modes: Add a function to generate analog display modes

Hi Maxime, On 11/10/22 08:07, Maxime Ripard wrote: > Multiple drivers (meson, vc4, sun4i) define analog TV 525-lines and > 625-lines modes in their drivers. > > Since those modes are fairly standard, and that we'll need to use them > in more places in the future, it makes sense to move their

[Intel-gfx] ✗ Fi.CI.SPARSE: warning 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 : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH 6/6] drm/i915: Bpp/timeslot calculation fixes for DP MST DSC

On Thu, Nov 03, 2022 at 03:23:00PM +0200, Stanislav Lisovskiy wrote: > Fix intel_dp_dsc_compute_config, previously timeslots parameter > was used in fact not as a timeslots, but more like a ratio > timeslots/64, which of course didn't have any effect for SST DSC, > but causes now issues for MST

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

== Series Details == Series: drm/i915: Finish (de)gamma readout (rev2) URL : https://patchwork.freedesktop.org/series/79614/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_79614v2 Summary ---

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

== Series Details == Series: drm/i915: Finish (de)gamma readout (rev2) URL : https://patchwork.freedesktop.org/series/79614/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

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

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

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

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_domain_set struct, currently its current > > > size close to 1kB, can be

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

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

Re: [Intel-gfx] [PATCH v6 00/20] drm/i915/vm_bind: Add VM_BIND functionality

On Thu, 2022-11-10 at 15:05 +, Matthew Auld wrote: > On 10/11/2022 14:47, Tvrtko Ursulin wrote: > > > > On 10/11/2022 05:49, Niranjana Vishwanathapura wrote: > > > On Wed, Nov 09, 2022 at 04:16:25PM -0800, Zanoni, Paulo R wrote: > > > > On Mon, 2022-11-07 at 00:51 -0800, Niranjana

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/display: Add missing checks for cdclk crawling

== Series Details == Series: drm/i915/display: Add missing checks for cdclk crawling URL : https://patchwork.freedesktop.org/series/110734/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH v6 05/20] drm/i915/vm_bind: Implement bind and unbind of object

On Thu, 2022-11-10 at 08:32 -0800, Niranjana Vishwanathapura wrote: > On Wed, Nov 09, 2022 at 05:28:59PM -0800, Zanoni, Paulo R wrote: > > On Mon, 2022-11-07 at 00:51 -0800, Niranjana Vishwanathapura wrote: > > > Add uapi and implement support for bind and unbind of an > > > object at the

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

On Wed, Nov 09, 2022 at 09:37:24PM -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

[Intel-gfx] ✓ Fi.CI.BAT: success for linux-next: build failure after merge of the drm-misc tree

== Series Details == Series: linux-next: build failure after merge of the drm-misc tree URL : https://patchwork.freedesktop.org/series/110730/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_110730v1

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: Fix unhandled deadlock in grab_vma()

== Series Details == Series: drm/i915: Fix unhandled deadlock in grab_vma() URL : https://patchwork.freedesktop.org/series/110733/ State : failure == Summary == Error: make failed CALLscripts/checksyscalls.sh DESCEND objtool MODPOST Module.symvers ERROR: modpost:

Re: [Intel-gfx] [PATCH v5 3/9] drm/i915/dp: Replace intel_dp.dfp members with the new crtc_state sink_format

On Fri, Oct 28, 2022 at 03:14:05PM +0530, Ankit Nautiyal wrote: > The decision to use DFP output format conversion capabilities should be > during compute_config phase. > > This patch uses the members of intel_dp->dfp to only store the > format conversion capabilities of the DP device and uses

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for linux-next: build failure after merge of the drm-misc tree

== Series Details == Series: linux-next: build failure after merge of the drm-misc tree URL : https://patchwork.freedesktop.org/series/110730/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2

Re: [Intel-gfx] [PATCH v5 1/9] drm/i915/display: Add new member to configure PCON color conversion

On Fri, Oct 28, 2022 at 03:14:03PM +0530, Ankit Nautiyal wrote: > The decision to use DFP output format conversion capabilities should be > during compute_config phase. > > This patch adds new member to crtc_state to represent the final > output_format to the sink. In case of a DFP this can be

[Intel-gfx] ✓ Fi.CI.BAT: success for Fix timeout handling when retiring requests

== Series Details == Series: Fix timeout handling when retiring requests URL : https://patchwork.freedesktop.org/series/110729/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_110729v1 Summary ---

Re: [Intel-gfx] [PATCH v3 6/6] freezer, sched: Rewrite core freezer logic

On Mon, Nov 07, 2022 at 01:47:23PM +0200, Ville Syrjälä wrote: > On Wed, Nov 02, 2022 at 11:16:48PM +0100, Peter Zijlstra wrote: > > On Wed, Nov 02, 2022 at 06:57:51PM +0200, Ville Syrjälä wrote: > > > On Thu, Oct 27, 2022 at 06:53:23PM +0200, Peter Zijlstra wrote: > > > > On Thu, Oct 27, 2022 at

Re: [Intel-gfx] [PATCH v3 0/7] vfio-ccw parent rework

On Fri, 4 Nov 2022 15:20:00 +0100 Eric Farman wrote: > Hi Alex, > > Here's the (last?) update to the vfio-ccw lifecycle changes that I've sent > recently, and were previously discussed at various points [1][2]. > > Patches 1-5 rework the behavior of the vfio-ccw driver's private struct. > In

[Intel-gfx] [PATCH v1 6/6] fastrpc: Assert held reservation lock for dma-buf mmapping

When userspace mmaps dma-buf's fd, the dma-buf reservation lock must be held. Add locking sanity check to the dma-buf mmaping callback to ensure that the locking assumption won't regress in the future. Suggested-by: Daniel Vetter Signed-off-by: Dmitry Osipenko --- drivers/misc/fastrpc.c | 3

[Intel-gfx] [PATCH v1 4/6] dma-buf/heaps: Assert held reservation lock for dma-buf mmapping

When userspace mmaps dma-buf's fd, the dma-buf reservation lock must be held. Add locking sanity checks to the dma-buf mmaping callbacks to ensure that the locking assumptions won't regress in the future. Suggested-by: Daniel Vetter Signed-off-by: Dmitry Osipenko ---

[Intel-gfx] [PATCH v1 5/6] media: videobuf2: Assert held reservation lock for dma-buf mmapping

When userspace mmaps dma-buf's fd, the dma-buf reservation lock must be held. Add locking sanity checks to the dma-buf mmaping callbacks to ensure that the locking assumptions won't regress in the future. Suggested-by: Daniel Vetter Signed-off-by: Dmitry Osipenko ---

[Intel-gfx] [PATCH v1 3/6] udmabuf: Assert held reservation lock for dma-buf mmapping

When userspace mmaps dma-buf's fd, the dma-buf reservation lock must be held. Add locking sanity check to the dma-buf mmaping callback to ensure that the locking assumption won't regress in the future. Suggested-by: Daniel Vetter Signed-off-by: Dmitry Osipenko --- drivers/dma-buf/udmabuf.c | 3

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

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 Signed-off-by: Dmitry Osipenko ---

[Intel-gfx] [PATCH v1 2/6] drm: Assert held reservation lock for dma-buf mmapping

When userspace mmaps dma-buf's fd, the dma-buf reservation lock must be held. Add locking sanity checks to the dma-buf mmaping callbacks of DRM drivers to ensure that the locking assumptions won't regress in future. Suggested-by: Daniel Vetter Signed-off-by: Dmitry Osipenko ---

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

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 dma_buf_mmap_internal() to the dynamic locking

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/4] drm/i915/hti: abstract hti handling

== Series Details == Series: series starting with [1/4] drm/i915/hti: abstract hti handling URL : https://patchwork.freedesktop.org/series/110712/ State : failure == Summary == CI Bug Log - changes from CI_DRM_12365_full -> Patchwork_110712v1_full

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Fix timeout handling when retiring requests

== Series Details == Series: Fix timeout handling when retiring requests URL : https://patchwork.freedesktop.org/series/110729/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✓ Fi.CI.BAT: success for DRM scheduling cgroup controller (rev2)

== Series Details == Series: DRM scheduling cgroup controller (rev2) URL : https://patchwork.freedesktop.org/series/109902/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_109902v2 Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3)

== Series Details == Series: series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3) URL : https://patchwork.freedesktop.org/series/110646/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_110646v3

[Intel-gfx] ✗ Fi.CI.BUILD: failure for add guard padding around i915_vma

== Series Details == Series: add guard padding around i915_vma URL : https://patchwork.freedesktop.org/series/110720/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/110720/revisions/1/mbox/ not applied Applying: drm/i915: Wrap all access to

[Intel-gfx] ✗ Fi.CI.BUILD: failure for add guard patting around i915_vma

== Series Details == Series: add guard patting around i915_vma URL : https://patchwork.freedesktop.org/series/110719/ State : failure == Summary == Error: patch https://patchwork.freedesktop.org/api/1.0/series/110719/revisions/1/mbox/ not applied Applying: drm/i915: Wrap all access to

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

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_domain_set struct, currently its current > > size close to 1kB, can be allocated on the stack, it's better to > > allocate the per-domain

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: header cleanups, cont'd

== Series Details == Series: drm/i915: header cleanups, cont'd URL : https://patchwork.freedesktop.org/series/110716/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_110716v1 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for DRM scheduling cgroup controller (rev2)

== Series Details == Series: DRM scheduling cgroup controller (rev2) URL : https://patchwork.freedesktop.org/series/109902/ State : warning == Summary == Error: dim checkpatch failed 0529c5855829 drm: Replace DRM_DEBUG with drm_dbg_core in file and ioctl handling 00d2ae726f37 drm: Track

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for DRM scheduling cgroup controller (rev2)

== Series Details == Series: DRM scheduling cgroup controller (rev2) URL : https://patchwork.freedesktop.org/series/109902/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

Re: [Intel-gfx] [PATCH 4/6] drm/i915: Try to use the correct power sequencer intiially on bxt/glk

On Thu, Nov 10, 2022 at 04:41:24PM +0200, Ville Syrjälä wrote: > On Thu, Nov 10, 2022 at 01:56:46PM +, Manna, Animesh wrote: > > > > > > > -Original Message- > > > From: Ville Syrjala > > > Sent: Wednesday, November 9, 2022 4:47 PM > > > To: intel-gfx@lists.freedesktop.org > > > Cc:

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

On Tue, Nov 08, 2022 at 05:18:23PM +0200, Imre Deak wrote: > Since the intel_display_power_domain_set struct, currently its current > size close to 1kB, can be allocated on the stack, it's better to > allocate the per-domain wakeref pointer array - used for debugging - > within the struct

Re: [Intel-gfx] [PATCH 04/10] vfio: Move storage of allow_unsafe_interrupts to vfio_main.c

On Wed, Nov 09, 2022 at 11:28:22AM -0700, Alex Williamson wrote: > > > > I'd be much more comfortable with this as a system wide iommufd flag > > > > if we also tied it to do some demonstration of privilege - eg a > > > > requirement to open iommufd with CAP_SYS_RAWIO for instance. > > > > > >

Re: [Intel-gfx] [PATCH v3 4/9] drm/i915/tgl+: Enable display DC power states on all eDP ports

On Thu, Nov 10, 2022 at 08:57:43PM +0200, Ville Syrjälä wrote: > On Thu, Nov 10, 2022 at 08:52:00PM +0200, Ville Syrjälä wrote: > > On Tue, Nov 08, 2022 at 05:18:25PM +0200, Imre Deak wrote: > > > Starting with TGL eDP is supported on ports B+ (besides port A), so make > > > sure DC states are not

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3)

== Series Details == Series: series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3) URL : https://patchwork.freedesktop.org/series/110646/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3)

== Series Details == Series: series starting with [CI,1/7] drm/i915/huc: only load HuC on GTs that have VCS engines (rev3) URL : https://patchwork.freedesktop.org/series/110646/ State : warning == Summary == Error: dim checkpatch failed be57a55a080f drm/i915/huc: only load HuC on GTs that

Re: [Intel-gfx] [PATCH v3 4/9] drm/i915/tgl+: Enable display DC power states on all eDP ports

On Thu, Nov 10, 2022 at 08:52:00PM +0200, Ville Syrjälä wrote: > On Tue, Nov 08, 2022 at 05:18:25PM +0200, Imre Deak wrote: > > Starting with TGL eDP is supported on ports B+ (besides port A), so make > > sure DC states are not blocked on any such ports. For this add an > > AUX_IO_ power domain

Re: [Intel-gfx] [PATCH v3 4/9] drm/i915/tgl+: Enable display DC power states on all eDP ports

On Tue, Nov 08, 2022 at 05:18:25PM +0200, Imre Deak wrote: > Starting with TGL eDP is supported on ports B+ (besides port A), so make > sure DC states are not blocked on any such ports. For this add an > AUX_IO_ power domain for each port with eDP support. These domains > similarly to AUX_IO_A

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: header cleanups, cont'd

== Series Details == Series: drm/i915: header cleanups, cont'd URL : https://patchwork.freedesktop.org/series/110716/ State : warning == Summary == Error: dim sparse failed Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately.

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: header cleanups, cont'd

== Series Details == Series: drm/i915: header cleanups, cont'd URL : https://patchwork.freedesktop.org/series/110716/ State : warning == Summary == Error: dim checkpatch failed a1c8e7edfaca drm/i915/reg: move masked field helpers to i915_reg_defs.h -:48: CHECK:MACRO_ARG_REUSE: Macro argument

[Intel-gfx] [PATCH] drm/i915/guc: enable GuC GGTT invalidation from the start

Invalidating the GuC TLBs while GuC is not loaded does not have negative consequences, so if we're starting the driver with GuC enabled we can use the GGTT invalidation function from the get-go, iinstead of switching to it when we initialize the GuC objects. In MTL, this fixes and issue where we

Re: [Intel-gfx] [PATCH v2 10/11] vfio: Make vfio_container optionally compiled

On Thu, Nov 10, 2022 at 06:57:57AM +, Tian, Kevin wrote: > > + /* > > +* Emulation for NOIMMU is imperfect in that VFIO blocks almost all > > +* other ioctls. We let them keep working but they mostly fail since no > > +* IOAS should exist. > > +*/ > > + if

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

On Thu, Nov 10, 2022 at 01:28:19PM +0200, Jani Nikula wrote: > On Wed, 09 Nov 2022, 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

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915/hti: abstract hti handling

== Series Details == Series: series starting with [1/4] drm/i915/hti: abstract hti handling URL : https://patchwork.freedesktop.org/series/110712/ State : success == Summary == CI Bug Log - changes from CI_DRM_12365 -> Patchwork_110712v1

[Intel-gfx] [PATCH v3 1/2] i915/uncore: Acquire fw before loop in intel_uncore_read64_2x32

PMU reads the GT timestamp as a 2x32 mmio read and since upper and lower 32 bit registers are read in a loop, there is a latency involved between getting the GT timestamp and the CPU timestamp. As part of the resolution, refactor intel_uncore_read64_2x32 to acquire forcewake and uncore lock prior

[Intel-gfx] [PATCH v3 2/2] drm/i915/selftest: Bump up sample period for busy stats selftest

Engine busyness samples around a 10ms period is failing with busyness ranging approx. from 87% to 115% as shown below. The expected range is +/- 5% of the sample period. Fail 10% of the time. rcs0: reported 11716042ns [91%] busyness while spinning [for 12805719ns] When determining busyness of

[Intel-gfx] [PATCH v3 0/2] Fix live busy stats selftest failure

Fix live busy stats selftest failure in BAT. The issue is seen more easily on DG1 runs. v2: (Tvrtko) In addition refactor intel_uncore_read64_2x32 to obtain the forcewake once before reading upper and lower register dwords. v3: (Ashutosh) Update commit msg Signed-off-by: Umesh Nerlige Ramappa

Re: [Intel-gfx] [PATCH v2 07/11] vfio-iommufd: Support iommufd for physical VFIO devices

On Thu, Nov 10, 2022 at 03:11:16AM +, Tian, Kevin wrote: > > From: Jason Gunthorpe > > Sent: Tuesday, November 8, 2022 8:53 AM > > > > + > > +int vfio_iommufd_bind(struct vfio_device *vdev, struct iommufd_ctx *ictx) > > +{ > > + u32 ioas_id; > > + u32 device_id; > > + int ret; > > + >

Re: [Intel-gfx] [PATCH v2 10/11] vfio: Make vfio_container optionally compiled

On Thu, 10 Nov 2022 06:57:57 + "Tian, Kevin" wrote: > > From: Jason Gunthorpe > > Sent: Thursday, November 10, 2022 3:53 AM > > > > On Wed, Nov 09, 2022 at 10:18:09AM -0700, Alex Williamson wrote: > > > > > DPDK supports no-iommu mode. > > > > Er? Huh? How? I thought no-iommu was for

[Intel-gfx] ✗ Fi.CI.DOCS: warning for series starting with [1/4] drm/i915/hti: abstract hti handling

== Series Details == Series: series starting with [1/4] drm/i915/hti: abstract hti handling URL : https://patchwork.freedesktop.org/series/110712/ State : warning == Summary == Error: make htmldocs had i915 warnings ./drivers/gpu/drm/i915/i915_perf_types.h:319: warning: Function parameter or

  1   2   >