From: Zbigniew Kempczyński
Extend coverage of the blitter client by exercising conversion to and
from tiled sources. In the process we perform spot checks to verify that
the tiling/detiling is being applied correctly, along with position
invariance of the tiling parameters.
Signed-off-by: Zbigni
On 29.04.2020 10:57, Jani Nikula wrote:
> On Tue, 28 Apr 2020, Michal Orzel wrote:
>> As suggested by the TODO list for the kernel DRM subsystem, replace
>> the deprecated functions that take/drop modeset locks with new helpers.
>>
>> Signed-off-by: Michal Orzel
>> ---
>> drivers/gpu/drm/drm_
== Series Details ==
Series: drm/i915: Add support for HDCP 1.4 over MST connectors (rev6)
URL : https://patchwork.freedesktop.org/series/70393/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8394_full -> Patchwork_17521_full
On 2020-04-29 at 18:12:32 +, Voldman, Mikhail wrote:
> Hi Ram,
>
> Thank you for your help, in the past.
> We can control HDCP on our products as needed.
>
> One issue on the new motherboard used in our product.
> In this case, i915 advertises itself as DP-1 sink repeater and authenticated
== Series Details ==
Series: series starting with [1/3] drm/i915: Nuke mode.vrefresh usage
URL : https://patchwork.freedesktop.org/series/76741/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8394_full -> Patchwork_17520_full
== Series Details ==
Series: drm/i915/gt: Stop holding onto the pinned_default_state
URL : https://patchwork.freedesktop.org/series/76738/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8394_full -> Patchwork_17519_full
Summ
== Series Details ==
Series: drm/i915: Update Slylake PCI IDs
URL : https://patchwork.freedesktop.org/series/76750/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8399 -> Patchwork_17524
Summary
---
**SUCCESS**
No
Add three new devices 0x1913, 0x1915, and 0x1917 also known as
iSKLULTGT15, iSKLULXGT15, and iSKLDTGT15; GT1.5 looks closer to GT2.
Reclassify 0x1923, 0x1927, and 0x192A according to specifications and
the second least significant digit, which points to GT3 as appropriate tier.
Signed-off-by: Alex
Reclassify 0x0426 as GT3 (GT2+) according to specifications and the second
least significant digit.
Signed-off-by: Alexei Podtelezhnikov
---
include/drm/i915_pciids.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/drm/i915_pciids.h b/include/drm/i915_pciids.h
index
Hi all,
What follows are small changes to Haswell and Skylake lists. Some of
the changes are purely semantic because some devices are not even
tracked in the current Windows driver. Do they even exist? Perhaps, at
some point the discontinued lines can be cleaned. I also learned that,
from Haswell
On Sat, 2020-04-25, Lyude Paul wrote:
>
>Hi! Sorry this took me a little while to get back to, I had a couple of MST
>regressions that I had to look into
>
>On Sat, 2020-04-18 at 05:24 +0800, Lee Shawn C wrote:
>> So far, max dot clock rate for MST mode rely on physcial bandwidth
>> limitation.
== Series Details ==
Series: drm/i915/selftests: Add tiled blits selftest
URL : https://patchwork.freedesktop.org/series/76746/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8397 -> Patchwork_17523
Summary
---
**FAIL
== Series Details ==
Series: drm/i915/selftests: Add tiled blits selftest
URL : https://patchwork.freedesktop.org/series/76746/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
94fe0ca107f9 drm/i915/selftests: Add tiled blits selftest
-:578: WARNING:LINE_SPACING: Missing a blank l
Quoting Chris Wilson (2020-04-30 01:20:35)
> +static int igt_client_tiled_blits(void *arg)
> +{
> + struct drm_i915_private *i915 = arg;
> + I915_RND_STATE(prng);
> + int inst = 0;
> +
> + /* Test requires explicit BLT tiling controls */
> + if (INTEL_GEN(i915) < 4)
>
From: Zbigniew Kempczyński
Extend coverage of the blitter client by exercising conversion to and
from tiled sources. In the process we perform spot checks to verify that
the tiling/detiling is being applied correctly, along with position
invariance of the tiling parameters.
Signed-off-by: Zbigni
== Series Details ==
Series: drm/i915/gt: Keep a no-frills swappable copy of the default context
state (rev4)
URL : https://patchwork.freedesktop.org/series/76678/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8392_full -> Patchwork_17518_full
== Series Details ==
Series: drm/i915: FBC fixes (rev2)
URL : https://patchwork.freedesktop.org/series/76714/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8392_full -> Patchwork_17517_full
Summary
---
**SUCCESS**
== Series Details ==
Series: series starting with [CI,1/6] drm/i915/gt: Always enable busy-stats for
execlists
URL : https://patchwork.freedesktop.org/series/76744/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8395 -> Patchwork_17522
=
== Series Details ==
Series: series starting with [CI,1/6] drm/i915/gt: Always enable busy-stats for
execlists
URL : https://patchwork.freedesktop.org/series/76744/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5b70b28be5c0 drm/i915/gt: Always enable busy-stats for execlists
8
== Series Details ==
Series: drm/i915: Add support for HDCP 1.4 over MST connectors (rev6)
URL : https://patchwork.freedesktop.org/series/70393/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8394 -> Patchwork_17521
Summary
In the near future, we will utilize the busy-stats on each engine to
approximate the C0 cycles of each, and use that as an input to a manual
RPS mechanism. That entails having busy-stats always enabled and so we
can remove the enable/disable routines and simplify the pmu setup. As a
consequence of
Use the new intel_rps.flags field to store whether or not interrupts are
being used with RPS.
Signed-off-by: Chris Wilson
Reviewed-by: Andi Shyti
---
drivers/gpu/drm/i915/gt/intel_rps.c | 17 -
drivers/gpu/drm/i915/gt/intel_rps.h | 15 +++
drivers/gpu/drm
We treat parking as a manual RPS timeout event, and downclock the GPU
for the next unpark and batch execution. However, having restored the
aggressive downclocking and observed that we have very light workloads
whose only interaction is through the manual parking events, carry over
the aggressive d
Pull the boolean intel_rps.enabled and intel_rps.active into a single
flags field, in preparation for more.
Signed-off-by: Chris Wilson
Reviewed-by: Andi Shyti
---
drivers/gpu/drm/i915/gt/debugfs_gt_pm.c | 5 +--
drivers/gpu/drm/i915/gt/intel_rps.c | 43 ++-
drivers
As with the realisation for soft-rc6, we respond to idling the engines
within microseconds, far faster than the response times for HW RC6 and
RPS. Furthermore, our fast parking upon idle, prevents HW RPS from
running for many desktop workloads, as the RPS evaluation intervals are
on the order of te
We reduced the clocks slowly after a boost event based on the
observation that the smoothness of animations suffered. However, since
reducing the evalution intervals, we should be able to respond to the
rapidly fluctuating workload of a simple desktop animation and so
restore the more aggressive do
== Series Details ==
Series: drm/i915: Add support for HDCP 1.4 over MST connectors (rev6)
URL : https://patchwork.freedesktop.org/series/70393/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7c5a77a1d31e drm/i915: Fix sha_text population code
-:66: WARNING:LINE_SPACING: Missing
== Series Details ==
Series: series starting with [1/3] drm/i915: Nuke mode.vrefresh usage
URL : https://patchwork.freedesktop.org/series/76741/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8394 -> Patchwork_17520
Summary
== Series Details ==
Series: series starting with [1/3] drm/i915: Nuke mode.vrefresh usage
URL : https://patchwork.freedesktop.org/series/76741/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c72890c16d9b drm/i915: Nuke mode.vrefresh usage
e45bfe3703e2 drm/i915: Rename variables
== Series Details ==
Series: drm/i915/gt: Stop holding onto the pinned_default_state
URL : https://patchwork.freedesktop.org/series/76738/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8394 -> Patchwork_17519
Summary
--
From: Sean Paul
In order to act upon content_protection property changes, we'll need to
implement the .update_pipe() hook. We can re-use intel_ddi_update_pipe
for this
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20191203173638.94919-10-s...@poorly.run
#v1
Link
From: Sean Paul
Instead of hand rolling the transfer ourselves in the hdcp hook, inspect
aux messages and add the aksv flag in the aux transfer hook.
IIRC, this was the original implementation and folks wanted this hack to
be isolated to the hdcp code, which makes sense.
However in testing an L
From: Sean Paul
Although DP_MST fake encoders are not subclassed from digital ports,
they are associated with them. Support these encoders.
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20191203173638.94919-9-s...@poorly.run
#v1
Link:
https://patchwork.freedesk
From: Sean Paul
This patch plumbs port through hdcp init instead of relying on
intel_attached_encoder() to return a non-NULL encoder which won't work
for MST connectors.
Cc: Ville Syrjälä
Signed-off-by: Sean Paul
Changes in v5:
-Added to the set
Changes in v6:
-None
Signed-off-by: Sean Paul
From: Sean Paul
This patch adds some protection against connectors being destroyed
before the HDCP workers are finished.
For check_work, we do a synchronous cancel after the connector is
unregistered which will ensure that it is finished before destruction.
In the case of prop_work, we can't do
From: Sean Paul
De-duplicate the HDCP version code for each connector and print it for
all connectors.
Cc: Juston Li
Cc: Ramalingam C
Reviewed-by: Juston Li
Reviewed-by: Ramalingam C
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20200227185714.171466-1-s...@
From: Sean Paul
Currently we derive the connector from digital port in check_link(). For
MST, this isn't sufficient since the digital port passed into the
function can have multiple connectors downstream. This patch adds
connector to the check_link() arguments so we have it when we need it.
Sign
From: Sean Paul
This is a bit of housecleaning for a future patch. Instead of sprinkling
hdcp->value assignments and prop_work scheduling everywhere, introduce a
function to do it for us.
Reviewed-by: Ramalingam C
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20
From: Sean Paul
On HDCP disable, clear the repeater bit. This ensures if we connect a
non-repeater sink after a repeater, the bit is in the state we expect.
Fixes: ee5e5e7a5e0f (drm/i915: Add HDCP framework + base implementation)
Cc: Chris Wilson
Cc: Ramalingam C
Cc: Daniel Vetter
Cc: Sean Pa
From: Sean Paul
Instead of using intel_dig_port's encoder pipe to determine which
transcoder to toggle signalling on, use the cpu_transcoder field already
stored in intel_hdmi.
This is particularly important for MST.
Suggested-by: Ville Syrjälä
Reviewed-by: Ramalingam C
Signed-off-by: Sean Pa
From: Sean Paul
Now that all the groundwork has been laid, we can turn on HDCP 1.4 over
MST. Everything except for toggling the HDCP signalling and HDCP 2.2
support is the same as the DP case, so we'll re-use those callbacks
Cc: Juston Li
Signed-off-by: Sean Paul
Link:
https://patchwork.freed
From: Sean Paul
This patch fixes a few bugs:
1- We weren't taking into account sha_leftovers when adding multiple
ksvs to sha_text. As such, we were or'ing the end of ksv[j - 1] with
the beginning of ksv[j]
2- In the sha_leftovers == 2 and sha_leftovers == 3 case, bstatus was
being pla
From: Sean Paul
This patch is required for HDCP over MST. If a port is being used for
multiple HDCP streams, we don't want to fully disable HDCP on a port if
one of them is disabled. Instead, we just disable the HDCP signalling on
that particular pipe and exit early. The last pipe to disable HDCP
From: Sean Paul
These functions are all the same for dp and dp_mst, so move them into a
dedicated file for both sst and mst to use.
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20191203173638.94919-11-s...@poorly.run
#v1
Link:
https://patchwork.freedesktop.org
From: Sean Paul
Used to query whether an MST stream is encrypted or not.
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20200218220242.107265-14-s...@poorly.run
#v4
Link:
https://patchwork.freedesktop.org/patch/msgid/20200305201236.152307-15-s...@poorly.run
#v
From: Sean Paul
HDCP signalling should not be left on, WARN if it is
Cc: Ville Syrjälä
Cc: Daniel Vetter
Reviewed-by: Ramalingam C
Signed-off-by: Sean Paul
Link:
https://patchwork.freedesktop.org/patch/msgid/20191212190230.188505-4-s...@poorly.run
#v2
Link:
https://patchwork.freedesktop.o
From: Sean Paul
Changes in v6:
-Rebased on -tip
-Disabled HDCP over MST on GEN12
-Addressed Lyude's review comments in the QUERY_STREAM_ENCRYPTION_STATUS patch
Sean Paul (16):
drm/i915: Fix sha_text population code
drm/i915: Clear the repeater bit on HDCP disable
drm/i915: WARN if HDCP sig
== Series Details ==
Series: drm/i915/hdcp: Fix the return handling of drm_hdcp_check_ksvs_revoked
URL : https://patchwork.freedesktop.org/series/76730/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8391_full -> Patchwork_17515_full
Quoting Ville Syrjala (2020-04-29 19:54:57)
> From: Ville Syrjälä
>
> All these ROUNDIND_FACTORs and whatnot are making this thing hard to
> read. Get rid of them. And let's massage some of the fractions to
> give us less questionable intermediate results and perhaps less
> divisions.
>
> Also l
Quoting Ville Syrjala (2020-04-29 19:54:55)
> From: Ville Syrjälä
>
> mode.vrefresh is rounded to the nearest integer. You don't want to use
> it anywhere that requires precision. Also I want to nuke it.
> vtotal*vrefresh == 1000*clock/htotal, so let's use the latter.
>
> Cc: Anshuman Gupta
> C
== Series Details ==
Series: drm/i915/selftests: fix error handling in __live_lrc_indirect_ctx_bb()
URL : https://patchwork.freedesktop.org/series/76727/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8391_full -> Patchwork_17514_full
===
From: Ville Syrjälä
All these ROUNDIND_FACTORs and whatnot are making this thing hard to
read. Get rid of them. And let's massage some of the fractions to
give us less questionable intermediate results and perhaps less
divisions.
Also looks like a good helping of 64bit math stuff is needed to
av
From: Ville Syrjälä
Since the code seems insistent on using the variable names from the
bspec formulat, let's be consistent and use those names for all
the things. For some reason 'link_clk' and 'lanes' were left out
in the code until now.
Cc: Anshuman Gupta
Cc: Uma Shankar
Signed-off-by: Vill
From: Ville Syrjälä
mode.vrefresh is rounded to the nearest integer. You don't want to use
it anywhere that requires precision. Also I want to nuke it.
vtotal*vrefresh == 1000*clock/htotal, so let's use the latter.
Cc: Anshuman Gupta
Cc: Uma Shankar
Signed-off-by: Ville Syrjälä
---
drivers/g
As we only restore the default context state upon banning a context, we
only need enough of the state to run the ring and nothing more. That is
we only need our bare protocontext.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc: Mika Kuoppala
Cc: Andi Shyti
---
drivers/gpu/drm/i915/gt/intel
Hi Ram,
Thank you for your help, in the past.
We can control HDCP on our products as needed.
One issue on the new motherboard used in our product.
In this case, i915 advertises itself as DP-1 sink repeater and authenticated as
HDCP 1.4 capable device, but downstream HDMI device is HDCP 2.3 capa
== Series Details ==
Series: drm/i915: Allow some leniency in PCU reads
URL : https://patchwork.freedesktop.org/series/76723/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8391_full -> Patchwork_17512_full
Summary
---
== Series Details ==
Series: drm/i915/gt: Keep a no-frills swappable copy of the default context
state (rev4)
URL : https://patchwork.freedesktop.org/series/76678/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8392 -> Patchwork_17518
==
== Series Details ==
Series: drm/i915/gt: Keep a no-frills swappable copy of the default context
state (rev4)
URL : https://patchwork.freedesktop.org/series/76678/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c042783f5aa7 drm/i915/gt: Keep a no-frills swappable copy of the de
== Series Details ==
Series: drm/i915: FBC fixes (rev2)
URL : https://patchwork.freedesktop.org/series/76714/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8392 -> Patchwork_17517
Summary
---
**SUCCESS**
No regres
We need to keep the default context state around to instantiate new
contexts (aka golden rendercontext), and we also keep it pinned while
the engine is active so that we can quickly reset a hanging context.
However, the default contexts are large enough to merit keeping in
swappable memory as oppos
Quoting Patchwork (2020-04-29 18:01:19)
> == Series Details ==
>
> Series: series starting with [CI,1/2] drm/i915/gt: Keep a no-frills swappable
> copy of the default context state (rev4)
> URL : https://patchwork.freedesktop.org/series/76719/
> State : failure
>
> == Summary ==
>
> CI Bug Lo
== Series Details ==
Series: drm/i915: Update Slylake PCI IDs
URL : https://patchwork.freedesktop.org/series/76720/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8391_full -> Patchwork_17510_full
Summary
---
**FAILUR
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/gt: Keep a no-frills swappable
copy of the default context state (rev4)
URL : https://patchwork.freedesktop.org/series/76719/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8392 -> Patchwork_17516
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/gt: Keep a no-frills swappable
copy of the default context state (rev4)
URL : https://patchwork.freedesktop.org/series/76719/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
33c25886e49a drm/i915/gt: Keep a no-f
Quoting Matthew Auld (2020-04-29 17:11:38)
> On 28/04/2020 22:55, Chris Wilson wrote:
> > We need to keep the default context state around to instantiate new
> > contexts (aka golden rendercontext), and we also keep it pinned while
> > the engine is active so that we can quickly reset a hanging con
On 2020-04-29 at 10:46:29 -0400, Sean Paul wrote:
> On Wed, Apr 29, 2020 at 10:22 AM Ramalingam C wrote:
> >
> > On 2020-04-29 at 09:58:16 -0400, Sean Paul wrote:
> > > On Wed, Apr 29, 2020 at 9:50 AM Ramalingam C
> > > wrote:
> > > >
> > > > On 2020-04-14 at 15:02:55 -0400, Sean Paul wrote:
> >
Hi,
On Thu, Apr 23, 2020 at 09:26:01PM -0400, Rodrigo Siqueira wrote:
> A couple of months ago, I updated and re-submitted a patchset made by
> Brian Starkey and Liviu Dudau for adding a writeback connectors test to
> IGT. It is important to highlight that DRM already have writeback
> connectors s
April 28, 2020 5:14 PM, "Daniel Vetter" wrote:
> On Fri, Apr 24, 2020 at 06:26:15PM +0200, Kenny Levinsen wrote:
>
>> Some processes, such as systemd, are only polling for EPOLLERR|EPOLLHUP.
>> As drm_file uses unkeyed wakeups, such a poll can receive many spurious
>> wakeups from uninteresting
On 28/04/2020 22:55, Chris Wilson wrote:
We need to keep the default context state around to instantiate new
contexts (aka golden rendercontext), and we also keep it pinned while
the engine is active so that we can quickly reset a hanging context.
However, the default contexts are large enough to
On 29/04/2020 18:26, Chris Wilson wrote:
Quoting Lionel Landwerlin (2020-04-29 16:23:34)
On 29/04/2020 18:05, Chris Wilson wrote:
Wait until the GPU is idle before starting a fresh round of probing
gen8-unprivileged-single-ctx-counter. This avoids building up a huge
backlog of render copies, ho
On Wed, Apr 29, 2020 at 7:41 AM Alexei Podtelezhnikov
wrote:
>
> Add three new devices 0x1913, 0x1915, and 0x1917 also known as
> iSKLULTGT15, iSKLULXGT15, and iSKLDTGT15. Reclassify 0x1923, 0x1927,
> and 0x192A according to specifications. Of note, the second to last
> digit seems to correspond t
From: Ville Syrjälä
Consult the actual plane stride instead of the fb stride. The two
will disagree when we remap the gtt. The plane stride is what the
hw will be fed so that's what we should look at for the FBC
retrictions/cfb allocation.
Since we no longer require a fence we are going to attem
Quoting Lionel Landwerlin (2020-04-29 16:23:34)
> On 29/04/2020 18:05, Chris Wilson wrote:
> > Wait until the GPU is idle before starting a fresh round of probing
> > gen8-unprivileged-single-ctx-counter. This avoids building up a huge
> > backlog of render copies, hogging buffers and stale context
== Series Details ==
Series: drm: Put drm_display_mode on diet (rev6)
URL : https://patchwork.freedesktop.org/series/73674/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8390_full -> Patchwork_17509_full
Summary
---
On 29/04/2020 18:05, Chris Wilson wrote:
Wait until the GPU is idle before starting a fresh round of probing
gen8-unprivileged-single-ctx-counter. This avoids building up a huge
backlog of render copies, hogging buffers and stale contexts, and
invoking the oomkiller.
v2: Release everything befor
== Series Details ==
Series: drm/i915/hdcp: Fix the return handling of drm_hdcp_check_ksvs_revoked
URL : https://patchwork.freedesktop.org/series/76730/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8391 -> Patchwork_17515
As we only restore the default context state upon banning a context, we
only need enough of the state to run the ring and nothing more. That is
we only need our bare protocontext.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
Cc: Mika Kuoppala
Cc: Andi Shyti
---
drivers/gpu/drm/i915/gt/intel
Wait until the GPU is idle before starting a fresh round of probing
gen8-unprivileged-single-ctx-counter. This avoids building up a huge
backlog of render copies, hogging buffers and stale contexts, and
invoking the oomkiller.
v2: Release everything before starting again.
Signed-off-by: Chris Wil
Quoting Lionel Landwerlin (2020-04-29 15:57:41)
> Oh... Is that on a low end platform?
glk. But it was mostly that it got stuck in the rut of hitting -EAGAIN.
/* This needs to be investigated... From time
* to time, the work we kick off doesn't seem
* to happen. WTH?? */
Hmm. And that's before
Oh... Is that on a low end platform?
Looks alright :
Reviewed-by: Lionel Landwerlin
Thanks,
-Lionel
On 29/04/2020 17:51, Chris Wilson wrote:
Wait until the GPU is idle before starting a fresh round of probing
gen8-unprivileged-single-ctx-counter. This avoids building up a huge
backlog of re
== Series Details ==
Series: drm/i915/selftests: fix error handling in __live_lrc_indirect_ctx_bb()
URL : https://patchwork.freedesktop.org/series/76727/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8391 -> Patchwork_17514
Wait until the GPU is idle before starting a fresh round of probing
gen8-unprivileged-single-ctx-counter. This avoids building up a huge
backlog of render copies, hogging buffers and stale contexts, and
invoking the oomkiller.
Signed-off-by: Chris Wilson
Cc: Lionel Landwerlin
---
tests/perf.c |
On Wed, Apr 29, 2020 at 9:46 AM Ramalingam C wrote:
>
> drm_hdcp_check_ksvs_revoked() returns the number of revoked keys and
> error codes when the SRM parsing is failed.
>
> Errors in SRM parsing can't affect the HDCP auth, hence with this patch,
> I915 will look out for revoked key count alone.
On Wed, Apr 29, 2020 at 10:22 AM Ramalingam C wrote:
>
> On 2020-04-29 at 09:58:16 -0400, Sean Paul wrote:
> > On Wed, Apr 29, 2020 at 9:50 AM Ramalingam C wrote:
> > >
> > > On 2020-04-14 at 15:02:55 -0400, Sean Paul wrote:
> > > > From: Sean Paul
> > > >
> > > > The SRM cleanup in 79643fddd6eb
== Series Details ==
Series: series starting with [CI,1/6] drm/i915/gt: Always enable busy-stats for
execlists
URL : https://patchwork.freedesktop.org/series/76715/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8390_full -> Patchwork_17508_full
===
== Series Details ==
Series: series starting with [01/25] perf/core: Only copy-to-user after
completely unlocking all locks, v3.
URL : https://patchwork.freedesktop.org/series/76724/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8391 -> Patchwork_17513
===
On 2020-04-29 at 09:58:16 -0400, Sean Paul wrote:
> On Wed, Apr 29, 2020 at 9:50 AM Ramalingam C wrote:
> >
> > On 2020-04-14 at 15:02:55 -0400, Sean Paul wrote:
> > > From: Sean Paul
> > >
> > > The SRM cleanup in 79643fddd6eb2 ("drm/hdcp: optimizing the srm
> > > handling") inadvertently altere
Quoting Tvrtko Ursulin (2020-04-29 14:42:44)
>
> On 28/04/2020 10:02, Chris Wilson wrote:
> > Once the intel_context is closed, the GEM context may be freed and so
> > the link from intel_context.gem_context is invalid.
> >
> > <3>[ 219.782944] BUG: KASAN: use-after-free in
> > intel_engine_cor
Hi Dan,
On Wed, Apr 29, 2020 at 04:24:25PM +0300, Dan Carpenter wrote:
> If intel_context_create() fails then it leads to an error pointer
> dereference. I shuffled things around to make error handling easier.
>
> Fixes: 1dd47b54baea ("drm/i915: Add live selftests for indirect ctx
> batchbuffer
== Series Details ==
Series: series starting with [01/25] perf/core: Only copy-to-user after
completely unlocking all locks, v3.
URL : https://patchwork.freedesktop.org/series/76724/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
fafe194bca56 perf/core: Only copy-to-user after
On Wed, Apr 29, 2020 at 9:50 AM Ramalingam C wrote:
>
> On 2020-04-14 at 15:02:55 -0400, Sean Paul wrote:
> > From: Sean Paul
> >
> > The SRM cleanup in 79643fddd6eb2 ("drm/hdcp: optimizing the srm
> > handling") inadvertently altered the behavior of HDCP auth when
> > the SRM firmware is missing
== Series Details ==
Series: drm/i915: Allow some leniency in PCU reads
URL : https://patchwork.freedesktop.org/series/76723/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8391 -> Patchwork_17512
Summary
---
**SUCCES
Quoting Dan Carpenter (2020-04-29 14:24:25)
> If intel_context_create() fails then it leads to an error pointer
> dereference. I shuffled things around to make error handling easier.
>
> Fixes: 1dd47b54baea ("drm/i915: Add live selftests for indirect ctx
> batchbuffers")
> Signed-off-by: Dan Car
Quoting Patchwork (2020-04-29 14:46:49)
> == Series Details ==
>
> Series: series starting with [CI,1/2] drm/i915/gt: Keep a no-frills swappable
> copy of the default context state (rev3)
> URL : https://patchwork.freedesktop.org/series/76719/
> State : failure
>
> == Summary ==
>
> CI Bug Lo
On 2020-04-14 at 15:02:55 -0400, Sean Paul wrote:
> From: Sean Paul
>
> The SRM cleanup in 79643fddd6eb2 ("drm/hdcp: optimizing the srm
> handling") inadvertently altered the behavior of HDCP auth when
> the SRM firmware is missing. Before that patch, missing SRM was
> interpreted as the device h
== Series Details ==
Series: series starting with [CI,1/2] drm/i915/gt: Keep a no-frills swappable
copy of the default context state (rev3)
URL : https://patchwork.freedesktop.org/series/76719/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8391 -> Patchwork_17511
drm_hdcp_check_ksvs_revoked() returns the number of revoked keys and
error codes when the SRM parsing is failed.
Errors in SRM parsing can't affect the HDCP auth, hence with this patch,
I915 will look out for revoked key count alone.
Signed-off-by: Ramalingam C
cc: Sean Paul
---
drivers/gpu/dr
== Series Details ==
Series: drm/i915: FBC fixes
URL : https://patchwork.freedesktop.org/series/76714/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8390_full -> Patchwork_17507_full
Summary
---
**FAILURE**
Seriou
On 28/04/2020 10:02, Chris Wilson wrote:
Once the intel_context is closed, the GEM context may be freed and so
the link from intel_context.gem_context is invalid.
<3>[ 219.782944] BUG: KASAN: use-after-free in
intel_engine_coredump_alloc+0x1bc3/0x2250 [i915]
<3>[ 219.782996] Read of size 8
1 - 100 of 179 matches
Mail list logo
