[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Fix documentation for __intel_wait_for_register_fw*

2019-08-03 Thread Patchwork
== Series Details == Series: drm/i915: Fix documentation for __intel_wait_for_register_fw* URL : https://patchwork.freedesktop.org/series/64608/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6614_full -> Patchwork_13850_full

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] drm/i915/execlists: Always clear pending&inflight requests on reset (rev3)

2019-08-03 Thread Patchwork
== Series Details == Series: series starting with [1/3] drm/i915/execlists: Always clear pending&inflight requests on reset (rev3) URL : https://patchwork.freedesktop.org/series/64426/ State : success == Summary == CI Bug Log - changes from CI_DRM_6612_full -> Patchwork_13847_full ===

Re: [Intel-gfx] [PATCH v3 1/1] drm/vblank: drop use of DRM_WAIT_ON()

2019-08-03 Thread Sam Ravnborg
Hi all. On Fri, Jul 26, 2019 at 11:06:58PM +0200, Sam Ravnborg wrote: > DRM_WAIT_ON() is from the deprecated drm_os_linux header and > the modern replacement is the wait_event_*. > > The return values differ, so a conversion is needed to > keep the original interface towards userspace. > Introduc

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pmu: Use GT parked for estimating RC6 while asleep (rev2)

2019-08-03 Thread Patchwork
== Series Details == Series: drm/i915/pmu: Use GT parked for estimating RC6 while asleep (rev2) URL : https://patchwork.freedesktop.org/series/56583/ State : success == Summary == CI Bug Log - changes from CI_DRM_6622 -> Patchwork_13864 Sum

[Intel-gfx] [PATCH] drm/i915/pmu: Use GT parked for estimating RC6 while asleep

2019-08-03 Thread Chris Wilson
As we track when we put the GT device to sleep upon idling, we can use that callback to sample the current rc6 counters and record the timestamp for estimating samples after that point while asleep. v2: Stick to using ktime_t Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105010 Signed-of

[Intel-gfx] ✓ Fi.CI.IGT: success for i915/gem_exec_schedule: Check timeslice

2019-08-03 Thread Patchwork
== Series Details == Series: i915/gem_exec_schedule: Check timeslice URL : https://patchwork.freedesktop.org/series/64600/ State : success == Summary == CI Bug Log - changes from CI_DRM_6612_full -> IGTPW_3315_full Summary --- **SUCC

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Remove stale kerneldoc for internal MOCS functions

2019-08-03 Thread Patchwork
== Series Details == Series: drm/i915/gt: Remove stale kerneldoc for internal MOCS functions URL : https://patchwork.freedesktop.org/series/64649/ State : success == Summary == CI Bug Log - changes from CI_DRM_6622 -> Patchwork_13863 Summar

Re: [Intel-gfx] [PATCH 2/2] drm/syncobj: Lookup the syncobj with RCU protection

2019-08-03 Thread kbuild test robot
/commits/Chris-Wilson/drm-syncobj-Convert-syncobj_idr-to-XArray/20190803-170547 reproduce: make htmldocs If you fix the issue, kindly add following tag Reported-by: kbuild test robot All warnings (new ones prefixed by >>): include/linux/skbuff.h:893: warning: Function parameter or

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

2019-08-03 Thread Maxime Ripard
Hi Daniel, Dave, Here is the first (and pretty late) drm-misc-next PR. It's pretty big due to the lateness, but there's nothing really major showing up. It's pretty much the usual bunch of reworks, fixes, and new helpers being introduced. Thanks! Maxime drm-misc-next-2019-08-03: drm-misc-next f

[Intel-gfx] [PATCH] drm/i915/gt: Remove stale kerneldoc for internal MOCS functions

2019-08-03 Thread Chris Wilson
The kerneldoc were stale, generating mismatching parameters warning, but furthermore they were for internal routines, not part of the MOCS interface so the instructions were superfluous. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/gt/intel_mocs.c | 57 +--- 1 fil

[Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/gem: Make caps.scheduler static

2019-08-03 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/gem: Make caps.scheduler static URL : https://patchwork.freedesktop.org/series/64647/ State : failure == Summary == CI Bug Log - changes from CI_DRM_6621 -> Patchwork_13862 Su

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/gem: Make caps.scheduler static

2019-08-03 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/gem: Make caps.scheduler static URL : https://patchwork.freedesktop.org/series/64647/ State : warning == Summary == $ dim checkpatch origin/drm-tip 136c5adecffd drm/i915/gem: Make caps.scheduler static 57f5cfd5d696 drm/i915/gt: M

[Intel-gfx] [PATCH 1/2] drm/i915/gem: Make caps.scheduler static

2019-08-03 Thread Chris Wilson
We do not notify userspace when the scheduler capabilities are changed (due to wedging the driver) and as such userspace will expect the caps to be static and unchanging. Make it so, and so we only need to compute our caps once during driver registration. Signed-off-by: Chris Wilson Cc: Tvrtko Ur

[Intel-gfx] [PATCH 2/2] drm/i915/gt: Move the [class][inst] lookup for engines onto the GT

2019-08-03 Thread Chris Wilson
To maintain a fast lookup from a GT centric irq handler, we want the engine lookup tables on the intel_gt. To avoid having multiple copies of the same multi-dimension lookup table, move the generic user engine lookup into an rbtree (for fast and flexible indexing). v2: Split uabi_instance cf uabi_

Re: [Intel-gfx] [RFC] drm/i915/gt: create a subfolder for GT debugfs

2019-08-03 Thread Chris Wilson
Quoting Daniele Ceraolo Spurio (2019-08-03 02:09:44) > The idea is to better organize our debugfs entries by moving the > GT-related ones into their own subfolder, similarly to what we did for > the kernel code. > > As an example, this patch moves the GuC/HuC and user_forcewake debugfs, > but a fe

Re: [Intel-gfx] [PATCH 10/34] genwqe: convert put_page() to put_user_page*()

2019-08-03 Thread Greg Kroah-Hartman
On Thu, Aug 01, 2019 at 07:19:41PM -0700, john.hubb...@gmail.com wrote: > From: John Hubbard > > For pages that were retained via get_user_pages*(), release those pages > via the new put_user_page*() routines, instead of via put_page() or > release_pages(). > > This is part a tree-wide conversio

Re: [Intel-gfx] [PATCH 15/34] staging/vc04_services: convert put_page() to put_user_page*()

2019-08-03 Thread Greg Kroah-Hartman
On Thu, Aug 01, 2019 at 07:19:46PM -0700, john.hubb...@gmail.com wrote: > From: John Hubbard > > For pages that were retained via get_user_pages*(), release those pages > via the new put_user_page*() routines, instead of via put_page() or > release_pages(). > > This is part a tree-wide conversio