[Intel-gfx] ✗ Fi.CI.BAT: failure for pcm_lock deadlock

== Series Details == Series: pcm_lock deadlock URL : https://patchwork.freedesktop.org/series/68742/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7221 -> Patchwork_15064 Summary --- **FAILURE** Serious unknown ch

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for tgl: MST support

== Series Details == Series: tgl: MST support URL : https://patchwork.freedesktop.org/series/68749/ State : warning == Summary == $ dim checkpatch origin/drm-tip dd2dcb37cff0 drm/i915: Add for_each_new_intel_connector_in_state() -:26: ERROR:COMPLEX_MACRO: Macros with complex values should be e

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for tgl: MST support

== Series Details == Series: tgl: MST support URL : https://patchwork.freedesktop.org/series/68749/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.6.0 Commit: drm/i915: Add for_each_new_intel_connector_in_state() Okay! Commit: drm/i915: add wrappers to get intel

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Defer engine registration until fully initialised

== Series Details == Series: drm/i915/gt: Defer engine registration until fully initialised URL : https://patchwork.freedesktop.org/series/68746/ State : success == Summary == CI Bug Log - changes from CI_DRM_7221 -> Patchwork_15065 Summary

[Intel-gfx] ✓ Fi.CI.BAT: success for tgl: MST support

== Series Details == Series: tgl: MST support URL : https://patchwork.freedesktop.org/series/68749/ State : success == Summary == CI Bug Log - changes from CI_DRM_7221 -> Patchwork_15066 Summary --- **SUCCESS** No regressions foun

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [RFC,1/2] drm/i915: add display uncore helpers

== Series Details == Series: series starting with [RFC,1/2] drm/i915: add display uncore helpers URL : https://patchwork.freedesktop.org/series/68713/ State : success == Summary == CI Bug Log - changes from CI_DRM_7211_full -> Patchwork_15049_full ==

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Nuke 'mode' argument to intel_get_load_detect_pipe()

== Series Details == Series: drm/i915: Nuke 'mode' argument to intel_get_load_detect_pipe() URL : https://patchwork.freedesktop.org/series/68717/ State : success == Summary == CI Bug Log - changes from CI_DRM_7211_full -> Patchwork_15050_full ===

Re: [Intel-gfx] [RFC 0/3] Display uncore

On Tue, 29 Oct 2019, Daniele Ceraolo Spurio wrote: > On 10/29/19 2:23 AM, Jani Nikula wrote: >> On Wed, 07 Aug 2019, Daniele Ceraolo Spurio >> wrote: >>> I've been trying to identify MMIO ranges to clearly define what belongs >>> to display_uncore to do a check on access, but there are lots of

[Intel-gfx] [PATCH V6 0/6] mdev based hardware virtio offloading support

Hi all: There are hardwares that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and re

[Intel-gfx] [PATCH V6 1/6] mdev: class id support

Mdev bus only supports vfio driver right now, so it doesn't implement match method. But in the future, we may add drivers other than vfio, the first driver could be virtio-mdev. This means we need to add device class id support in bus match method to pair the mdev device and mdev driver correctly.

[Intel-gfx] [PATCH V6 2/6] modpost: add support for mdev class id

Add support to parse mdev class id table. Reviewed-by: Parav Pandit Signed-off-by: Jason Wang --- drivers/vfio/mdev/vfio_mdev.c | 2 ++ scripts/mod/devicetable-offsets.c | 3 +++ scripts/mod/file2alias.c | 11 +++ 3 files changed, 16 insertions(+) diff --git a/drivers/vf

[Intel-gfx] [PATCH V6 3/6] mdev: introduce device specific ops

Currently, except for the create and remove, the rest of mdev_parent_ops is designed for vfio-mdev driver only and may not help for kernel mdev driver. With the help of class id, this patch introduces device specific callbacks inside mdev_device structure. This allows different set of callback to b

[Intel-gfx] [PATCH V6 4/6] mdev: introduce virtio device and its device ops

This patch implements basic support for mdev driver that supports virtio transport for kernel virtio driver. Signed-off-by: Jason Wang --- drivers/vfio/mdev/mdev_core.c| 20 drivers/vfio/mdev/mdev_private.h | 2 + include/linux/mdev.h | 6 ++ include/linux/virtio_mdev_o

[Intel-gfx] [PATCH V6 5/6] virtio: introduce a mdev based transport

This patch introduces a new mdev transport for virtio. This is used to use kernel virtio driver to drive the mediated device that is capable of populating virtqueue directly. A new virtio-mdev driver will be registered to the mdev bus, when a new virtio-mdev device is probed, it will register the

[Intel-gfx] [PATCH V6 6/6] docs: sample driver to demonstrate how to implement virtio-mdev framework

This sample driver creates mdev device that simulate virtio net device over virtio mdev transport. The device is implemented through vringh and workqueue. A device specific dma ops is to make sure HVA is used directly as the IOVA. This should be sufficient for kernel virtio driver to work. Only 'v

<    1   2   3