[Intel-gfx] [PULL] drm-intel-fixes

2021-05-13 Thread Jani Nikula
Hi Dave & Daniel - Sorry, late due to public holidays. drm-intel-fixes-2021-05-14: drm/i915 fixes for v5.13-rc2: - Fix active callback alignment annotations and subsequent crashes - Retract link training strategy to slow and wide, again - Avoid division by zero on gen2 - Use correct width reads

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/4] drm/i915/display: Nuke has_infoframe

2021-05-13 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm/i915/display: Nuke has_infoframe URL : https://patchwork.freedesktop.org/series/90149/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20124 Summa

Re: [Intel-gfx] [PATCH 0/7] Per client engine busyness

2021-05-13 Thread Alex Deucher
+ David, Christian On Thu, May 13, 2021 at 12:41 PM Tvrtko Ursulin wrote: > > > Hi, > > On 13/05/2021 16:48, Alex Deucher wrote: > > On Thu, May 13, 2021 at 7:00 AM Tvrtko Ursulin > > wrote: > >> > >> From: Tvrtko Ursulin > >> > >> Resurrect of the previosuly merged per client engine busyness p

Re: [Intel-gfx] [PATCH] drm/i915: Fix a possible use of uninitialized variable in remap_io_sg()

2021-05-13 Thread Christoph Hellwig
On Thu, May 13, 2021 at 04:28:41PM -0700, José Roberto de Souza wrote: > If the do while loop breaks in 'if (!sg_dma_len(sgl))' in the first > iteration, err is uninitialized causing a wrong call to zap_vma_ptes(). But scatterlist must have at least one valid segment. So while the patch looks ok,

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/display: Nuke has_infoframe

2021-05-13 Thread Patchwork
== Series Details == Series: series starting with [1/4] drm/i915/display: Nuke has_infoframe URL : https://patchwork.freedesktop.org/series/90149/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. +d

[Intel-gfx] [PATCH 4/4] drm/i915/display: Fix fastsets involving PSR

2021-05-13 Thread José Roberto de Souza
Commit 78b772e1a01f ("drm/i915/display: Fill PSR state during hardware configuration read out") is not allowing fastsets to happen when PSR states changes but PSR is a feature that can be enabled and disabled during fastsets. So here moving the PSR pipe conf checks to a block that is only executed

[Intel-gfx] [PATCH 2/4] drm/i915/display: Replace intel_dp_set_infoframes() disable calls by dig_port->set_infoframes()

2021-05-13 Thread José Roberto de Souza
Both do the same thing and this change help towards the goal of nuke intel_dp_set_infoframes() completely. Cc: Ville Syrjälä Signed-off-by: José Roberto de Souza --- drivers/gpu/drm/i915/display/intel_ddi.c| 5 ++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 5 +++-- 2 files changed, 5

[Intel-gfx] [PATCH 3/4] drm/i915/display: Replace intel_dp_set_infoframes() enable calls by dig_port->set_infoframes()

2021-05-13 Thread José Roberto de Souza
intel_dp_set_infoframes() and set_infoframes() hook had some code overlapping that makes sense us try to drop it. set_infoframes() is called during the pre_enable phase while intel_dp_set_infoframes() was being called in the enable phase but it was only enabling DP_SDP_VSC and HDMI_PACKET_TYPE_GAM

[Intel-gfx] [PATCH 1/4] drm/i915/display: Nuke has_infoframe

2021-05-13 Thread José Roberto de Souza
This was only reduntant information has_hdmi_sink can do the same job. set_infoframes() hooks will call intel_write_infoframe() for the supported infoframes types and it will only be enabled if given type is set in crtc_state->infoframes.enable. Cc: Ville Syrjälä Signed-off-by: José Roberto de So

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix a possible use of uninitialized variable in remap_io_sg()

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915: Fix a possible use of uninitialized variable in remap_io_sg() URL : https://patchwork.freedesktop.org/series/90142/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20123_full =

Re: [Intel-gfx] linux-next: manual merge of the drm-intel tree with the drm tree

2021-05-13 Thread Stephen Rothwell
Hi all, On Fri, 30 Apr 2021 08:23:21 +1000 Stephen Rothwell wrote: > > On Thu, 18 Mar 2021 12:52:41 +1100 Stephen Rothwell > wrote: > > > > On Wed, 17 Mar 2021 14:08:24 +1100 Stephen Rothwell > > wrote: > > > > > > Today's linux-next merge of the drm-intel tree got a conflict in: > > > >

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix a possible use of uninitialized variable in remap_io_sg()

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915: Fix a possible use of uninitialized variable in remap_io_sg() URL : https://patchwork.freedesktop.org/series/90142/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20123 ===

[Intel-gfx] [PATCH] drm/i915: Fix a possible use of uninitialized variable in remap_io_sg()

2021-05-13 Thread José Roberto de Souza
If the do while loop breaks in 'if (!sg_dma_len(sgl))' in the first iteration, err is uninitialized causing a wrong call to zap_vma_ptes(). Fixes: b12d691ea5e0 ("i915: fix remap_io_sg to verify the pgprot") Cc: Christoph Hellwig Signed-off-by: James Ausmus Signed-off-by: José Roberto de Souza -

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4 URL : https://patchwork.freedesktop.org/series/90102/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20115_full ===

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/jsl: Add W/A 1409054076 for JSL (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL (rev2) URL : https://patchwork.freedesktop.org/series/90129/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20122_full Summary ---

Re: [Intel-gfx] [PATCH v3 11/48] drm/i915: Get slice height before computing rc params

2021-05-13 Thread Navare, Manasi
On Fri, May 07, 2021 at 07:27:43PM -0700, Matt Roper wrote: > From: Vandita Kulkarni > > We need slice height to calculate few RC parameters > hence assign slice height first. > > Cc: Manasi Navare > Signed-off-by: Vandita Kulkarni > Signed-off-by: Matt Roper Reviewed-by: Manasi Navare Man

Re: [Intel-gfx] [PATCH v3 10/48] drm/i915/xelpd: Support DP1.4 compression BPPs

2021-05-13 Thread Navare, Manasi
On Fri, May 07, 2021 at 07:27:42PM -0700, Matt Roper wrote: > From: Vandita Kulkarni > > Support compression BPPs from bpc to uncompressed BPP -1. > So far we have 8,10,12 as valid compressed BPPS now the > support is extended. > > Cc: Manasi Navare > Signed-off-by: Vandita Kulkarni > Signed-o

Re: [Intel-gfx] [PATCH v3 41/48] drm/i915/bigjoiner: atomic commit changes for uncompressed joiner

2021-05-13 Thread Navare, Manasi
On Fri, May 07, 2021 at 07:28:13PM -0700, Matt Roper wrote: > From: Animesh Manna > > Respective bit for master or slave to be set for uncompressed > bigjoiner in dss_ctl1 register. > > Cc: Manasi Navare > Signed-off-by: Animesh Manna > Signed-off-by: Clinton Taylor > Signed-off-by: Matt Rope

Re: [Intel-gfx] [PATCH v3 40/48] drm/i915/bigjoiner: Avoid dsc_compute_config for uncompressed bigjoiner

2021-05-13 Thread Navare, Manasi
On Fri, May 07, 2021 at 07:28:12PM -0700, Matt Roper wrote: > From: Animesh Manna > > For uncompressed big joiner DSC engine will not be used so will avoid > compute config of DSC. > > Cc: Manasi Navare > Signed-off-by: Animesh Manna > Signed-off-by: Clinton Taylor > Signed-off-by: Matt Roper

Re: [Intel-gfx] [PATCH v3 39/48] drm/i915/bigjoiner: Mode validation with uncompressed pipe joiner

2021-05-13 Thread Navare, Manasi
On Fri, May 07, 2021 at 07:28:11PM -0700, Matt Roper wrote: > From: Animesh Manna > > No need for checking dsc flag for uncompressed pipe joiner mode > validation. > > Cc: Manasi Navare > Signed-off-by: Animesh Manna > Signed-off-by: Clinton Taylor > Signed-off-by: Matt Roper Reviewed-by: M

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gem: Pin the L-shape quirked object as unshrinkable (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/gem: Pin the L-shape quirked object as unshrinkable (rev2) URL : https://patchwork.freedesktop.org/series/90065/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20121_full =

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4

2021-05-13 Thread Vudum, Lakshminarayana
Re-reported. -Original Message- From: Deak, Imre Sent: Wednesday, May 12, 2021 3:46 PM To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana Subject: Re: ✗ Fi.CI.BAT: failure for drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4 Hi Lakshmi, On Wed, May 12, 2021

Re: [Intel-gfx] [PATCH 0/7] Per client engine busyness

2021-05-13 Thread Tvrtko Ursulin
Hi, On 13/05/2021 16:48, Alex Deucher wrote: On Thu, May 13, 2021 at 7:00 AM Tvrtko Ursulin wrote: From: Tvrtko Ursulin Resurrect of the previosuly merged per client engine busyness patches. In a nutshell it enables intel_gpu_top to be more top(1) like useful and show not only physical GPU

[Intel-gfx] ✗ Fi.CI.IGT: failure for Per client engine busyness

2021-05-13 Thread Patchwork
== Series Details == Series: Per client engine busyness URL : https://patchwork.freedesktop.org/series/90128/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20118_full Summary --- **FAILURE**

Re: [Intel-gfx] [PATCH v2 1/1] drm/dp_mst: Use kHz as link rate units when settig source max link caps at init

2021-05-13 Thread Lyude Paul
Reviewed-by: Lyude Paul Will let this sit on the list for a few days to see if anyone's got any objections and then I'll go ahead and push it On Wed, 2021-05-12 at 17:00 -0400, Nikola Cornij wrote: > [why] > Link rate in kHz is what is eventually required to calculate the link > bandwidth, which

Re: [Intel-gfx] [PATCH 0/7] Per client engine busyness

2021-05-13 Thread Alex Deucher
On Thu, May 13, 2021 at 7:00 AM Tvrtko Ursulin wrote: > > From: Tvrtko Ursulin > > Resurrect of the previosuly merged per client engine busyness patches. In a > nutshell it enables intel_gpu_top to be more top(1) like useful and show not > only physical GPU engine usage but per process view as we

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915: Reenable LTTPR non-transparent LT mode for DPCD_REV<1.4 URL : https://patchwork.freedesktop.org/series/90102/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20115 Sum

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/jsl: Add W/A 1409054076 for JSL (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL (rev2) URL : https://patchwork.freedesktop.org/series/90129/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20122 Summary --- **

[Intel-gfx] [PULL] drm-misc-fixes

2021-05-13 Thread Maxime Ripard
Hi Dave, Daniel, Here's the first round of drm-misc-fixes for 5.13 Maxime drm-misc-fixes-2021-05-13: A BO list maintainance fix for TTM, removing an unused function and a MAINTAINERS update. The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5: Linux 5.13-rc1 (2021-05-0

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/jsl: Add W/A 1409054076 for JSL (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL (rev2) URL : https://patchwork.freedesktop.org/series/90129/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. +drivers/gpu/drm/i

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/jsl: Add W/A 1409054076 for JSL (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL (rev2) URL : https://patchwork.freedesktop.org/series/90129/ State : warning == Summary == $ dim checkpatch origin/drm-tip b258ec7f5e7f drm/i915/jsl: Add W/A 1409054076 for JSL -:61: CHECK:LINE_SPACING: Please don't use mult

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix "mitigations" parsing if i915 is builtin (rev4)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915: Fix "mitigations" parsing if i915 is builtin (rev4) URL : https://patchwork.freedesktop.org/series/88998/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10074_full -> Patchwork_20117_full ===

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gem: Pin the L-shape quirked object as unshrinkable (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/gem: Pin the L-shape quirked object as unshrinkable (rev2) URL : https://patchwork.freedesktop.org/series/90065/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20121 S

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/jsl: Add W/A 1409054076 for JSL

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL URL : https://patchwork.freedesktop.org/series/90129/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20119 Summary --- **WARNING

[Intel-gfx] [PATCH V2] drm/i915/jsl: Add W/A 1409054076 for JSL

2021-05-13 Thread Tejas Upadhyay
When pipe A is disabled and MIPI DSI is enabled on pipe B, the AMT KVMR feature will incorrectly see pipe A as enabled. Set 0x42080 bit 23=1 before enabling DSI on pipe B and leave it set while DSI is enabled on pipe B. No impact to setting it all the time. Changes since V1: - ./dim checkp

[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gt: Disable HiZ Raw Stall Optimization on broken gen7 (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/gt: Disable HiZ Raw Stall Optimization on broken gen7 (rev2) URL : https://patchwork.freedesktop.org/series/89502/ State : failure == Summary == Applying: drm/i915/gt: Disable HiZ Raw Stall Optimization on broken gen7 error: corrupt patch at line 16 error:

[Intel-gfx] [PATCH v2] drm/i915/gem: Pin the L-shape quirked object as unshrinkable

2021-05-13 Thread Matthew Auld
From: Chris Wilson When instantiating a tiled object on an L-shaped memory machine, we mark the object as unshrinkable to prevent the shrinker from trying to swap out the pages. We have to do this as we do not know the swizzling on the individual pages, and so the data will be scrambled across sw

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/jsl: Add W/A 1409054076 for JSL

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL URL : https://patchwork.freedesktop.org/series/90129/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. +drivers/gpu/drm/i915/dis

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/jsl: Add W/A 1409054076 for JSL

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915/jsl: Add W/A 1409054076 for JSL URL : https://patchwork.freedesktop.org/series/90129/ State : warning == Summary == $ dim checkpatch origin/drm-tip 816593a3ccd4 drm/i915/jsl: Add W/A 1409054076 for JSL -:23: CHECK:PARENTHESIS_ALIGNMENT: Alignment should ma

[Intel-gfx] ✓ Fi.CI.BAT: success for Per client engine busyness

2021-05-13 Thread Patchwork
== Series Details == Series: Per client engine busyness URL : https://patchwork.freedesktop.org/series/90128/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20118 Summary --- **WARNING** Minor un

Re: [Intel-gfx] [PATCH] drm/i915: Fix wrong name announced on FB driver switching

2021-05-13 Thread Janusz Krzysztofik
Hi Jani, On Mon, 3 May 2021 19:38:17 CEST Jani Nikula wrote: > On Thu, 29 Apr 2021, Janusz Krzysztofik wrote: > > Commit 7a0f9ef9703d ("drm/i915: Use drm_fb_helper_fill_info") > > effectively changed our FB driver name from "inteldrmfb" to > > "i915drmfb". However, we are still using the old na

Re: [Intel-gfx] [PATCH] drm/i915/gt: Disable HiZ Raw Stall Optimization on broken gen7

2021-05-13 Thread Rodrigo Vivi
On Thu, May 13, 2021 at 10:18:49AM +1000, Dave Airlie wrote: > Reviewed-by: Dave Airlie > > Can we get this fix in, having a regression spanning 3 kernels isn't a > good look, we can work out why it matters later in life if anyone > cares. Agreed and pushed do drm-intel-next. This triggered me

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Per client engine busyness

2021-05-13 Thread Patchwork
== Series Details == Series: Per client engine busyness URL : https://patchwork.freedesktop.org/series/90128/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/i915/display/intel_d

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Per client engine busyness

2021-05-13 Thread Patchwork
== Series Details == Series: Per client engine busyness URL : https://patchwork.freedesktop.org/series/90128/ State : warning == Summary == $ dim checkpatch origin/drm-tip 289c10899f79 drm/i915: Expose list of clients in sysfs -:89: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), d

[Intel-gfx] [PATCH] drm/i915/jsl: Add W/A 1409054076 for JSL

2021-05-13 Thread Tejas Upadhyay
When pipe A is disabled and MIPI DSI is enabled on pipe B, the AMT KVMR feature will incorrectly see pipe A as enabled. Set 0x42080 bit 23=1 before enabling DSI on pipe B and leave it set while DSI is enabled on pipe B. No impact to setting it all the time. Signed-off-by: Tejas Upadhyay --- driv

[Intel-gfx] [PATCH 7/7] drm/i915: Expose per-engine client busyness

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Expose per-client and per-engine busyness under the previously added sysfs client root. The new files are one per-engine instance and located under the 'busy' directory. Each contains a monotonically increasing nano-second resolution times each client's jobs were executing o

[Intel-gfx] [PATCH 6/7] drm/i915: Track context current active time

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Track context active (on hardware) status together with the start timestamp. This will be used to provide better granularity of context runtime reporting in conjunction with already tracked pphwsp accumulated runtime. The latter is only updated on context save so does not g

[Intel-gfx] [PATCH 4/7] drm/i915: Track runtime spent in closed and unreachable GEM contexts

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin As contexts are abandoned we want to remember how much GPU time they used (per class) so later we can used it for smarter purposes. As GEM contexts are closed we want to have the DRM client remember how much GPU time they used (per class) so later we can used it for smarter

[Intel-gfx] [PATCH 5/7] drm/i915: Track all user contexts per client

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin We soon want to start answering questions like how much GPU time is the context belonging to a client which exited still using. To enable this we start tracking all context belonging to a client on a separate list. Signed-off-by: Tvrtko Ursulin Reviewed-by: Aravind Iddamse

[Intel-gfx] [PATCH 3/7] drm/i915: Make GEM contexts track DRM clients

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin If we make GEM contexts keep a reference to i915_drm_client for the whole of their lifetime, we can consolidate the current task pid and name usage by getting it from the client. v2: Don't bother supporting selftests contexts from debugfs. (Chris) v3 (Lucas): Finish construc

[Intel-gfx] [PATCH 2/7] drm/i915: Update client name on context create

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Some clients have the DRM fd passed to them over a socket by the X server. Grab the real client and pid when they create their first context and update the exposed data for more useful enumeration. To enable lockless access to client name and pid data from the following pat

[Intel-gfx] [PATCH 0/7] Per client engine busyness

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Resurrect of the previosuly merged per client engine busyness patches. In a nutshell it enables intel_gpu_top to be more top(1) like useful and show not only physical GPU engine usage but per process view as well. Example screen capture: ~

[Intel-gfx] [PATCH 1/7] drm/i915: Expose list of clients in sysfs

2021-05-13 Thread Tvrtko Ursulin
From: Tvrtko Ursulin Expose a list of clients with open file handles in sysfs. This will be a basis for a top-like utility showing per-client and per- engine GPU load. Currently we only expose each client's pid and name under opaque numbered directories in /sys/class/drm/card0/clients/. For in

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix "mitigations" parsing if i915 is builtin (rev4)

2021-05-13 Thread Patchwork
== Series Details == Series: drm/i915: Fix "mitigations" parsing if i915 is builtin (rev4) URL : https://patchwork.freedesktop.org/series/88998/ State : success == Summary == CI Bug Log - changes from CI_DRM_10074 -> Patchwork_20117 Summary

[Intel-gfx] ✗ Fi.CI.BUILD: failure for Fix I915_GVT dependency (rev2)

2021-05-13 Thread Patchwork
== Series Details == Series: Fix I915_GVT dependency (rev2) URL : https://patchwork.freedesktop.org/series/89996/ State : failure == Summary == Applying: drm/i915/gvt: Move mdev attribute groups into kvmgt module Applying: Revert "vfio/gvt: fix DRM_I915_GVT dependency on VFIO_MDEV" Using index

[Intel-gfx] [PATCH V3 RESEND] drm/i915: Fix "mitigations" parsing if i915 is builtin

2021-05-13 Thread Jisheng Zhang
I met below error during boot with i915 builtin if pass "i915.mitigations=off": [0.015589] Booting kernel: `off' invalid for parameter `i915.mitigations' The reason is slab subsystem isn't ready at that time, so kstrdup() returns NULL. Fix this issue by using stack var instead of kstrdup(). F

[Intel-gfx] [PATCH v2] drm/i915/gvt: Move mdev attribute groups into kvmgt module

2021-05-13 Thread Zhenyu Wang
As kvmgt module contains all handling for VFIO/mdev, leaving mdev attribute groups in gvt module caused dependency issue. Although it was there for possible other hypervisor usage, that turns out never to be true. So this moves all mdev handling into kvmgt module completely to resolve dependency is