Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [CI,1/9] drm/i915/preempt: Fix WaEnablePreemptionGranularityControlByUMD

On Wed, Oct 04, 2017 at 07:41:15PM -, Patchwork wrote: > == Series Details == > > Series: series starting with [CI,1/9] drm/i915/preempt: Fix > WaEnablePreemptionGranularityControlByUMD > URL : https://patchwork.freedesktop.org/series/31394/ > State : failure > > == Summary == > > Test

[Intel-gfx] ✗ Fi.CI.IGT: warning for series starting with [v2,1/2] drm/i915: Runtime disable for eDP DRRS (rev3)

== Series Details == Series: series starting with [v2,1/2] drm/i915: Runtime disable for eDP DRRS (rev3) URL : https://patchwork.freedesktop.org/series/32887/ State : warning == Summary == Test kms_setmode: Subgroup basic: fail -> PASS (shard-hsw)

Re: [Intel-gfx] [PATCH v16 5/6] vfio: ABI for mdev display dma-buf operation

Hi, > Should we then specify the error code for "head doesn't exist" vs > "head > doesn't support dmabuf", with the former taking precedence?  Perhaps > -ENODEV vs -EINVAL. NODEV for "head doesn't exist" and INVAL for "head doesn't support dmabuf/region/..." ? > Are the heads guaranteed to be

Re: [Intel-gfx] [PATCH] tests/kms_plane_scaling: Enhanced plane scaler test case.

Regards, Nabendu > -Original Message- > From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of > Yadav Jyoti > Sent: Tuesday, November 7, 2017 9:19 AM > To: intel-gfx@lists.freedesktop.org > Cc: daniel.vet...@ffwll.ch; Srinivas, Vidya >

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/crt: Silence compiler warning for uninitialised status

== Series Details == Series: drm/i915/crt: Silence compiler warning for uninitialised status URL : https://patchwork.freedesktop.org/series/33365/ State : failure == Summary == Series 33365v1 drm/i915/crt: Silence compiler warning for uninitialised status

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Ignore frequent clang warnings

== Series Details == Series: drm/i915: Ignore frequent clang warnings URL : https://patchwork.freedesktop.org/series/33366/ State : failure == Summary == Series 33366v1 drm/i915: Ignore frequent clang warnings https://patchwork.freedesktop.org/api/1.0/series/33366/revisions/1/mbox/ Test

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Prune the reservation shared fence array (rev3)

== Series Details == Series: drm/i915: Prune the reservation shared fence array (rev3) URL : https://patchwork.freedesktop.org/series/15254/ State : failure == Summary == Series 15254v3 drm/i915: Prune the reservation shared fence array

Re: [Intel-gfx] [PATCH v6 1/3] drm/i915: Add Guc/HuC firmware details to error state

On Mon, 2017-11-06 at 14:15 +, Chris Wilson wrote: > Quoting Michal Wajdeczko (2017-10-26 18:36:55) > > Include GuC and HuC firmware details in captured error state > > to provide additional debug information. To reuse existing > > uc firmware pretty printer, introduce new drm-printer variant

[Intel-gfx] [PATCH i-g-t 2/5] aubdump: Avoid mixing declarations and code

From: Tvrtko Ursulin Avoids the build warning about ISO C90 forbiding mixing the two. Signed-off-by: Tvrtko Ursulin --- tools/aubdump.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/tools/aubdump.c

[Intel-gfx] [PATCH i-g-t 5/5] intel_gvtg_test: Handle system(3) return value.

From: Tvrtko Ursulin Avoid the build warning by checking the pkill either did not find any guests or managed to send a signal to all of them. Signed-off-by: Tvrtko Ursulin --- tools/intel_gvtg_test.c | 4 +++- 1 file changed, 3

[Intel-gfx] [PATCH] drm/i915: Use trace_printk to provide a death rattle for GEM

Trying to enable printk debugging for GEM is fraught with the issue of spam; interactions with HW are very frequent and often boring. However, one instance where they are not so boring is just before a BUG; here ftrace provides a facility to dump its ringbuffer on an oops. So for CI let's enable

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT (rev2)

== Series Details == Series: drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT (rev2) URL : https://patchwork.freedesktop.org/series/33380/ State : success == Summary == Series 33380v2 drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT

Re: [Intel-gfx] [PATCH i-g-t 5/5] intel_gvtg_test: Handle system(3) return value.

Quoting Tvrtko Ursulin (2017-11-08 12:06:54) > From: Tvrtko Ursulin > > Avoid the build warning by checking the pkill either did not find > any guests or managed to send a signal to all of them. > > Signed-off-by: Tvrtko Ursulin > --- >

Re: [Intel-gfx] [PATCH v6 1/3] drm/i915: Add Guc/HuC firmware details to error state

On Wed, 08 Nov 2017 12:27:20 +0100, Joonas Lahtinen wrote: On Mon, 2017-11-06 at 14:15 +, Chris Wilson wrote: Quoting Michal Wajdeczko (2017-10-26 18:36:55) > Include GuC and HuC firmware details in captured error state > to provide additional debug

Re: [Intel-gfx] [PATCH] ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock

On Wed, Nov 08, 2017 at 01:23:56PM +0100, Rafael J. Wysocki wrote: > On Wed, Nov 8, 2017 at 12:06 AM, Rafael J. Wysocki wrote: > > On Tuesday, November 7, 2017 11:47:54 PM CET Rafael J. Wysocki wrote: > >> On Tue, Nov 7, 2017 at 10:08 PM, Ville Syrjala > >>

Re: [Intel-gfx] [PATCH i-g-t 5/5] intel_gvtg_test: Handle system(3) return value.

On 08/11/2017 12:19, Chris Wilson wrote: Quoting Tvrtko Ursulin (2017-11-08 12:06:54) From: Tvrtko Ursulin Avoid the build warning by checking the pkill either did not find any guests or managed to send a signal to all of them. Signed-off-by: Tvrtko Ursulin

Re: [Intel-gfx] [PATCH] drm/i915: sync dp link status checks against atomic commmits

On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote: > On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote: > > Two bits: > > - check actual atomic state, the legacy stuff can only be looked at > > from within the atomic_commit_tail function, since it's only > > protected

Re: [Intel-gfx] [PATCH] drm/i915: sync dp link status checks against atomic commmits

On Wed, Nov 08, 2017 at 03:26:15PM +0200, Ville Syrjälä wrote: > On Wed, Nov 08, 2017 at 02:11:46PM +0100, Daniel Vetter wrote: > > On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote: > > > On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote: > > > > Two bits: > > > > - check

[Intel-gfx] [PATCH i-g-t] gem_ctx_param: Update for context priorities

From: Tvrtko Ursulin Update the test to check for context priority get and set and at the same time bump the invalid flag tests. Signed-off-by: Tvrtko Ursulin Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103107 Cc: Daniel Vetter

Re: [Intel-gfx] [PATCH] drm/i915: Include engine state on detecting a missed breadcrumb/seqno

Quoting Chris Wilson (2017-11-08 10:07:46) > Now that we have a common engine state pretty printer, we can use that > instead of the adhoc information printed when we miss a breadcrumb. > > Signed-off-by: Chris Wilson > Cc: Mika Kuoppala > Cc:

Re: [Intel-gfx] [PATCH] gem_ctx_param: Update for context priorities

On 08/11/2017 10:11, Daniel Vetter wrote: On Wed, Nov 08, 2017 at 09:47:20AM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Update the test to check for context priority get and set and at the same time bump the invalid flag tests. Signed-off-by: Tvrtko Ursulin

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/atomic-helper: always track connector commits, too

== Series Details == Series: series starting with [1/2] drm/atomic-helper: always track connector commits, too URL : https://patchwork.freedesktop.org/series/33410/ State : success == Summary == Series 33410v1 series starting with [1/2] drm/atomic-helper: always track connector commits, too

[Intel-gfx] [PATCH igt] lib: Always enable ftrace-dump-on-oops

Some debugging information is too voluminous to enable by default, yet may be invaluable when it comes to post-mortem debugging. trace_printk() provides the facility for the trace ringbuffer to be dumped on oops, this way we can cheaply spam the debug log and only present it in case of emergency.

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited

== Series Details == Series: series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited URL : https://patchwork.freedesktop.org/series/33395/ State : warning == Summary == Series 33395v1 series starting with [(resend),1/3] drm/i915: Ignore previous

Re: [Intel-gfx] [PATCH] drm/i915: Include intel_engine_is_idle() status in engine pretty-printer

On Tue, 2017-11-07 at 15:22 +, Chris Wilson wrote: > Upon parking, if we discover an active engine we dump its state. Follow > that state with an indication of whether the engine was idle. > > References: https://bugs.freedesktop.org/show_bug.cgi?id=103479 > Signed-off-by: Chris Wilson

[Intel-gfx] [PATCH] drm/i915: sync dp link status checks against atomic commmits

Two bits: - check actual atomic state, the legacy stuff can only be looked at from within the atomic_commit_tail function, since it's only protected by ordering and not by any locks. - Make sure we don't wreak the work an ongoing nonblocking commit is doing. v2: We need the crtc lock too,

Re: [Intel-gfx] [PATCH] drm/i915: Remove support for legacy debugfs crc interface

Op 02-11-17 om 17:11 schreef Ville Syrjälä: > On Thu, Nov 02, 2017 at 05:19:07PM +0200, Jani Nikula wrote: >> On Thu, 02 Nov 2017, Ville Syrjälä wrote: >>> On Thu, Nov 02, 2017 at 02:56:51PM +0100, Maarten Lankhorst wrote: This interface is deprecated, and has

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited

== Series Details == Series: series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited URL : https://patchwork.freedesktop.org/series/33395/ State : success == Summary == Series 33395v1 series starting with [(resend),1/3] drm/i915: Ignore previous

[Intel-gfx] [PATCH i-g-t 1/5] intel-gpu-overlay: Avoid theoretical string overflow

From: Tvrtko Ursulin GCC 7 notices a theoretical string overflow. Use snprintf and increase the buffer to avoid that. Signed-off-by: Tvrtko Ursulin --- overlay/overlay.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[Intel-gfx] [PATCH i-g-t 3/5] lib/core: Avoid unused result in backtrace printing

From: Tvrtko Ursulin Add helpers for direct write to stderr to consolidate the code and avoid the unused result warning in build. v2: Use igt_ignore_warn since it is questionable whether igt_assert is safe in signal handlers. (Chris Wilson) Signed-off-by: Tvrtko

[Intel-gfx] [PATCH i-g-t 4/5] gem_syslatency: Avoid arithmetic on void * warning

From: Tvrtko Ursulin Signed-off-by: Tvrtko Ursulin --- benchmarks/gem_syslatency.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/benchmarks/gem_syslatency.c b/benchmarks/gem_syslatency.c index e2b1f74a43f4..580edc5f5c72

[Intel-gfx] [PATCH i-g-t 0/5] Assorted compile warnings fixes

From: Tvrtko Ursulin As the subject says. Even if some are not perfect I doubt they make anything worse. Tvrtko Ursulin (5): intel-gpu-overlay: Avoid theoretical string overflow aubdump: Avoid mixing declarations and code lib/core: Avoid unused result in

Re: [Intel-gfx] [PATCH i-g-t 1/5] intel-gpu-overlay: Avoid theoretical string overflow

On Wed, Nov 08, 2017 at 12:06:50PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > GCC 7 notices a theoretical string overflow. Use snprintf and increase > the buffer to avoid that. > > Signed-off-by: Tvrtko Ursulin Reviewed-by:

Re: [Intel-gfx] [PATCH igt] lib: Always enable ftrace-dump-on-oops

Quoting Petri Latvala (2017-11-08 12:32:09) > On Wed, Nov 08, 2017 at 12:18:40PM +, Chris Wilson wrote: > > Some debugging information is too voluminous to enable by default, yet > > may be invaluable when it comes to post-mortem debugging. trace_printk() > > provides the facility for the

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Idle the GPU before shinking everything (rev2)

== Series Details == Series: drm/i915: Idle the GPU before shinking everything (rev2) URL : https://patchwork.freedesktop.org/series/33373/ State : success == Summary == Test perf: Subgroup polling: pass -> FAIL (shard-hsw) fdo#102252 Test kms_busy:

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Include engine state on detecting a missed breadcrumb/seqno

== Series Details == Series: drm/i915: Include engine state on detecting a missed breadcrumb/seqno URL : https://patchwork.freedesktop.org/series/33407/ State : failure == Summary == Series 33407 revision 1 was fully merged or fully failed: no git log

[Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

--- drivers/gpu/drm/i915/intel_display.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c index 39d1f30cd0c4..436374b08b69 100644 --- a/drivers/gpu/drm/i915/intel_display.c +++ b/drivers/gpu/drm/i915/intel_display.c

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Idle the GPU before shinking everything (rev2)

== Series Details == Series: drm/i915: Idle the GPU before shinking everything (rev2) URL : https://patchwork.freedesktop.org/series/33373/ State : failure == Summary == Series 33373v2 drm/i915: Idle the GPU before shinking everything

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Idle the GPU before shinking everything (rev2)

== Series Details == Series: drm/i915: Idle the GPU before shinking everything (rev2) URL : https://patchwork.freedesktop.org/series/33373/ State : success == Summary == Series 33373v2 drm/i915: Idle the GPU before shinking everything

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited

== Series Details == Series: series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited URL : https://patchwork.freedesktop.org/series/33395/ State : warning == Summary == Series 33395v1 series starting with [(resend),1/3] drm/i915: Ignore previous

Re: [Intel-gfx] [PATCH i-g-t 4/5] gem_syslatency: Avoid arithmetic on void * warning

On Wed, Nov 08, 2017 at 12:06:53PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Signed-off-by: Tvrtko Ursulin Chris wanted to disable the warning here instead. Either way is fine with me so Reviewed-by: Petri Latvala

[Intel-gfx] ✓ Fi.CI.BAT: success for Add Plane Color Properties (rev2)

== Series Details == Series: Add Plane Color Properties (rev2) URL : https://patchwork.freedesktop.org/series/30875/ State : success == Summary == Series 30875v2 Add Plane Color Properties https://patchwork.freedesktop.org/api/1.0/series/30875/revisions/2/mbox/ Test chamelium:

Re: [Intel-gfx] [PATCH] ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock

On Wednesday, November 8, 2017 1:31:22 PM CET Ville Syrjälä wrote: > On Wed, Nov 08, 2017 at 01:23:56PM +0100, Rafael J. Wysocki wrote: > > On Wed, Nov 8, 2017 at 12:06 AM, Rafael J. Wysocki > > wrote: > > > On Tuesday, November 7, 2017 11:47:54 PM CET Rafael J. Wysocki

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Read ilk FDI PLL frequency once during initialisation (rev2)

== Series Details == Series: drm/i915: Read ilk FDI PLL frequency once during initialisation (rev2) URL : https://patchwork.freedesktop.org/series/33210/ State : success == Summary == shard-hswtotal:2540 pass:1432 dwarn:1 dfail:0 fail:10 skip:1097 time:9230s == Logs == For

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Idle the GPU before shinking everything (rev2)

== Series Details == Series: drm/i915: Idle the GPU before shinking everything (rev2) URL : https://patchwork.freedesktop.org/series/33373/ State : success == Summary == Series 33373v2 drm/i915: Idle the GPU before shinking everything

Re: [Intel-gfx] [PATCH 06/11] drm/i915: Save all MMIO WAs and apply them at a later time

On Fri, 2017-11-03 at 15:56 -0700, Oscar Mateo wrote: > > On 10/16/2017 03:34 AM, Joonas Lahtinen wrote: > > On Fri, 2017-10-13 at 13:49 -0700, Oscar Mateo wrote: > > > On 10/12/2017 03:35 AM, Joonas Lahtinen wrote: > > > > On Wed, 2017-10-11 at 11:15 -0700, Oscar Mateo wrote: > > > > > By doing

[Intel-gfx] [PATCH igt] lib: Always enable ftrace-dump-on-oops

Some debugging information is too voluminous to enable by default, yet may be invaluable when it comes to post-mortem debugging. trace_printk() provides the facility for the trace ringbuffer to be dumped on oops, this way we can cheaply spam the debug log and only present it in case of emergency.

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/crt: Silence compiler warning for uninitialised status

== Series Details == Series: drm/i915/crt: Silence compiler warning for uninitialised status URL : https://patchwork.freedesktop.org/series/33365/ State : success == Summary == Series 33365v1 drm/i915/crt: Silence compiler warning for uninitialised status

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Ignore frequent clang warnings

== Series Details == Series: drm/i915: Ignore frequent clang warnings URL : https://patchwork.freedesktop.org/series/33366/ State : success == Summary == Series 33366v1 drm/i915: Ignore frequent clang warnings https://patchwork.freedesktop.org/api/1.0/series/33366/revisions/1/mbox/ Test

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [1/2] drm/i915: implemented dynamic WOPCM partition.

== Series Details == Series: series starting with [1/2] drm/i915: implemented dynamic WOPCM partition. URL : https://patchwork.freedesktop.org/series/33165/ State : warning == Summary == Series 33165v1 series starting with [1/2] drm/i915: implemented dynamic WOPCM partition.

Re: [Intel-gfx] [PATCH igt] lib: Always enable ftrace-dump-on-oops

On Wed, Nov 08, 2017 at 12:36:32PM +, Chris Wilson wrote: > Quoting Petri Latvala (2017-11-08 12:32:09) > > On Wed, Nov 08, 2017 at 12:18:40PM +, Chris Wilson wrote: > > > Some debugging information is too voluminous to enable by default, yet > > > may be invaluable when it comes to

[Intel-gfx] [PATCH i-g-t v2] intel_gvtg_test: Handle system(3) return value.

From: Tvrtko Ursulin Avoid the build warning by checking the pkill either did not find any guests or managed to send a signal to all of them. v2: Inspect system(3) return value properly. (Petri Latvala) Signed-off-by: Tvrtko Ursulin ---

Re: [Intel-gfx] [PATCH] drm/i915: sync dp link status checks against atomic commmits

On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote: > Two bits: > - check actual atomic state, the legacy stuff can only be looked at > from within the atomic_commit_tail function, since it's only > protected by ordering and not by any locks. > > - Make sure we don't wreak the work

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

Please use trybot (i.e. send patches to intel-gfx-try...@lists.freedesktop.org) for hacks that aren't intended for upstream. Then they can be prioritized appropriately. BR, Jani. On Wed, 08 Nov 2017, Maarten Lankhorst wrote: > --- >

Re: [Intel-gfx] [PATCH] drm/i915: sync dp link status checks against atomic commmits

Op 08-11-17 om 14:04 schreef Ville Syrjälä: > On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote: >> Two bits: >> - check actual atomic state, the legacy stuff can only be looked at >> from within the atomic_commit_tail function, since it's only >> protected by ordering and not by

Re: [Intel-gfx] [PATCH] gem_ctx_param: Update for context priorities

On Wed, Nov 08, 2017 at 09:47:20AM +, Tvrtko Ursulin wrote: Subject: [Intel-gfx] [PATCH] gem_ctx_param: Update for context priorities Can you resend with PATCH i-g-t so this gets to the correct patchwork? -- Petri Latvala ___ Intel-gfx mailing

[Intel-gfx] [PATCH] drm/i915: Include engine state on detecting a missed breadcrumb/seqno

Now that we have a common engine state pretty printer, we can use that instead of the adhoc information printed when we miss a breadcrumb. Signed-off-by: Chris Wilson Cc: Mika Kuoppala Cc: Tvrtko Ursulin ---

Re: [Intel-gfx] [PATCH v2] drm/i915: Read ilk FDI PLL frequency once during initialisation

On Tue, Nov 07, 2017 at 09:47:13PM +, Chris Wilson wrote: > During intel_atomic_check(), we do not take the intel_runtime_pm_get() > wakeref and so should do the atomic modeset precalculations without > referring to the HW. However, on Ironlake we see > > <7>[ 23.487557]

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/atomic-helper: always track connector commits, too

== Series Details == Series: series starting with [1/2] drm/atomic-helper: always track connector commits, too URL : https://patchwork.freedesktop.org/series/33410/ State : failure == Summary == Series 33410v1 series starting with [1/2] drm/atomic-helper: always track connector commits, too

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Generalize transcoder looping (rev2)

== Series Details == Series: drm/i915: Generalize transcoder looping (rev2) URL : https://patchwork.freedesktop.org/series/32965/ State : success == Summary == Series 32965v2 drm/i915: Generalize transcoder looping https://patchwork.freedesktop.org/api/1.0/series/32965/revisions/2/mbox/

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/vblanks: Deal with HW vblank counter resets.

== Series Details == Series: drm/vblanks: Deal with HW vblank counter resets. URL : https://patchwork.freedesktop.org/series/33316/ State : success == Summary == Series 33316v1 drm/vblanks: Deal with HW vblank counter resets.

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/8] drm/i915: Assert guc->stage_desc_pool is allocated

== Series Details == Series: series starting with [CI,1/8] drm/i915: Assert guc->stage_desc_pool is allocated URL : https://patchwork.freedesktop.org/series/33254/ State : success == Summary == Series 33254v1 series starting with [CI,1/8] drm/i915: Assert guc->stage_desc_pool is allocated

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister

== Series Details == Series: series starting with [v5,1/2] x86/platform/intel/iosf_mbi: Add unlocked PMIC bus access notifier unregister URL : https://patchwork.freedesktop.org/series/32288/ State : success == Summary == Series 32288v1 series starting with [v5,1/2]

Re: [Intel-gfx] [PATCH] ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock

On Wed, Nov 8, 2017 at 1:41 PM, Rafael J. Wysocki wrote: > On Wednesday, November 8, 2017 1:31:22 PM CET Ville Syrjälä wrote: >> On Wed, Nov 08, 2017 at 01:23:56PM +0100, Rafael J. Wysocki wrote: >> > On Wed, Nov 8, 2017 at 12:06 AM, Rafael J. Wysocki >>

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT (rev2)

== Series Details == Series: drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT (rev2) URL : https://patchwork.freedesktop.org/series/33380/ State : failure == Summary == Series 33380v2 drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT

[Intel-gfx] [PATCH 1/2] drm/atomic-helper: always track connector commits, too

It's useful for syncing async connector work like link retraining. Cc: Manasi Navare Cc: Maarten Lankhorst Cc: Ville Syrjälä Signed-off-by: Daniel Vetter ---

[Intel-gfx] [PATCH 2/2] drm/i915: sync dp link status checks against atomic commmits

Two bits: - check actual atomic state, the legacy stuff can only be looked at from within the atomic_commit_tail function, since it's only protected by ordering and not by any locks. - Make sure we don't wreak the work an ongoing nonblocking commit is doing. Cc: Manasi Navare

[Intel-gfx] ✗ Fi.CI.BAT: warning for series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited

== Series Details == Series: series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited URL : https://patchwork.freedesktop.org/series/33395/ State : warning == Summary == Series 33395v1 series starting with [(resend),1/3] drm/i915: Ignore previous

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/atomic-helper: always track connector commits, too

== Series Details == Series: series starting with [1/2] drm/atomic-helper: always track connector commits, too URL : https://patchwork.freedesktop.org/series/33410/ State : failure == Summary == Series 33410v1 series starting with [1/2] drm/atomic-helper: always track connector commits, too

Re: [Intel-gfx] [PATCH] drm/i915/gen9: Add WaVFEStateAfterPipeControlwithMediaStateClear

s/Arun/Jeff + Jon/ This W/A would seem to be breaking context isolation as it is not context saved. Thus it is a candidate for being removed. I have to say I did not get any wiser from reading the HSD, so can you guys bring some insight here? Regards, Joonas On Wed, 2017-11-01 at 22:44

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm: i915: remove timeval users

On Wed, Nov 08, 2017 at 02:01:12PM +0100, Arnd Bergmann wrote: > On Wed, Nov 8, 2017 at 1:31 PM, Patchwork > wrote: > > == Series Details == > > > > Series: drm: i915: remove timeval users > > URL : https://patchwork.freedesktop.org/series/33147/ > > State :

Re: [Intel-gfx] [PATCH] gem_ctx_param: Update for context priorities

On Wed, Nov 08, 2017 at 09:47:20AM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Update the test to check for context priority get and set and at the same > time bump the invalid flag tests. > > Signed-off-by: Tvrtko Ursulin >

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited

== Series Details == Series: series starting with [(resend),1/3] drm/i915: Ignore previous watermarks on ILK if inherited URL : https://patchwork.freedesktop.org/series/33395/ State : success == Summary == shard-hswtotal:2540 pass:1431 dwarn:2 dfail:0 fail:10 skip:1097

Re: [Intel-gfx] [PATCH] drm/i915: Remove support for legacy debugfs crc interface

On Wed, Nov 08, 2017 at 11:40:19AM +0100, Maarten Lankhorst wrote: > Op 02-11-17 om 17:11 schreef Ville Syrjälä: > > On Thu, Nov 02, 2017 at 05:19:07PM +0200, Jani Nikula wrote: > >> On Thu, 02 Nov 2017, Ville Syrjälä wrote: > >>> On Thu, Nov 02, 2017 at 02:56:51PM

Re: [Intel-gfx] [PATCH] gem_ctx_param: Update for context priorities

On Wed, Nov 08, 2017 at 10:24:50AM +, Tvrtko Ursulin wrote: > > On 08/11/2017 10:11, Daniel Vetter wrote: > > On Wed, Nov 08, 2017 at 09:47:20AM +, Tvrtko Ursulin wrote: > > > From: Tvrtko Ursulin > > > > > > Update the test to check for context priority get

[Intel-gfx] ✓ Fi.CI.BAT: success for ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock

== Series Details == Series: ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock URL : https://patchwork.freedesktop.org/series/33372/ State : success == Summary == Series 33372v1 ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock

Re: [Intel-gfx] [PATCH i-g-t 5/5] intel_gvtg_test: Handle system(3) return value.

On Wed, Nov 08, 2017 at 12:06:54PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Avoid the build warning by checking the pkill either did not find > any guests or managed to send a signal to all of them. > > Signed-off-by: Tvrtko Ursulin

Re: [Intel-gfx] [PATCH i-g-t v2] intel_gvtg_test: Handle system(3) return value.

On Wed, Nov 08, 2017 at 12:47:43PM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Avoid the build warning by checking the pkill either did not find > any guests or managed to send a signal to all of them. > > v2: Inspect system(3) return value properly. (Petri

Re: [Intel-gfx] [PATCH] ACPI / PM: Fix acpi_pm_notifier_lock vs. flush_workqueue() deadlock

On Wed, Nov 08, 2017 at 01:41:06PM +0100, Rafael J. Wysocki wrote: > On Wednesday, November 8, 2017 1:31:22 PM CET Ville Syrjälä wrote: > > On Wed, Nov 08, 2017 at 01:23:56PM +0100, Rafael J. Wysocki wrote: > > > On Wed, Nov 8, 2017 at 12:06 AM, Rafael J. Wysocki > > > wrote:

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

Hi Dave, drm-misc-next-fixes-2017-11-08: 4.15 merge window fixes, round 2: randconfig fix from Arnd, plus the vblank WARN_ON fix from Ville. Right away a new pull request because somehow Ville's fix was stuck for a bit too long and everyone forgot :-( And I didn't notice because i915 isn't

Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm: i915: remove timeval users

On Wed, Nov 8, 2017 at 1:31 PM, Patchwork wrote: > == Series Details == > > Series: drm: i915: remove timeval users > URL : https://patchwork.freedesktop.org/series/33147/ > State : failure > For more details see:

Re: [Intel-gfx] [PATCH] drm/i915: sync dp link status checks against atomic commmits

On Wed, Nov 08, 2017 at 02:11:46PM +0100, Daniel Vetter wrote: > On Wed, Nov 08, 2017 at 03:04:58PM +0200, Ville Syrjälä wrote: > > On Wed, Nov 08, 2017 at 01:57:50PM +0100, Daniel Vetter wrote: > > > Two bits: > > > - check actual atomic state, the legacy stuff can only be looked at > > > from

[Intel-gfx] [PATCH v2] drm/i915: Move init_clock_gating() back to where it was

From: Ville Syrjälä Apparently setting up a bunch of GT registers before we've properly initialized the rest of the GT hardware leads to these setting being lost. So looks like I broke HSW with commit b7048ea12fbb ("drm/i915: Do .init_clock_gating() earlier to

[Intel-gfx] ✗ Fi.CI.BAT: warning for HAX: WARN_ON(crtc->crc.opened during disable)

== Series Details == Series: HAX: WARN_ON(crtc->crc.opened during disable) URL : https://patchwork.freedesktop.org/series/33411/ State : warning == Summary == Series 33411v1 HAX: WARN_ON(crtc->crc.opened during disable) https://patchwork.freedesktop.org/api/1.0/series/33411/revisions/1/mbox/

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

Quoting Jani Nikula (2017-11-08 13:06:39) > > Please use trybot (i.e. send patches to > intel-gfx-try...@lists.freedesktop.org) for hacks that aren't intended > for upstream. Then they can be prioritized appropriately. We don't have excess to the extended test run on trybot yet... -Chris

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

On Wed, 08 Nov 2017, Chris Wilson wrote: > Quoting Jani Nikula (2017-11-08 13:06:39) >> >> Please use trybot (i.e. send patches to >> intel-gfx-try...@lists.freedesktop.org) for hacks that aren't intended >> for upstream. Then they can be prioritized appropriately. > >

Re: [Intel-gfx] [PATCH (resend) 1/3] drm/i915: Ignore previous watermarks on ILK if inherited

On Wed, Nov 08, 2017 at 10:29:20AM +0100, Maarten Lankhorst wrote: > Fixes the following error when fastset is enabled, caught by CI: > > [drm:ilk_validate_wm_level.part.8 [i915]] Sprite WM0 too large 56 (max 0) > [drm:ilk_validate_pipe_wm [i915]] LP0 watermark invalid >

Re: [Intel-gfx] [PATCH v2] drm/i915: Move init_clock_gating() back to where it was

Quoting Ville Syrjala (2017-11-08 13:35:55) > From: Ville Syrjälä > > Apparently setting up a bunch of GT registers before we've properly > initialized the rest of the GT hardware leads to these setting being > lost. So looks like I broke HSW with commit

Re: [Intel-gfx] [PATCH (resend) 3/3] drm/i915: Re-enable fastboot by default

On Wed, Nov 08, 2017 at 10:29:22AM +0100, Maarten Lankhorst wrote: > This fix was originally reverted because it left a chromebook pixel > black, and no immediate fix was available. This has been fixed in the > meantime. > > Rather than trying to remove the parameter, set it to default to true >

Re: [Intel-gfx] [PATCH] HAX: WARN_ON(crtc->crc.opened during disable)

On 08/11/17 17:59, Jani Nikula wrote: > On Wed, 08 Nov 2017, Tomi Sarvela wrote: >> On 08/11/17 17:27, Jani Nikula wrote: >>> On Wed, 08 Nov 2017, Chris Wilson wrote: Quoting Jani Nikula (2017-11-08 13:06:39) > > Please use trybot

[Intel-gfx] [PATCH 0/4] drm/i915: introduce query information

Hi, This series is based off work that Tvrtko started, initially for exposing the engines available to userspace. I've added the topology information I would like to expose for normalizing the performance counters. Cheers, Lionel Landwerlin (3): drm/i915: store all subslice masks

[Intel-gfx] [PATCH 3/4] drm/i915/debugfs: reuse max slice/subslices already stored in sseu

Now that we have that information in topology fields, let's just reused it. Signed-off-by: Lionel Landwerlin --- drivers/gpu/drm/i915/i915_debugfs.c | 26 ++ 1 file changed, 10 insertions(+), 16 deletions(-) diff --git

[Intel-gfx] [PATCH 4/4] drm/i915: expose rcs topology through discovery uAPI

With the introduction of asymetric slices in CNL, we cannot rely on the previous SUBSLICE_MASK getparam. Here we introduce a more detailed way of querying the Gen's GPU topology that doesn't aggregate numbers. This is essential for monitoring parts of the GPU with the OA unit, because counters

[Intel-gfx] [PATCH 1/4] drm/i915: introduce query info uAPI

From: Tvrtko Ursulin Query info uAPI allows userspace to probe for a number of properties of the GPU. This partially removes the need for userspace to maintain the internal PCI id based database (as well as code duplication across userspace components). This first

Re: [Intel-gfx] [PATCH v2] drm/i915: Idle the GPU before shinking everything

On Wed, 2017-11-08 at 09:44 +, Chris Wilson wrote: > The handling of contexts are peculiar. Instead of tieing their vma to > activity, we pin the context. This means that we cannot simply unbind > the context object itself at will (which would normally cause us to wait > for the vma to be

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Use trace_printk to provide a death rattle for GEM

== Series Details == Series: drm/i915: Use trace_printk to provide a death rattle for GEM URL : https://patchwork.freedesktop.org/series/33421/ State : success == Summary == Series 33421v1 drm/i915: Use trace_printk to provide a death rattle for GEM

[Intel-gfx] [PATCH] drm/edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks

From: Ville Syrjälä Apparently some sinks look at the YQ bits even when receiving RGB, and they get somehow confused when they see a non-zero YQ value. So we can't just blindly follow CEA-861-F and set YQ to match the RGB range. Unfortunately there is no good way

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks

== Series Details == Series: drm/edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks URL : https://patchwork.freedesktop.org/series/33432/ State : failure == Summary == Series 33432v1 drm/edid: Don't send non-zero YQ in AVI infoframe for HDMI 1.x sinks

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Move init_clock_gating() back to where it was (rev2)

== Series Details == Series: drm/i915: Move init_clock_gating() back to where it was (rev2) URL : https://patchwork.freedesktop.org/series/33124/ State : success == Summary == Series 33124v2 drm/i915: Move init_clock_gating() back to where it was

Re: [Intel-gfx] [PATCH] drm/i915: Enable runtime pm

On Tue, Nov 07, 2017 at 05:18:21PM +0100, Daniel Vetter wrote: > Now that we have CI, and that pm_rpm fully passes (I guess the audio > folks have implemented proper runtime pm for snd-hda, hooray, pls > confirm) it's time to enable this again by default. > > Real goal here is to have 1

  1   2   3   >