Re: [Intel-gfx] [PATCH v13 08/10] drm: Expose modes with aspect ratio, only if requested

2018-05-06 Thread Nautiyal, Ankit K
On 5/5/2018 1:49 AM, Ville Syrjälä wrote: On Thu, May 03, 2018 at 08:26:26AM +0200, Daniel Vetter wrote: On Wed, May 02, 2018 at 12:20:20PM +0530, Nautiyal, Ankit K wrote: From: Ankit Nautiyal We parse the EDID and add all the modes in the connector's modelist.

[Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority

2018-05-06 Thread Patchwork
== Series Details == Series: series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority URL : https://patchwork.freedesktop.org/series/42783/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4149_full -> Patchwork_8919_full = == Summary - FAILURE ==

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority

2018-05-06 Thread Patchwork
== Series Details == Series: series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority URL : https://patchwork.freedesktop.org/series/42783/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4149 -> Patchwork_8919 = == Summary - SUCCESS == No

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority

2018-05-06 Thread Patchwork
== Series Details == Series: series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority URL : https://patchwork.freedesktop.org/series/42783/ State : warning == Summary == $ dim sparse origin/drm-tip Commit: drm/i915: Flush submission tasklet after bumping priority

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority

2018-05-06 Thread Patchwork
== Series Details == Series: series starting with [1/3] drm/i915: Flush submission tasklet after bumping priority URL : https://patchwork.freedesktop.org/series/42783/ State : warning == Summary == $ dim checkpatch origin/drm-tip f722a94e0311 drm/i915: Flush submission tasklet after bumping

Re: [Intel-gfx] [PATCH 3/3] drm/i915/execlists: Direct submit onto idle engines

2018-05-06 Thread Chris Wilson
Quoting Chris Wilson (2018-05-06 23:47:28) > +static void __submit_queue(struct intel_engine_cs *engine) > +{ > + struct intel_engine_execlists * const execlists = >execlists; > + > + GEM_BUG_ON(!engine->i915->gt.awake); > + > + /* Directly submit the first request to reduce the

[Intel-gfx] [PATCH 2/3] drm/i915: Combine set-wedged protection and tasklet kicking

2018-05-06 Thread Chris Wilson
Around request submission, we protect the call to schedule with a premption disable loop to prevent set-wedge chaning function pointers underneath us. This also prevents the tasklet running on the local CPU, a trick we use immediately afterwards to forcibly execute the tasklet after submission. We

[Intel-gfx] [PATCH 1/3] drm/i915: Flush submission tasklet after bumping priority

2018-05-06 Thread Chris Wilson
When called from process context tasklet_schedule() defers itself to ksoftirqd. From experience this may cause unacceptable latencies of over 200ms in executing the submission tasklet, our goal is to reprioritise the HW execution queue and trigger preemption immediately, so convert the rcu

[Intel-gfx] [PATCH 3/3] drm/i915/execlists: Direct submit onto idle engines

2018-05-06 Thread Chris Wilson
Bypass using the tasklet to submit the first request to HW, as the tasklet may be deferred unto ksoftirqd and at a minimum will add in excess of 10us (and maybe tens of milliseconds) to our execution latency. This latency reduction is most notable when execution flows between engines.

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Don't request a bug report for unsafe module parameters

2018-05-06 Thread Patchwork
== Series Details == Series: drm/i915: Don't request a bug report for unsafe module parameters URL : https://patchwork.freedesktop.org/series/42775/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4149_full -> Patchwork_8918_full = == Summary - WARNING == Minor unknown

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Don't request a bug report for unsafe module parameters

2018-05-06 Thread Patchwork
== Series Details == Series: drm/i915: Don't request a bug report for unsafe module parameters URL : https://patchwork.freedesktop.org/series/42775/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4149 -> Patchwork_8918 = == Summary - SUCCESS == No regressions found.

[Intel-gfx] [PATCH] drm/i915: Don't request a bug report for unsafe module parameters

2018-05-06 Thread Chris Wilson
Unsafe module parameters are just that, unsafe. If the user is foolish enough to try them and the kernel breaks, they get to keep both pieces. Don't ask them to file a bug report if they broke it themselves. References: https://bugs.freedesktop.org/show_bug.cgi?id=106423 Fixes: d15d7538c6d2

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Speed up idle detection by kicking the tasklets (rev2)

2018-05-06 Thread Patchwork
== Series Details == Series: drm/i915: Speed up idle detection by kicking the tasklets (rev2) URL : https://patchwork.freedesktop.org/series/42774/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4149_full -> Patchwork_8917_full = == Summary - WARNING == Minor unknown

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Speed up idle detection by kicking the tasklets (rev2)

2018-05-06 Thread Patchwork
== Series Details == Series: drm/i915: Speed up idle detection by kicking the tasklets (rev2) URL : https://patchwork.freedesktop.org/series/42774/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4149 -> Patchwork_8917 = == Summary - SUCCESS == No regressions found.

[Intel-gfx] [PATCH v2] drm/i915: Speed up idle detection by kicking the tasklets

2018-05-06 Thread Chris Wilson
We rely on ksoftirqd to run in a timely fashion in order to drain the execlists queue. Quite frequently, it does not. In some cases we may see latencies of over 200ms triggering our idle timeouts and forcing us to declare the driver wedged! Thus we can speed up idle detection by bypassing

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Speed up idle detection by kicking the tasklets

2018-05-06 Thread Patchwork
== Series Details == Series: drm/i915: Speed up idle detection by kicking the tasklets URL : https://patchwork.freedesktop.org/series/42774/ State : failure == Summary == = CI Bug Log - changes from CI_DRM_4149_full -> Patchwork_8916_full = == Summary - FAILURE == Serious unknown changes

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Speed up idle detection by kicking the tasklets

2018-05-06 Thread Patchwork
== Series Details == Series: drm/i915: Speed up idle detection by kicking the tasklets URL : https://patchwork.freedesktop.org/series/42774/ State : success == Summary == = CI Bug Log - changes from CI_DRM_4149 -> Patchwork_8916 = == Summary - SUCCESS == No regressions found. External

[Intel-gfx] [PATCH] drm/i915: Speed up idle detection by kicking the tasklets

2018-05-06 Thread Chris Wilson
We rely on ksoftirqd to run in a timely fashion in order to drain the execlists queue. Quite frequently, it does not. In some cases we may see latencies of over 200ms triggering our idle timeouts and forcing us to declare the driver wedged! Thus we can speed up idle detection by bypassing