On Wed, Jun 22, 2022 at 06:54:49PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> On g4x/vlv/chv the hardware seems incapable of changing the pixel
> format, rotation, or YUV->RGB CSC matrix while in CxSR.
>
> Additionally on VLV/CHV the sprites seem incapable of tiling
> changes while
== Series Details ==
Series: Simplify uncore register updates (rev2)
URL : https://patchwork.freedesktop.org/series/109374/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_1_full -> Patchwork_109374v2_full
Summary
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: enable PS64 support for DG2
(rev2)
URL : https://patchwork.freedesktop.org/series/109384/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_1_full -> Patchwork_109384v2_full
Greg KH 于2022年10月7日周五 03:22写道：
>
> On Fri, Oct 07, 2022 at 12:58:45AM +0800, Zheng Wang wrote:
> > If intel_gvt_dma_map_guest_page failed, it will call
> > ppgtt_invalidate_spt, which will finally free the spt.
> > But the caller does not notice that, it will free spt again in error path.
> >
> >
== Series Details ==
Series: drm/i915: Allow panel fixed modes to have differing sync polarities
URL : https://patchwork.freedesktop.org/series/109467/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_109467v1
== Series Details ==
Series: Delay disabling GuC scheduling of an idle context
URL : https://patchwork.freedesktop.org/series/109466/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_109466v1
Summary
On 10/6/2022 15:51, Alan Previn wrote:
With the introduction of the delayed disable-sched behavior,
we use the GuC's xarray of valid guc-id's as a way to
identify if new requests had been added to a context
when the said context is being checked for closure.
Additionally that prior change also
On 10/6/2022 15:51, Alan Previn wrote:
From: Matthew Brost
Add a delay, configurable via debugfs (default 34ms), to disable
scheduling of a context after the pin count goes to zero. Disable
scheduling is a costly operation as it requires synchronizing with
the GuC. So the idea is that a delay
== Series Details ==
Series: Delay disabling GuC scheduling of an idle context
URL : https://patchwork.freedesktop.org/series/109466/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/edid/firmware: stop using throwaway platform device
URL : https://patchwork.freedesktop.org/series/109464/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_109464v1
Summary
== Series Details ==
Series: drm/edid/firmware: stop using throwaway platform device
URL : https://patchwork.freedesktop.org/series/109464/
State : warning
== Summary ==
Error: dim checkpatch failed
88cfbbf5d352 drm/edid/firmware: stop using throwaway platform device
-:19:
On Tue, Oct 4, 2022 at 10:38 AM Jani Nikula wrote:
> Got any bug report with more info, or any other details to back this up?
> This is kind of thin. What's the 800 ms based on?
This issue affected several different CometLake-based Chrome OS device
designs. The details of the original report are
From: Ville Syrjälä
Apparently some panels declare multiple modes with random
sync polarities. Seems a bit weird, but looks like Windows/GOP
doesn't care, so let follow suit and accept alternate fixed
modes regardless of their sync polarities.
Closes:
From: Matthew Brost
Add a delay, configurable via debugfs (default 34ms), to disable
scheduling of a context after the pin count goes to zero. Disable
scheduling is a costly operation as it requires synchronizing with
the GuC. So the idea is that a delay allows the user to resubmit
something
With the introduction of the delayed disable-sched behavior,
we use the GuC's xarray of valid guc-id's as a way to
identify if new requests had been added to a context
when the said context is being checked for closure.
Additionally that prior change also closes the race for when
a new incoming
This series adds a delay before disabling scheduling of the guc-context
when a context has become idle to avoid costly re-registration that may
occur immediately after. The 2nd patch should explain it quite well.
The origin of this series was posted by Matthew Brost back in Oct 2021
On Wed, 2022-10-05 at 23:02 -0700, Alan Previn wrote:
> -static inline bool context_has_committed_requests(struct intel_context *ce)
> -{
> - return !!ce->guc_state.number_committed_requests;
> -}
> -
Offline conversation with John Harrison and team matest concluded we dont even
need
the
We've used a temporary platform device for firmware EDID loading since
it was introduced in commit da0df92b5731 ("drm: allow loading an EDID as
firmware to override broken monitor"), but there's no explanation why.
Do we need to?
Maybe this fixes the suspend/resume issue?
(Yes, I'll rewrite the
== Series Details ==
Series: Improve anti-pre-emption w/a for compute workloads (rev8)
URL : https://patchwork.freedesktop.org/series/100428/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_100428v8
== Series Details ==
Series: Improve anti-pre-emption w/a for compute workloads (rev8)
URL : https://patchwork.freedesktop.org/series/100428/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: Improve anti-pre-emption w/a for compute workloads (rev8)
URL : https://patchwork.freedesktop.org/series/100428/
State : warning
== Summary ==
Error: dim checkpatch failed
e700b8ded220 drm/i915/guc: Limit scheduling properties to avoid overflow
-:45:
== Series Details ==
Series: Simplify uncore register updates (rev3)
URL : https://patchwork.freedesktop.org/series/109374/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_109374v3
Summary
---
From: John Harrison
A workaround was added to the driver to allow compute workloads to run
'forever' by disabling pre-emption on the RCS engine for Gen12.
It is not totally unbound as the heartbeat will kick in eventually
and cause a reset of the hung engine.
However, this does not work well in
From: John Harrison
An earlier patch added support for compute engines. However, it missed
enabling the anti-pre-emption w/a for the new engine class. So move
the 'compute capable' flag earlier and use it for the pre-emption w/a
test.
Fixes: c674c5b9342e ("drm/i915/xehp: CCS should use RCS
From: John Harrison
Compute workloads are inherently not pre-emptible for long periods on
current hardware. As a workaround for this, the pre-emption timeout
for compute capable engines was disabled. This is undesirable with GuC
submission as it prevents per engine reset of hung contexts. Hence
From: John Harrison
GuC converts the pre-emption timeout and timeslice quantum values into
clock ticks internally. That significantly reduces the point of 32bit
overflow. On current platforms, worst case scenario is approximately
110 seconds. Rather than allowing the user to set higher values
From: John Harrison
Compute workloads are inherently not pre-emptible on current hardware.
Thus the pre-emption timeout was disabled as a workaround to prevent
unwanted resets. Instead, the hang detection was left to the heartbeat
and its (longer) timeout. This is undesirable with GuC submission
== Series Details ==
Series: Simplify uncore register updates (rev3)
URL : https://patchwork.freedesktop.org/series/109374/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Wed, Oct 05, 2022 at 08:59:43AM -0700, Vinay Belgaumkar wrote:
> Read the values stored in the SLPC structures. Remove the
> fields that are no longer valid (like RPS interrupts) as
> well.
>
> v2: Move all functionality changes to this patch (Jani)
> v3: Fix compile warning and if condition
== Series Details ==
Series: drm/display: Don't assume dual mode adaptors support i2c sub-addressing
(rev3)
URL : https://patchwork.freedesktop.org/series/109049/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_109049v3
== Series Details ==
Series: Delay disabling GuC scheduling of an idle context
URL : https://patchwork.freedesktop.org/series/109442/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12221_full -> Patchwork_109442v1_full
drm_device pointers are unwelcome.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/i915/display/icl_dsi.c| 9 ++--
drivers/gpu/drm/i915/display/intel_display.c | 9 ++--
.../drm/i915/display/intel_display_debugfs.c | 51 ---
On 10/6/2022 13:16, Ceraolo Spurio, Daniele wrote:
On 10/6/2022 1:09 PM, John Harrison wrote:
On 10/6/2022 10:20, Daniele Ceraolo Spurio wrote:
We're observing sporadic HuC delayed load timeouts in CI, due to
mei_pxp
binding completing later than we expected. HuC is still still loaded
still
On 10/6/2022 1:09 PM, John Harrison wrote:
On 10/6/2022 10:20, Daniele Ceraolo Spurio wrote:
We're observing sporadic HuC delayed load timeouts in CI, due to mei_pxp
binding completing later than we expected. HuC is still still loaded
still still
when the bind occurs, but in the meantime
On 10/6/2022 10:20, Daniele Ceraolo Spurio wrote:
We're observing sporadic HuC delayed load timeouts in CI, due to mei_pxp
binding completing later than we expected. HuC is still still loaded
still still
when the bind occurs, but in the meantime i915 has started allowing
submission to the VCS
== Series Details ==
Series: Fix Guc-Err-Capture sizing warning
URL : https://patchwork.freedesktop.org/series/109439/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12221_full -> Patchwork_109439v1_full
Summary
---
On Thu, Oct 06, 2022 at 12:01:17AM +0300, Imre Deak wrote:
> On Wed, Oct 05, 2022 at 10:14:43PM +0300, Ville Syrjälä wrote:
> > On Wed, Oct 05, 2022 at 08:52:51PM +0300, Imre Deak wrote:
> > > The GPU reset involves a display suspend/resume sequence, but this is
> > > done without
On Fri, Oct 07, 2022 at 12:58:45AM +0800, Zheng Wang wrote:
> If intel_gvt_dma_map_guest_page failed, it will call
> ppgtt_invalidate_spt, which will finally free the spt.
> But the caller does not notice that, it will free spt again in error path.
>
> Fix this by spliting invalidate and free in
== Series Details ==
Series: drm/i915/huc: bump timeout for delayed load and reduce print verbosity
URL : https://patchwork.freedesktop.org/series/109455/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12223 -> Patchwork_109455v1
On 10/5/2022 22:31, Alan Previn wrote:
During GuC error capture initialization, we estimate the amount of size
we need for the error-capture-region of the shared GuC-log-buffer.
This calculation was incorrect so fix that. With the fixed calculation
we can reduce the allocation of error-capture
On Thu, 6 Oct 2022 08:37:09 -0300
Jason Gunthorpe wrote:
> On Wed, Oct 05, 2022 at 04:03:56PM -0600, Alex Williamson wrote:
> > We can't have a .remove callback that does nothing, this breaks
> > removing the device while it's in use. Once we have the
> > vfio_unregister_group_dev() fix below,
== Series Details ==
Series: drm/i915/huc: bump timeout for delayed load and reduce print verbosity
URL : https://patchwork.freedesktop.org/series/109455/
State : warning
== Summary ==
Error: dim checkpatch failed
423e7c295e41 drm/i915/huc: bump timeout for delayed load and reduce print
== Series Details ==
Series: drm/i915/pxp: Prepare intel_pxp entry points for MTL (rev2)
URL : https://patchwork.freedesktop.org/series/109429/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12221_full -> Patchwork_109429v2_full
We're observing sporadic HuC delayed load timeouts in CI, due to mei_pxp
binding completing later than we expected. HuC is still still loaded
when the bind occurs, but in the meantime i915 has started allowing
submission to the VCS engines even if HuC is not there.
In most of the cases I've
== Series Details ==
Series: Simplify uncore register updates (rev2)
URL : https://patchwork.freedesktop.org/series/109374/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_1 -> Patchwork_109374v2
Summary
---
== Series Details ==
Series: Simplify uncore register updates (rev2)
URL : https://patchwork.freedesktop.org/series/109374/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
On Thu, Oct 06, 2022 at 06:31:57PM +0200, Andrzej Hajda wrote:
> Alias is shorter and more readable.
NAK. We want to get rid of these extra 'dev' pointers.
>
> Signed-off-by: Andrzej Hajda
> Reviewed-by: Andi Shyti
> ---
> drivers/gpu/drm/i915/display/icl_dsi.c | 4 ++--
>
There is special helper for register read/modify/write.
Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
---
drivers/gpu/drm/i915/display/intel_tc.c | 9 +-
drivers/gpu/drm/i915/i915_irq.c | 227 +---
drivers/gpu/drm/i915/intel_pm.c | 60 ++-
Two small changes in intel_uncore_rmw will allow to use it more broadly:
- write register unconditionally, for use with latch registers,
- return old value of the register, IRQ cleanup and similar.
If we really want to keep write-only-if-changed feature maybe other
helper will be more suitable
Alias is shorter and more readable.
Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
---
drivers/gpu/drm/i915/i915_irq.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index
Alias is shorter and more readable.
Signed-off-by: Andrzej Hajda
Reviewed-by: Andi Shyti
---
drivers/gpu/drm/i915/display/icl_dsi.c | 4 ++--
drivers/gpu/drm/i915/display/intel_display.c| 3 +--
.../gpu/drm/i915/display/intel_display_debugfs.c| 2 +-
This patchset should not modify behaviour of the code (except patch 3).
It just replaces sequence of uncore read/modify/write with single call.
Moreover it replaces nested pointers with alias if there is one.
All patches except 3rd, were generated using coccinelle (quite ugly)
and adjusted in some
== Series Details ==
Series: drm/display: Don't assume dual mode adaptors support i2c sub-addressing
(rev2)
URL : https://patchwork.freedesktop.org/series/109049/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_1 -> Patchwork_109049v2
== Series Details ==
Series: drm/display: Don't assume dual mode adaptors support i2c sub-addressing
(rev2)
URL : https://patchwork.freedesktop.org/series/109049/
State : warning
== Summary ==
Error: patch
https://patchwork.freedesktop.org/api/1.0/series/109049/revisions/2/mbox/ not
found
Current dual mode adaptor ("DP++") detection code assumes that all
adaptors support i2c sub-addressing for read operations from the
DP-HDMI adaptor ID buffer. It has been observed that multiple
adaptors do not in fact support this, and always return data starting
at register 0. On affected
== Series Details ==
Series: drm/i915: stop using swiotlb (rev7)
URL : https://patchwork.freedesktop.org/series/106589/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_1 -> Patchwork_106589v7
Summary
---
== Series Details ==
Series: series starting with [1/3] drm/i915: Extract intel_mmio_bar() (rev2)
URL : https://patchwork.freedesktop.org/series/109421/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12219_full -> Patchwork_109421v2_full
== Series Details ==
Series: drm/i915: stop using swiotlb (rev7)
URL : https://patchwork.freedesktop.org/series/106589/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: drm/i915/pxp: Prepare intel_pxp entry points for MTL
URL : https://patchwork.freedesktop.org/series/109429/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12219_full -> Patchwork_109429v1_full
On Wed, Oct 05, 2022 at 04:03:56PM -0600, Alex Williamson wrote:
> We can't have a .remove callback that does nothing, this breaks
> removing the device while it's in use. Once we have the
> vfio_unregister_group_dev() fix below, we'll block until the device is
> unused, at which point
On Wed, Oct 05, 2022 at 02:17:17PM -0600, Alex Williamson wrote:
> > diff --git a/drivers/gpu/drm/i915/gvt/kvmgt.c
> > b/drivers/gpu/drm/i915/gvt/kvmgt.c
> > index 41bba40feef8f4..9003145adb5a93 100644
> > --- a/drivers/gpu/drm/i915/gvt/kvmgt.c
> > +++ b/drivers/gpu/drm/i915/gvt/kvmgt.c
> > @@
== Series Details ==
Series: series starting with [1/2] drm/i915: Take display INIT power for GPU
reset/restore
URL : https://patchwork.freedesktop.org/series/109426/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12219_full -> Patchwork_109426v1_full
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: enable PS64 support for DG2
(rev2)
URL : https://patchwork.freedesktop.org/series/109384/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_1 -> Patchwork_109384v2
Hi Dave, Daniel,
Some fixes for the merge window - one EHL MOCS table fix and the rest is
in the display area around modifier handling and PSR on Gen12+, one fixup
for g4x+ and one fixing recent fastset refactoring.
Regards,
Tvrtko
drm-intel-next-fixes-2022-10-06-1:
- Round to closest in g4x+
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: enable PS64 support for DG2
(rev2)
URL : https://patchwork.freedesktop.org/series/109384/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked
== Series Details ==
Series: series starting with [v3,1/2] drm/i915: enable PS64 support for DG2
(rev2)
URL : https://patchwork.freedesktop.org/series/109384/
State : warning
== Summary ==
Error: dim checkpatch failed
cd65a7e6406b drm/i915: enable PS64 support for DG2
-:15:
> -Original Message-
> From: Jani Nikula
> Sent: Friday, September 30, 2022 12:05 PM
> To: Kahola, Mika ; intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH 1/5] drm/i915/mtl: Add Support for C10, C20
> PHY
> Message Bus
>
> On Thu, 29 Sep 2022, Mika Kahola wrote:
> >
On 05/10/2022 19:48, John Harrison wrote:
On 10/3/2022 05:00, Tvrtko Ursulin wrote:
On 03/10/2022 08:53, Tvrtko Ursulin wrote:
On 30/09/2022 18:44, John Harrison wrote:
On 9/30/2022 02:22, Tvrtko Ursulin wrote:
On 29/09/2022 17:21, John Harrison wrote:
On 9/29/2022 00:42, Tvrtko Ursulin
== Series Details ==
Series: drm/i915/slpc: Update frequency debugfs for SLPC (rev4)
URL : https://patchwork.freedesktop.org/series/109328/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12219_full -> Patchwork_109328v4_full
On Wed, 5 Oct 2022 at 20:56, Ville Syrjala
wrote:
>
> From: Ville Syrjälä
>
> We use all kinds of weird names for our base address registers.
> Take the names from the spec and stick to them to avoid confusing
> everyone.
>
> The only exceptions are IOBAR and LMEMBAR since naming them
>
== Series Details ==
Series: series starting with [1/2] drm/i915: add back GEN12_BDSM_MASK
URL : https://patchwork.freedesktop.org/series/109420/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12219_full -> Patchwork_109420v1_full
== Series Details ==
Series: Delay disabling GuC scheduling of an idle context
URL : https://patchwork.freedesktop.org/series/109442/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12221 -> Patchwork_109442v1
Summary
== Series Details ==
Series: Fix Guc-Err-Capture sizing warning
URL : https://patchwork.freedesktop.org/series/109439/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12221 -> Patchwork_109439v1
Summary
---
From: Matthew Brost
Add a delay, configurable via debugfs (default 34ms), to disable
scheduling of a context after the pin count goes to zero. Disable
scheduling is a costly operation as it requires synchronizing with
the GuC. So the idea is that a delay allows the user to resubmit
something
This series adds a delay before disabling scheduling of the guc-context
when a context has become idle to avoid costly re-registration that may
occur immediately after. The 2nd patch should explain it quite well.
The origin of this series was posted by Matthew Brost back in Oct 2021
75 matches
Mail list logo
