== Series Details ==
Series: drm/i915/selftests: add basic selftests for rc6 (rev7)
URL : https://patchwork.freedesktop.org/series/69825/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7874 -> Patchwork_16452
Summary
---
== Series Details ==
Series: series starting with [v2,1/3] drm/i915/display/fbc: Make fences a
nice-to-have for GEN11+
URL : https://patchwork.freedesktop.org/series/73070/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7874 -> Patchwork_16451
=
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: aed2ea22e07850d8f5fae07fcf3db8adf694b3d9
commit: 9c654e423507127b37b32e15543b2e04a719eab2 [6/9] Merge remote-tracking
branch 'drm-intel/drm-intel-next-queued' into drm-tip
config: i386-randconfig-g002-20200206 (attached as .config)
== Series Details ==
Series: series starting with [v2,1/3] drm/i915/display/fbc: Make fences a
nice-to-have for GEN11+
URL : https://patchwork.freedesktop.org/series/73070/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
33582ba1b9a2 drm/i915/display/fbc: Make fences a nice-to-h
== Series Details ==
Series: series starting with [1/3] drm/i915/gt: Tweak gen7 xcs flushing
URL : https://patchwork.freedesktop.org/series/73068/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7874 -> Patchwork_16450
Summar
== Series Details ==
Series: drm/i915/gt: Tweak gen7 xcs flushing
URL : https://patchwork.freedesktop.org/series/73067/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7874 -> Patchwork_16449
Summary
---
**SUCCESS**
== Series Details ==
Series: series starting with [1/3] drm/i915/gt: Tweak gen7 xcs flushing
URL : https://patchwork.freedesktop.org/series/73068/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
be0c11af059b drm/i915/gt: Tweak gen7 xcs flushing
-:51: WARNING:LONG_LINE: line over
== Series Details ==
Series: drm/i915/selftests: Trim blitter block size
URL : https://patchwork.freedesktop.org/series/73066/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7874 -> Patchwork_16448
Summary
---
**FAILU
== Series Details ==
Series: drm/i915/selftests: Trim blitter block size
URL : https://patchwork.freedesktop.org/series/73066/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b4454179762f drm/i915/selftests: Trim blitter block size
-:39: WARNING:MEMORY_BARRIER: memory barrier wit
== Series Details ==
Series: drm/i915: Fix redefinition of sanitize_watermarks_add_affected
URL : https://patchwork.freedesktop.org/series/73065/
State : failure
== Summary ==
Applying: drm/i915: Fix redefinition of sanitize_watermarks_add_affected
Using index info to reconstruct a base tree..
From: Andi Shyti
Add three basic tests for rc6 power status:
1. live_rc6_basic - simply checks if rc6 works when it's enabled
or stops when it's disabled.
2. live_rc6_threshold - rc6 should not work when the evaluation
interval is less than the threshold and should work otherwise.
3. liv
== Series Details ==
Series: drm/i915/selftests: add basic selftests for rc6 (rev6)
URL : https://patchwork.freedesktop.org/series/69825/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16446
Summary
---
Commit 44a67719497b ("drm/i915: Fix modeset locks in sanitize_watermarks()")
that added this function is correctly, this issue was introduced when
resolving the merge conflict.
Fixes: 9c654e423507 ("Merge remote-tracking branch
'drm-intel/drm-intel-next-queued' into drm-tip")
Cc: Jani Nikula
Cc:
From: Radhakrishna Sripada
Platforms without fences don't have FBC host tracking and those
registers are marked as reserved in those platforms.
v2: checking num_fences to write to FBC fence registers (Ville)
Cc: Rodrigo Vivi
Cc: Matt Roper
Cc: Dhinakaran Pandiyan
Cc: Ville Syrjälä
Signed-of
dGFX have local memory so it do not have aperture and do not support
CPU fences but even for iGFX it have a small number of fences.
As replacement for fences to track frontbuffer modifications by CPU
we have a software tracking that is already in used by FBC and PSR.
PSR don't support fences so it
Always prime the page table registers before starting the ring. Even
though we will update these to the per-context page tables during
dispatch, it is prudent to ensure that the registers always point to a
valid PD.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
.../gpu/drm/i915/gt/intel_rin
Trust that the HW does the right thing after simply updating the
PD_DIR_BASE?
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
drivers/gpu/drm/i915/gt/intel_ring_submission.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_ring_submis
Don't immediately write the seqno into the breadcrumb slot, but wait
until we've attempted to flush the writes; that is we need to ensure the
memory is coherent prior to updating the breadcrumb so that any
observers who see the new seqno can proceed.
Signed-off-by: Chris Wilson
---
.../gpu/drm/i
Hi Ross
I'm unable to reproduce this issue, could you share the complete dmesg?
On Wed, 2020-02-05 at 16:01 -0700, Ross Zwisler wrote:
> On Mon, Jan 06, 2020 at 07:21:28AM -0800, José Roberto de Souza
> wrote:
> > Recent improvements in the state tracking in i915 caused PSR to not
> > be
> > enab
== Series Details ==
Series: series starting with [1/2] drm/i915/gt: Set the PP_DIR registers upon
enabling ring submission
URL : https://patchwork.freedesktop.org/series/73059/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16445
== Series Details ==
Series: drm/i915: Expose exec parameter to force non IA-Coherent for Gen9+
URL : https://patchwork.freedesktop.org/series/2428/
State : failure
== Summary ==
CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_dpp_cm.o
CC [M] drivers/gpu/drm/amd/amdgpu/../displ
== Series Details ==
Series: drm/i915/dc3co: Add description of how it works
URL : https://patchwork.freedesktop.org/series/73058/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16444
Summary
---
**S
== Series Details ==
Series: series starting with [1/2] drm: Add a detailed DP HDMI branch info on
debugfs
URL : https://patchwork.freedesktop.org/series/72914/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7859_full -> Patchwork_16392_full
===
Don't immediately write the seqno into the breadcrumb slot, but wait
until we've attempted to flush the writes; that is we need to ensure the
memory is coherent prior to updating the breadcrumb so that any
observers who see the new seqno can proceed.
Signed-off-by: Chris Wilson
---
drivers/gpu/d
Reduce the amount of work we do to verify client blt correctness as
currently our 0.5s subtests takes about 15s on slower devices!
Signed-off-by: Chris Wilson
---
.../i915/gem/selftests/i915_gem_object_blt.c | 24 ---
1 file changed, 15 insertions(+), 9 deletions(-)
diff --git
Commit 44a67719497b ("drm/i915: Fix modeset locks in sanitize_watermarks()")
that added this function is correctly, this issue was introduced when
resolving the merge conflict.
Fixes: 9c654e423507 ("Merge remote-tracking branch
'drm-intel/drm-intel-next-queued' into drm-tip")
Cc: Jani Nikula
Cc:
== Series Details ==
Series: drm/i915/display/ehl: Add HBR2 and HBR3 voltage swing table
URL : https://patchwork.freedesktop.org/series/73055/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16443
Summary
--
On Wed, 2020-01-22 at 15:16 -0800, Juston Li wrote:
> From: Daniel Stone
>
> Mirroring addfb2, add tests for the new ioctl which will return us
> information about framebuffers containing multiple buffers, as well
> as
> modifiers.
>
> Changes since v4:
> - Remove unnecessary bo creation for get
Quoting Andi Shyti (2020-02-05 22:49:49)
> +int live_rc6_busy(void *arg)
> +{
> + struct intel_gt *gt = arg;
> + struct intel_rc6 *rc6 = >->rc6;
> + struct intel_engine_cs *engine;
> + struct igt_spinner spin;
> + intel_wakeref_t wakeref;
> + enum intel_engine_id
From: Andi Shyti
Add three basic tests for rc6 power status:
1. live_rc6_basic - simply checks if rc6 works when it's enabled
or stops when it's disabled.
2. live_rc6_threshold - rc6 should not work when the evaluation
interval is less than the threshold and should work otherwise.
3. liv
== Series Details ==
Series: drm/i915/gem: Don't leak non-persistent requests on changing engines
(rev4)
URL : https://patchwork.freedesktop.org/series/73023/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16442
===
On Wed, Feb 05, 2020 at 12:56:47PM -0800, José Roberto de Souza wrote:
> EHL only differs from ICL on the voltage swing table for HBR2 and
> HBR3.
>
> BSpec: 21257
> Cc: Matt Roper
> Signed-off-by: José Roberto de Souza
> ---
> drivers/gpu/drm/i915/display/intel_ddi.c | 34 +
Always prime the page table registers before starting the ring. Even
though we will update these to the per-context page tables during
dispatch, it is prudent to ensure that the registers always point to a
valid PD.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
.../gpu/drm/i915/gt/intel_rin
Trust that the HW does the right thing after simply updating the
PD_DIR_BASE?
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
drivers/gpu/drm/i915/gt/intel_ring_submission.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_ring_submis
== Series Details ==
Series: drm/i915/gem: Don't leak non-persistent requests on changing engines
(rev4)
URL : https://patchwork.freedesktop.org/series/73023/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
66727965053c drm/i915/gem: Don't leak non-persistent requests on changin
== Series Details ==
Series: drm/i915: Hotplug cleanups (rev3)
URL : https://patchwork.freedesktop.org/series/72348/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16441
Summary
---
**SUCCESS**
No
Add a basic description about how DC3CO works to help people not
familiar with it.
While at it, I also improved the delayed work handle and function
names and removed a debug message that is ambiguous and not much
useful, no changes in behavior here.
Cc: Anshuman Gupta
Cc: Imre Deak
Signed-off-
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and
observability (rev3)
URL : https://patchwork.freedesktop.org/series/72273/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16439
== Series Details ==
Series: drm: Introduce struct drm_device based WARN* and use them in i915 (rev6)
URL : https://patchwork.freedesktop.org/series/72035/
State : failure
== Summary ==
Applying: drm/i915/display/cdclk: Make WARN* drm specific where drm_priv ptr is
available
Applying: drm/i91
Quoting Andi Shyti (2020-02-05 18:40:55)
> Hi Mika,
>
> > I have a faint memory that the interval was not always 1.28us
> > but gen dependant.
>
> 1.28 is the incremental step and I haven't seen any different
> value in the docs. Have you?
The rc6 residency counter does flip over to a different c
Hi Mika,
> > +static bool test_rc6(struct intel_rc6 *rc6, bool enabled)
> > +{
> > + struct intel_uncore *uncore = rc6_to_uncore(rc6);
> > + intel_wakeref_t wakeref;
> > + u32 ec1, ec2;
> > + u32 interval;
> > +
> > + wakeref = intel_runtime_pm_get(uncore->rpm);
> > +
> > + interval =
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and
observability (rev3)
URL : https://patchwork.freedesktop.org/series/72273/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
afa7aa8e74c6 capabilities: introduce CAP_PERFMON to kernel an
EHL only differs from ICL on the voltage swing table for HBR2 and
HBR3.
BSpec: 21257
Cc: Matt Roper
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_ddi.c | 34 +++-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915
== Series Details ==
Series: In order to readout DP SDPs, refactors the handling of DP SDPs (rev4)
URL : https://patchwork.freedesktop.org/series/72853/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16438
== Series Details ==
Series: drm/i915/dsb: Pre allocate and late cleanup of cmd buffer
URL : https://patchwork.freedesktop.org/series/73036/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7871 -> Patchwork_16437
Summary
On 2/4/20 11:58 PM, Jani Nikula wrote:
On Tue, 04 Feb 2020, "Michal Wajdeczko" wrote:
On Tue, 04 Feb 2020 00:28:29 +0100, Daniele Ceraolo Spurio
wrote:
The log struct is the only thing the function needs (apart from
the seq_file), so we can pass just that instead of the whole dev_priv.
v
If we have a set of active engines marked as being non-persistent, we
lose track of those if the user replaces those engines with
I915_CONTEXT_PARAM_ENGINES. As part of our uABI contract is that
non-persistent requests are terminated if they are no longer being
tracked by the user's context (in ord
== Series Details ==
Series: In order to readout DP SDPs, refactors the handling of DP SDPs (rev4)
URL : https://patchwork.freedesktop.org/series/72853/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
337be6e4a25e drm: add DP 1.4 VSC SDP Payload related enums and a structure
8e6c
If we have a set of active engines marked as being non-persistent, we
lose track of those if the user replaces those engines with
I915_CONTEXT_PARAM_ENGINES. As part of our uABI contract is that
non-persistent requests are terminated if they are no longer being
tracked by the user's context (in ord
== Series Details ==
Series: drm/i915/selftests: Relax timeout for error-interrupt reset processing
URL : https://patchwork.freedesktop.org/series/73032/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7870 -> Patchwork_16436
On Mon, Feb 03, 2020 at 01:06:24AM +0200, Stanislav Lisovskiy wrote:
> Those patch series, do some initial preparation DBuf manipulating code
> cleanups, i.e remove redundant structures/code, switch to mask
> based DBuf manupulation, get into use DBuf assignment according to
> BSpec rules.
>
> Sta
Quoting Tvrtko Ursulin (2020-02-05 18:33:57)
>
> On 05/02/2020 16:44, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2020-02-05 16:22:34)
> >> On 05/02/2020 12:13, Chris Wilson wrote:
> >>> If we have a set of active engines marked as being non-persistent, we
> >>> lose track of those if the user
From: Ville Syrjälä
Remainder of the earlier hotplug cleanups. This time without
exposing functions between ddi and dp code, and instead we
just duplicate a few of them.
Ville Syrjälä (5):
drm/i915/hpd: Replace the loop-within-loop with two independent loops
drm/i915: Mark all HPD capabled c
From: Ville Syrjälä
Let's get rid of the platform if ladders in
intel_digital_port_connected() and make it a vfunc. Now the if
ladders are at the encoder initialization which makes them a bit
less convoluted.
v2: Add forward decl for intel_encoder in intel_tc.h
v3: Duplicate stuff to avoid expos
From: Ville Syrjälä
Currently we only set the DRM_CONNECTOR_POLL_{DISCONNECT,CONNECT}
bits in intel_connector->polled (the base setting), leading to
some confusing looking code to reset drm_connector->polled
(the actual setting) to DRM_CONNECTOR_POLL_HPD. Let's set
intel_connector->polled = DRM_C
From: Ville Syrjälä
Get rid of several platform specific variants of
intel_digital_port_connected() and just use the ISR bits we've
stashed away.
v2: Duplicate stuff to avoid exposing platform specific
functions across files (Jani)
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/dis
From: Ville Syrjälä
No point in looping over all connectors for each hpd pin. Just loop
over each connector first and deal with each one's hpd pin. Then
loop over all the hpd pins to mark them as enabled again.
Also get rid of the MST special case as MST encoders simply don't
have a HPD pin and
From: Ville Syrjälä
Instead of constnantly having to figure out which hpd status bit
array to use let's store them under dev_priv.
Should perhaps take this further and stash even more stuff to
make the hpd handling more abstract yet.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/i915_
On 05/02/2020 16:44, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2020-02-05 16:22:34)
On 05/02/2020 12:13, Chris Wilson wrote:
If we have a set of active engines marked as being non-persistent, we
lose track of those if the user replaces those engines with
I915_CONTEXT_PARAM_ENGINES. As part
== Series Details ==
Series: drm/i915: Mark i915.reset as unsigned
URL : https://patchwork.freedesktop.org/series/73024/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7869 -> Patchwork_16435
Summary
---
**SUCCESS**
== Series Details ==
Series: series starting with [1/6] drm/i915: Hold reference to previous active
fence as we queue
URL : https://patchwork.freedesktop.org/series/72906/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7857_full -> Patchwork_16390_full
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done automati
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done automati
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion was
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion was
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion was
Device specific dev_WARN and dev_WARN_ONCE macros available in kernel
include device information in the backtrace, so we know what device
the warnings originate from.
Similar to this, add new struct drm_device based drm_WARN* macros. These
macros include device information in the backtrace, so we
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_i915_private struct pointer is readily
available.
The conversion was done automati
drm specific WARN* calls include device information in the
backtrace, so we know what device the warnings originate from.
Covert all the calls of WARN* with device specific drm_WARN*
variants in functions where drm_device or drm_i915_private struct
pointer is readily available.
The conversion was
Open access to monitoring for CAP_PERFMON privileged process.
Providing the access under CAP_PERFMON capability singly, without
the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse
the credentials and makes operation more secure.
CAP_PERFMON implements the principal of least privil
Open access to monitoring for CAP_PERFMON privileged process.
Providing the access under CAP_PERFMON capability singly, without
the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse
the credentials and makes operation more secure.
CAP_PERFMON implements the principal of least privile
Open access to monitoring for CAP_PERFMON privileged process.
Providing the access under CAP_PERFMON capability singly, without
the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse
the credentials and makes operation more secure.
CAP_PERFMON implements the principal of least privile
Open access to monitoring for CAP_PERFMON privileged process.
Providing the access under CAP_PERFMON capability singly, without
the rest of CAP_SYS_ADMIN credentials, excludes chances to misuse
the credentials and makes operation more secure.
CAP_PERFMON implements the principal of least privile
Open access to bpf_trace monitoring for CAP_PERFMON privileged process.
Providing the access under CAP_PERFMON capability singly, without the
rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the
credentials and makes operation more secure.
CAP_PERFMON implements the principal of lea
Open access to i915_perf monitoring for CAP_PERFMON privileged process.
Providing the access under CAP_PERFMON capability singly, without the
rest of CAP_SYS_ADMIN credentials, excludes chances to misuse the
credentials and makes operation more secure.
CAP_PERFMON implements the principal of lea
Extend error messages to mention CAP_PERFMON capability as an option
to substitute CAP_SYS_ADMIN capability for secure system performance
monitoring and observability operations. Make perf_event_paranoid_check()
and __cmd_ftrace() to be aware of CAP_PERFMON capability.
CAP_PERFMON implements the
Open access to monitoring via kprobes and uprobes and eBPF tracing for
CAP_PERFMON privileged process. Providing the access under CAP_PERFMON
capability singly, without the rest of CAP_SYS_ADMIN credentials, excludes
chances to misuse the credentials and makes operation more secure.
perf kprobes
Open access to monitoring of kernel code, cpus, tracepoints and namespaces
data for a CAP_PERFMON privileged process. Providing the access under
CAP_PERFMON capability singly, without the rest of CAP_SYS_ADMIN credentials,
excludes chances to misuse the credentials and makes operation more secure
Introduce CAP_PERFMON capability designed to secure system performance
monitoring and observability operations so that CAP_PERFMON would assist
CAP_SYS_ADMIN capability in its governing role for performance monitoring
and observability subsystems.
CAP_PERFMON hardens system security and integrit
Currently access to perf_events, i915_perf and other performance monitoring and
observability subsystems of the kernel is open only for a privileged process [1]
with CAP_SYS_ADMIN capability enabled in the process effective set [2].
This patch set introduces CAP_PERFMON capability designed to se
== Series Details ==
Series: drm/i915/gem: Don't leak non-persistent requests on changing engines
(rev2)
URL : https://patchwork.freedesktop.org/series/73023/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7869 -> Patchwork_16434
===
> -Original Message-
> From: Intel-gfx On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 17/17] drm/i915/psr: Use new DP VSC
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 16/17] drm/i915/dp: Add compute routine for DP P
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 15/17] drm/i915: Stop sending DP SDPs on
> intel
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 14/17] drm/i915: Program DP SDPs on pipe updates
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 13/17] drm/i915: Add state readout for DP VSC SD
> -Original Message-
> From: Intel-gfx On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 12/17] drm/i915: Add state readout f
> -Original Message-
> From: Intel-gfx On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 11/17] drm/i915: Program DP SDPs with
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 10/17] drm/i915: Include DP VSC SDP in the crtc
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 09/17] drm/i915: Include DP HDR Metadata Infofra
Quoting Tvrtko Ursulin (2020-02-05 16:22:34)
>
>
> On 05/02/2020 12:13, Chris Wilson wrote:
> > If we have a set of active engines marked as being non-persistent, we
> > lose track of those if the user replaces those engines with
> > I915_CONTEXT_PARAM_ENGINES. As part of our uABI contract is tha
== Series Details ==
Series: drm/i915: align dumb buffer stride to page_sz of the region
URL : https://patchwork.freedesktop.org/series/73021/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7869 -> Patchwork_16433
Summary
--
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 08/17] drm/i915: Include HDMI DRM infoframe in t
> -Original Message-
> From: Intel-gfx On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 07/17] drm: Add logging function for
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 06/17] drm/i915/dp: Read out DP SDPs (Secondary D
On 05/02/2020 12:13, Chris Wilson wrote:
If we have a set of active engines marked as being non-persistent, we
lose track of those if the user replaces those engines with
I915_CONTEXT_PARAM_ENGINES. As part of our uABI contract is that
non-persistent requests are terminated if they are no long
> -Original Message-
> From: Intel-gfx On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH v3 05/17] video/hdmi: Add Unpack only f
== Series Details ==
Series: series starting with [1/3] drm/i915/display: Defer application of
initial chv_phy_control
URL : https://patchwork.freedesktop.org/series/72905/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7857_full -> Patchwork_16389_full
===
> -Original Message-
> From: dri-devel On Behalf Of Gwan-
> gyeong Mun
> Sent: Tuesday, February 4, 2020 4:50 AM
> To: intel-gfx@lists.freedesktop.org
> Cc: linux-fb...@vger.kernel.org; dri-de...@lists.freedesktop.org
> Subject: [PATCH v3 04/17] drm/i915/dp: Add writing of DP SDPs (Secon
On 05/02/2020 13:48, Chris Wilson wrote:
As the kernel loses track of the context's old engines, if we request
that the context is non-persistent then any request on the untracked
engines must be cancelled.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
tests/i915/gem_ctx_persistence.c
1 - 100 of 175 matches
Mail list logo
