Quoting Chris Wilson (2020-04-23 07:29:05)
> intel_gt_wait_for_idle() tries to wait until all the outstanding requests
> are retired and the GPU is idle. As a side effect of retiring requests,
> we may submit more work to flush any pm barriers, and so the
> wait-for-idle tries to flush the backgrou
Quoting Andi Shyti (2020-04-22 23:45:29)
> Hi Chris,
>
> [...]
>
> > +static int s_many(void *arg)
> > +{
> > + struct perf_series *ps = arg;
>
> why do we need to go through void... all functions are taking a
> perf_series structure.
The kthread API defines the function pointer as int (*fn
intel_gt_wait_for_idle() tries to wait until all the outstanding requests
are retired and the GPU is idle. As a side effect of retiring requests,
we may submit more work to flush any pm barriers, and so the
wait-for-idle tries to flush the background pm work and catch the new
requests. However, if
intel_gt_wait_for_idle() tries to wait until all the outstanding requests
are retired and the GPU is idle. As a side effect of retiring requests,
we may submit more work to flush any pm barriers, and so the
wait-for-idle tries to flush the background pm work and catch the new
requests. However, if
On Wed, Apr 22, 2020 at 09:39:11AM -0300, Jason Gunthorpe wrote:
> > Nice callchain from hell.. Unfortunately such "code listings" tend to
> > get out of date very quickly, so I'm not sure it is worth keeping in
> > the code. What would be really worthile is consolidating the two
> > different se
Hi Chris,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20200422]
[cannot apply to drm-intel/for-linux-next drm-tip/drm-tip v5.7-rc2 v5.7-rc1
v5.6 v5.7-rc2]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW
Hi all,
On Tue, 21 Apr 2020 09:10:25 +0300 Tomi Valkeinen wrote:
>
> On 21/04/2020 04:52, Stephen Rothwell wrote:
> >
> > Today's linux-next merge of the drm-misc tree got a conflict in:he drm-misc
> > tree with the drm-misc-fixes tree
> >
> >drivers/gpu/drm/tidss/tidss_encoder.c
> >
> >
== Series Details ==
Series: series starting with [1/2] drm/i915/hdmi: Get digital_port only once in
intel_ddi_pre_enable_hdmi() (rev2)
URL : https://patchwork.freedesktop.org/series/76350/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8350_full -> Patchwork_17432_full
==
== Series Details ==
Series: drm/i915: Only close vma we open
URL : https://patchwork.freedesktop.org/series/76349/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350_full -> Patchwork_17429_full
Summary
---
**WARNIN
Hi Chris,
[...]
> +static int s_many(void *arg)
> +{
> + struct perf_series *ps = arg;
why do we need to go through void... all functions are taking a
perf_series structure.
> + IGT_TIMEOUT(end_time);
> + unsigned int idx = 0;
> +
[...]
> + for (idx = 0; idx < nengines
== Series Details ==
Series: series starting with [1/5] drm/i915: Make define for lrc state offset
(rev4)
URL : https://patchwork.freedesktop.org/series/76262/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350_full -> Patchwork_17427_full
== Series Details ==
Series: series starting with [v3,1/6] drm/i915: Fix skl+ non-scaled pfit modes
URL : https://patchwork.freedesktop.org/series/76346/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350_full -> Patchwork_17426_full
===
== Series Details ==
Series: series starting with [1/2] drm/i915/hdmi: Get digital_port only once in
intel_ddi_pre_enable_hdmi() (rev2)
URL : https://patchwork.freedesktop.org/series/76350/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17432
On Wed, Apr 22, 2020 at 07:19:17PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Change intel_{gmch,pch}_panel_fitting() to return a normal
> error vs. success int. We'll need this later to validate that
> the margin properties aren't misconfigured.
>
> Signed-off-by: Ville Syrjälä
Yes
On Wed, Apr 22, 2020 at 07:19:16PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Pass the entire connector state to intel_{gmch,pch}_panel_fitting().
> For now we just need to get at .scaling_mode but in the future we'll
> want access to the margin properties as well.
>
> v2: Deal with i
== Series Details ==
Series: drm/i915/gt: Warn more clearly if the context state is still pinned
URL : https://patchwork.freedesktop.org/series/76351/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17431
Su
== Series Details ==
Series: series starting with [1/2] drm/i915/hdmi: Get digital_port only once in
intel_ddi_pre_enable_hdmi()
URL : https://patchwork.freedesktop.org/series/76350/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17430
===
== Series Details ==
Series: drm/i915: Only close vma we open
URL : https://patchwork.freedesktop.org/series/76349/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17429
Summary
---
**SUCCESS**
No
On Sat, Apr 18, 2020 at 1:11 PM Rafael J. Wysocki wrote:
>
> From: "Rafael J. Wysocki"
>
> Rename DPM_FLAG_NEVER_SKIP to DPM_FLAG_NO_DIRECT_COMPLETE which
> matches its purpose more closely.
>
> No functional impact.
>
> Signed-off-by: Rafael J. Wysocki
> Acked-by: Bjorn Helgaas # for PCI parts
When recording the default context state, we submit an ordinary context
and then steal the context image for our defaults. To be able to steal
the state, we must have total ownership of the context. During CI we
want to make this error extremely obvious, as otherwise we will fail the
user's module
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and
observability (rev18)
URL : https://patchwork.freedesktop.org/series/72273/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17428
===
Quoting Mika Kuoppala (2020-04-21 15:29:32)
> We use different workarounds for render engine than
> for other engines. Split the selftest according to these
> types so that we get error rates per workaround.
>
> Signed-off-by: Mika Kuoppala
~o~
If you think it's useful,
Reviewed-by: Chris Wilso
Quoting Mika Kuoppala (2020-04-21 14:16:32)
> @@ -3290,7 +3355,7 @@ gen12_setup_timestamp_ctx_wa(struct intel_context *ce)
>
> fn = gen12_emit_timestamp_wa_lrm;
> if (ce->engine->class == RENDER_CLASS)
> - fn = gen12_emit_timestamp_wa_lrr;
> + fn = gen1
It was missing the step 7.b - "If not type-C static connection,
configure PORT_CL_DW10 Static Power Down to power up all lanes of the
DDI".
BSpec: 53339
BSpec: 49191
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_ddi.c | 10 ++
1 file changed, 10 insertions(+
Getting it only once also removing intel_hdmi that is used only once
and can be easily accessed by dig_port->hdmi.
Signed-off-by: José Roberto de Souza
---
drivers/gpu/drm/i915/display/intel_ddi.c | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/i91
Quoting Mika Kuoppala (2020-04-21 14:16:31)
> Indirect ctx batchbuffers are a hw feature of which
> batch can be run, by hardware, during context restoration stage.
> Driver can setup a batchbuffer and also an offset into the
> context image. When context image is marshalled from
> memory to regist
Quoting Mika Kuoppala (2020-04-21 14:16:30)
> Restoration of a previous timestamp can collide
> with updating the timestamp, causing a value corruption.
>
> Combat this issue by using indirect ctx bb to
> modify the context image during restoring process.
>
> For render engine, we can preload val
== Series Details ==
Series: drm/i915/execlists: Drop request-before-CS assertion
URL : https://patchwork.freedesktop.org/series/76340/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8348_full -> Patchwork_17423_full
Summary
Quoting Mika Kuoppala (2020-04-21 14:16:29)
> More often than not, we need a byte offset into lrc
> register state from the start of the hw state. Make it so.
>
> Signed-off-by: Mika Kuoppala
Reviewed-by: Chris Wilson
-Chris
___
Intel-gfx mailing list
On Wed, Apr 22, 2020 at 07:19:15PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Follow the new naming convention and call the crtc state
> "crtc_state", and while at it drop the redundant crtc argument.
>
> Signed-off-by: Ville Syrjälä
Reviewed-by: Manasi Navare
Manasi
> ---
> dri
On Wed, Apr 22, 2020 at 07:19:14PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Make things a bit more abstract by replacing the pch_pfit.pos/size
> raw register values with a drm_rect. Makes it slighly more convenient
> to eg. compute the scaling factors.
>
> v2: Use drm_rect_init()
>
== Series Details ==
Series: Introduce CAP_PERFMON to secure system performance monitoring and
observability (rev18)
URL : https://patchwork.freedesktop.org/series/72273/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f036c99151ab capabilities: Introduce CAP_PERFMON to kernel a
== Series Details ==
Series: series starting with [1/5] drm/i915: Make define for lrc state offset
(rev4)
URL : https://patchwork.freedesktop.org/series/76262/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17427
==
The history of i915_vma_close() is confusing, as is its use. As the
lifetime of the i915_vma is currently bounded by the object it is
attached to, we needed a means of identify when a vma was no longer in
use by userspace (via the user's fd). This is further complicated by
that only ppgtt vma shoul
== Series Details ==
Series: series starting with [1/5] drm/i915: Make define for lrc state offset
(rev4)
URL : https://patchwork.freedesktop.org/series/76262/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c89bc59fae80 drm/i915: Make define for lrc state offset
47e9e54a1306 dr
== Series Details ==
Series: series starting with [v3,1/6] drm/i915: Fix skl+ non-scaled pfit modes
URL : https://patchwork.freedesktop.org/series/76346/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17426
== Series Details ==
Series: series starting with [v3,1/6] drm/i915: Fix skl+ non-scaled pfit modes
URL : https://patchwork.freedesktop.org/series/76346/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9faaa25c52d4 drm/i915: Fix skl+ non-scaled pfit modes
a744ba6aef89 drm/i915: F
== Series Details ==
Series: series starting with [1/3] drm/i915/gt: Prefer soft-rc6 over RPS
DOWN_TIMEOUT (rev2)
URL : https://patchwork.freedesktop.org/series/76283/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17425
==
Hi!
On Tue, Apr 21, 2020 at 05:07:05PM -0400, Rodrigo Siqueira wrote:
> On 04/15, Maxime Ripard wrote:
> > On Mon, Oct 21, 2019 at 10:00:39PM -0300, Brian Starkey wrote:
> > > Add a test which makes commits using the writeback connector, and
> > > checks the output buffer hash to make sure it is/i
== Series Details ==
Series: drm/i915/icl: Fix timeout handling during TypeC AUX power well enabling
URL : https://patchwork.freedesktop.org/series/76336/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348_full -> Patchwork_17421_full
==
== Series Details ==
Series: series starting with [1/3] drm/i915/gt: Prefer soft-rc6 over RPS
DOWN_TIMEOUT (rev2)
URL : https://patchwork.freedesktop.org/series/76283/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
110e7737c6ac drm/i915/gt: Prefer soft-rc6 over RPS DOWN_TIMEOUT
[+Philip Yang]
Am 2020-04-21 um 8:21 p.m. schrieb Jason Gunthorpe:
> From: Jason Gunthorpe
>
> Presumably the intent here was that hmm_range_fault() could put the data
> into some HW specific format and thus avoid some work. However, nothing
> actually does that, and it isn't clear how anything a
== Series Details ==
Series: drm/i915/selftests: Verify context isolation (rev2)
URL : https://patchwork.freedesktop.org/series/76339/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8350 -> Patchwork_17424
Summary
---
== Series Details ==
Series: drm/i915/selftests: Verify context isolation (rev2)
URL : https://patchwork.freedesktop.org/series/76339/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
91ac23bb4db2 drm/i915/selftests: Verify context isolation
-:298: WARNING:LINE_SPACING: Missing a
Quoting Radhakrishna Sripada (2020-04-22 13:30:37)
> The workaround is moved from render engine context to intel_pm
> clk gating functions like the previous platforms.
Why?
> Closes: https://gitlab.freedesktop.org/drm/intel/issues/1222
Oh so you mean so that you don't actually have to test anyth
== Series Details ==
Series: Apply Wa_1406680159 as a clk_gating workaround
URL : https://patchwork.freedesktop.org/series/76334/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348_full -> Patchwork_17420_full
Summary
-
The following commit has been merged into the perf/core branch of tip:
Commit-ID: ab76878bb720cbd35a05ae868387f4373a58c949
Gitweb:
https://git.kernel.org/tip/ab76878bb720cbd35a05ae868387f4373a58c949
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:53:07 +03:00
Committ
[REQUEST]
Would it be possible for the patches that have already received Acked-by's in
this series to be accepted and applied to the tree? I lost an Acked-by (in
intel-panel.c) because it had a merge conflict with a new change that came in
after I rebased to tip. I wasn't sure earlier about accep
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 025b16f81dd7f51f29d0109399d669438c63b6ce
Gitweb:
https://git.kernel.org/tip/025b16f81dd7f51f29d0109399d669438c63b6ce
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:54:39 +03:00
Committ
Since the PWM framework is switching struct pwm_state.duty_cycle's
datatype to u64, prepare for this transition by using DIV_ROUND_UP_ULL
to handle a 64-bit dividend.
To: Jani Nikula
Cc: Joonas Lahtinen
Cc: David Airlie
Cc: Daniel Vetter
Cc: Chris Wilson
Cc: "Ville Syrjälä"
Cc: intel-gfx@lis
The following commit has been merged into the perf/core branch of tip:
Commit-ID: cea7d0d4a59b4efd0e1fe067130b4c06ab4d412f
Gitweb:
https://git.kernel.org/tip/cea7d0d4a59b4efd0e1fe067130b4c06ab4d412f
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:51:21 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: ff46758313e688fca7d762b3e6ead32843999511
Gitweb:
https://git.kernel.org/tip/ff46758313e688fca7d762b3e6ead32843999511
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:49:36 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 902a8dcc5ba6c5dc3332e8806b01be2f0f7ef2e4
Gitweb:
https://git.kernel.org/tip/902a8dcc5ba6c5dc3332e8806b01be2f0f7ef2e4
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:54:01 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 980737282232b752bb14dab96d77665c15889c36
Gitweb:
https://git.kernel.org/tip/980737282232b752bb14dab96d77665c15889c36
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:45:31 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 18aa18566218d4a46d940049b835314d2b071cc2
Gitweb:
https://git.kernel.org/tip/18aa18566218d4a46d940049b835314d2b071cc2
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:46:24 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: cf91baf3f7f39a0cd29072e21ed0e4bb1ab3b382
Gitweb:
https://git.kernel.org/tip/cf91baf3f7f39a0cd29072e21ed0e4bb1ab3b382
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:50:15 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 6b3e0e2e04615df128b2d38fa1dd1fcb84f2504c
Gitweb:
https://git.kernel.org/tip/6b3e0e2e04615df128b2d38fa1dd1fcb84f2504c
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:47:35 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: c9e0924e5c2b59365f9c0d43ff8722e79ecf4088
Gitweb:
https://git.kernel.org/tip/c9e0924e5c2b59365f9c0d43ff8722e79ecf4088
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:47:01 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 031258da05956646c5606023ab0abe10a7e68ea1
Gitweb:
https://git.kernel.org/tip/031258da05956646c5606023ab0abe10a7e68ea1
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:48:54 +03:00
Committ
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 4e3d3456b78fa5a70e65de0d7c5309b814281ae3
Gitweb:
https://git.kernel.org/tip/4e3d3456b78fa5a70e65de0d7c5309b814281ae3
Author:Alexey Budankov
AuthorDate:Thu, 02 Apr 2020 11:48:15 +03:00
Committ
On Wed, Apr 22, 2020 at 10:50:22AM +0300, Lisovskiy, Stanislav wrote:
> On Tue, Apr 21, 2020 at 07:00:38PM +0300, Ville Syrjälä wrote:
> > On Mon, Apr 20, 2020 at 02:14:10PM +0300, Stanislav Lisovskiy wrote:
> > > Future platforms require per-crtc SAGV evaluation
> > > and serializing global state
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore
MSA from DPCD
URL : https://patchwork.freedesktop.org/series/76328/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348_full -> Patchwork_17419_full
From: Ville Syrjälä
Most of the pfit functions are of the form:
func()
{
if (pfit_enabled) {
...
}
}
Flip the pfit_enabled check around to flatten the functions.
And while we're touching all this let's do the usual
s/pipe_config/crtc_state/ replacement.
Reviewe
From: Ville Syrjälä
Follow the new naming convention and call the crtc state
"crtc_state", and while at it drop the redundant crtc argument.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/icl_dsi.c | 3 +-
drivers/gpu/drm/i915/display/intel_dp.c| 8 +-
drivers/gpu/drm/
From: Ville Syrjälä
Fix skl_update_scaler_crtc() to deal with different scaling
modes correctly. The current implementation assumes
DRM_MODE_SCALE_FULLSCREEN. Fortunately we don't expose any
border properties currently so the code does actually end
up doing the right thing (assigning a scaler for
From: Ville Syrjälä
Make things a bit more abstract by replacing the pch_pfit.pos/size
raw register values with a drm_rect. Makes it slighly more convenient
to eg. compute the scaling factors.
v2: Use drm_rect_init()
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_display.
From: Ville Syrjälä
Change intel_{gmch,pch}_panel_fitting() to return a normal
error vs. success int. We'll need this later to validate that
the margin properties aren't misconfigured.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/icl_dsi.c | 10 +++---
drivers/gpu/drm/
From: Ville Syrjälä
Pass the entire connector state to intel_{gmch,pch}_panel_fitting().
For now we just need to get at .scaling_mode but in the future we'll
want access to the margin properties as well.
v2: Deal with intel_dp_ycbcr420_config()
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm
No unprivileged context should ever be allowed to modify state that is
visible to another; there should be no backchannels available or control
leakage for malicious actors.
This test tries to write to a set of random registers using
non-privileged instructions (ala userspace). It should only be a
Chris Wilson writes:
> When we migrated to execlists, one of the conditions we wanted to test
> for was whether the breadcrumb seqno was being written before the
> breadcumb interrupt was delivered. This was following on from issues
> observed on previous generations which were not so strong orde
== Series Details ==
Series: drm/i915/execlists: Drop request-before-CS assertion
URL : https://patchwork.freedesktop.org/series/76340/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17423
Summary
---
On Wed, 2020-04-22 at 15:34 +0300, Imre Deak wrote:
> Fix the check for when an AUX power well enabling timeout is expected
> on
> a legacy TypeC port.
>
> Fixes: 89e01caac641 ("drm/i915: Use single set of AUX powerwell ops
> for gen11+")
Reviewed-by: José Roberto de Souza
> Cc: Matt Roper
> C
== Series Details ==
Series: drm/i915/execlists: Drop request-before-CS assertion
URL : https://patchwork.freedesktop.org/series/76340/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ab29e29e07bc drm/i915/execlists: Drop request-before-CS assertion
-:11: WARNING:TYPO_SPELLING: '
== Series Details ==
Series: drm/i915/selftests: Verify context isolation
URL : https://patchwork.freedesktop.org/series/76339/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17422
Summary
---
**FAIL
== Series Details ==
Series: perf/core: Only copy-to-user after completely unlocking all locks, v3.
URL : https://patchwork.freedesktop.org/series/76325/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348_full -> Patchwork_17418_full
===
On 21/04/2020 17:41, Chris Wilson wrote:
Normally when we create a new context, and a new ppGTT to go with it, we
point all the unused pages in the ppGTT to a 'safe' scratch page. Any
inadvertent access outside of the declared user's area will result in a
read/write to scratch instead. However,
When we migrated to execlists, one of the conditions we wanted to test
for was whether the breadcrumb seqno was being written before the
breadcumb interrupt was delivered. This was following on from issues
observed on previous generations which were not so strong ordered. With
the removal of the mi
Chris Wilson writes:
> Since batch buffers dominant execution time, most preemption requests
> should naturally occur during execution of a batch buffer. We wish to
> verify that should a preemption occur within a batch buffer, when we
> come to restart that batch buffer, it occurs at the interru
On 22/04/2020 08:20, Chris Wilson wrote:
While the ggtt vma are protected by their object lifetime, the list
continues until it hits a non-ggtt vma, and that vma is not protected
and may be freed as we inspect it. Hence, we require the obj->vma.lock
to protect the list as we iterate.
An exampl
== Series Details ==
Series: drm/i915/selftests: Verify context isolation
URL : https://patchwork.freedesktop.org/series/76339/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e6764a40a77b drm/i915/selftests: Verify context isolation
-:275: WARNING:LINE_SPACING: Missing a blank l
== Series Details ==
Series: drm/i915/icl: Fix timeout handling during TypeC AUX power well enabling
URL : https://patchwork.freedesktop.org/series/76336/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17421
No unprivileged context should ever be allowed to modify state that is
visible to another; there should be no backchannels available or control
leakage for malicious actors.
This test tries to write to a set of random registers using
non-privileged instructions (ala userspace). It should only be a
== Series Details ==
Series: Apply Wa_1406680159 as a clk_gating workaround
URL : https://patchwork.freedesktop.org/series/76334/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17420
Summary
---
**SU
== Series Details ==
Series: drm/i915/selftests: Try to detect rollback during batchbuffer
preemption (rev2)
URL : https://patchwork.freedesktop.org/series/76279/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348_full -> Patchwork_17417_full
=
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore
MSA from DPCD
URL : https://patchwork.freedesktop.org/series/76328/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17419
==
Fix the check for when an AUX power well enabling timeout is expected on
a legacy TypeC port.
Fixes: 89e01caac641 ("drm/i915: Use single set of AUX powerwell ops for gen11+")
Cc: Matt Roper
Cc: José Roberto de Souza
Signed-off-by: Imre Deak
---
.../drm/i915/display/intel_display_power.c| 7
The workaround is moved from render engine context to intel_pm
clk gating functions like the previous platforms.
Closes: https://gitlab.freedesktop.org/drm/intel/issues/1222
Fixes: fb899dd8ea9c ("drm/i915: Apply Wa_1406680159:icl,ehl as an engine
workaround")
Cc: Matt Atwood
Cc: Matt Roper
Sign
This is a one patch series that moves the WA from RCS WA's list to
clock gating WA's in intel_pm.c
Test-with: 20200228104340.2895082-2-ch...@chris-wilson.co.uk
Radhakrishna Sripada (1):
drm/i915: Apply Wa_1406680159 as a clk_gating workaround
drivers/gpu/drm/i915/gt/intel_workarounds.c | 5 -
== Series Details ==
Series: series starting with [v5,1/3] drm/dp: DRM DP helper for reading Ignore
MSA from DPCD
URL : https://patchwork.freedesktop.org/series/76328/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
1e772a99285c drm/dp: DRM DP helper for reading Ignore MSA from
== Series Details ==
Series: perf/core: Only copy-to-user after completely unlocking all locks, v3.
URL : https://patchwork.freedesktop.org/series/76325/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17418
== Series Details ==
Series: perf/core: Only copy-to-user after completely unlocking all locks, v3.
URL : https://patchwork.freedesktop.org/series/76325/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
1eec2217d858 perf/core: Only copy-to-user after completely unlocking all locks
== Series Details ==
Series: drm/i915/selftests: Try to detect rollback during batchbuffer
preemption (rev2)
URL : https://patchwork.freedesktop.org/series/76279/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8348 -> Patchwork_17417
===
== Series Details ==
Series: drm/i915/selftests: Disable heartbeat around RPS interrupt testing
URL : https://patchwork.freedesktop.org/series/76312/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8347_full -> Patchwork_17415_full
===
From: Manasi Navare
From: Manasi Navare
DP sink device sets the Ignore MSA bit in its
DP_DOWNSTREAM_PORT_COUNT register to indicate its ability to
ignore the MSA video timing parameters and its ability to support
seamless video timing change over a range of timing exposed by
DisplayID and EDID.
From: Aditya Swarup
From: Aditya Swarup
This function sets the VRR property for connector based
on the platform support, EDID monitor range and DP sink
DPCD capability of outputing video without msa
timing information.
v4:
* Rebase (Mansi)
v3:
* intel_dp_is_vrr_capable can be used for debugfs,
From: Bhanuprakash Modem
[Why]
It's useful to know the min and max vrr range for IGT testing.
[How]
Expose the min and max vfreq for the connector via a debugfs file
on the connector, "vrr_range".
Example usage: cat /sys/kernel/debug/dri/0/DP-1/vrr_range
v4:
* Rebase (Bhanu)
* Remove "Vrr_capa
We inadvertently create a dependency on mmap_sem with a whole chain.
This breaks any user who wants to take a lock and call rcu_barrier(),
while also taking that lock inside mmap_sem:
<4> [604.892532] ==
<4> [604.892534] WARNING: possible circul
Tasklet scheduling can unfortunately be quite predicated. Where we are
only caring about workload distribution and not initial execution
latency (see kick_kthreads), make that kick more precise.
Signed-off-by: Chris Wilson
---
lib/igt_debugfs.h | 7 +++
tests/i915/gem_exec_bala
We have allowed the CPU 2s to process the hang and cleanup; but clearly
this is not always enough. Let's just give the CPU one last kick before
declaring that we have an issue, to try and be sure that we have a bug
to fix before worrying.
References: https://gitlab.freedesktop.org/drm/intel/issues
Quoting Patchwork (2020-04-22 11:03:39)
> Possible regressions
>
> * igt@i915_module_load@reload:
> - fi-ivb-3770:[PASS][1] -> [INCOMPLETE][2]
>[1]:
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8347/fi-ivb-3770/igt@i915_module_l...@reload.html
>[2]:
> https:/
1 - 100 of 115 matches
Mail list logo
