[Intel-gfx] [PATCH v2 02/25] drm/i915: Use engine to refer to the user's BSD intel_engine_cs

2016-07-22 Thread Chris Wilson
This patch transitions the execbuf engine selection away from using the ring nomenclature - though we still refer to the user's incoming selector as their user_ring_id. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/i915_drv.h| 4 ++-- drivers/gpu/drm/i915/i915_gem.c

[Intel-gfx] [PATCH v2 10/25] drm/i915: Rename struct intel_ringbuffer to struct intel_ring

2016-07-22 Thread Chris Wilson
The state stored in this struct is not only the information about the buffer object, but the ring used to communicate with the hardware. Using buffer here is overly specific and, for me at least, conflates with the notion of buffer objects themselves. s/struct intel_ringbuffer/struct intel_ring/ s

Re: [Intel-gfx] [PATCH 18/18] drm/i915: Simplify calling engine->sync_to

2016-07-22 Thread Joonas Lahtinen
On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > Since requests can no longer be generated as a side-effect of > intel_ring_begin(), we know that the seqno will be unchanged during > ring-emission. This predicatablity then means we do not have to check > for the seqno wrapping around whilst

Re: [Intel-gfx] [PATCH 17/18] drm/i915: Unify legacy/execlists submit_execbuf callbacks

2016-07-22 Thread Joonas Lahtinen
On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > Now that emitting requests is identical between legacy and execlists, we > can use the same function to build up the ring for submitting to either > engine. (With the exception of i915_switch_contexts(), but in time that > will also be handled

Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.99.917

2016-07-22 Thread Peter Hessler
On 2016 Jan 26 (Tue) at 21:51:10 +0100 (+0100), Ren? Rebe wrote: : :On Jan 26, 2016, at 19:03, Andreas Radke wrote: : :> Am Wed, 6 May 2015 22:02:57 +0200 :> schrieb Julien Cristau : :> :>> On Sun, Dec 21, 2014 at 14:47:58 +, Chris Wilson wrote: :>> :>>> Snapshot 2.99.917 (2014-12-21) :>>> =

Re: [Intel-gfx] [PATCH 2/2] drm/doc: Fix more kerneldoc/sphinx warnings

2016-07-22 Thread Mauro Carvalho Chehab
Em Wed, 20 Jul 2016 20:35:09 +0200 Markus Heiser escreveu: > Am 20.07.2016 um 14:20 schrieb Mauro Carvalho Chehab > : > > > Em Tue, 19 Jul 2016 14:36:50 +0200 > > Daniel Vetter escreveu: > > > >> On Tue, Jul 19, 2016 at 01:42:55PM +0200, Daniel Vetter wrote: > >>> These are the leftovers

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Markus Heiser
Am 20.07.2016 um 13:27 schrieb Daniel Vetter : > On Wed, Jul 20, 2016 at 12:55 PM, Markus Heiser > wrote: >> Hi Daniel, hi Mauro, >> >> Am 19.07.2016 um 17:32 schrieb Daniel Vetter : >> >>> On Tue, Jul 19, 2016 at 5:25 PM, Daniel Vetter >>> wrote: On Tue, Jul 19, 2016 at 4:59 PM, Markus

Re: [Intel-gfx] [PATCH 2/2] drm/doc: Fix more kerneldoc/sphinx warnings

2016-07-22 Thread Markus Heiser
Am 20.07.2016 um 14:20 schrieb Mauro Carvalho Chehab : > Em Tue, 19 Jul 2016 14:36:50 +0200 > Daniel Vetter escreveu: > >> On Tue, Jul 19, 2016 at 01:42:55PM +0200, Daniel Vetter wrote: >>> These are the leftovers I could only track down using keep_warnings = >>> True. For some of them we might

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Mauro Carvalho Chehab
Em Wed, 20 Jul 2016 14:29:01 +0200 Markus Heiser escreveu: > Am 20.07.2016 um 13:27 schrieb Daniel Vetter : > > > On Wed, Jul 20, 2016 at 12:55 PM, Markus Heiser > > wrote: > >> Hi Daniel, hi Mauro, > >> > >> Am 19.07.2016 um 17:32 schrieb Daniel Vetter : > >> > >>> On Tue, Jul 19, 2016 a

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Markus Heiser
Hi Daniel, hi Mauro, Am 19.07.2016 um 17:32 schrieb Daniel Vetter : > On Tue, Jul 19, 2016 at 5:25 PM, Daniel Vetter wrote: >> On Tue, Jul 19, 2016 at 4:59 PM, Markus Heiser >> wrote: >>> >>> Am 19.07.2016 um 13:42 schrieb Daniel Vetter : >>> Unfortunately warnings generated after parsin

Re: [Intel-gfx] [PATCH 2/2] drm/doc: Fix more kerneldoc/sphinx warnings

2016-07-22 Thread Mauro Carvalho Chehab
Em Tue, 19 Jul 2016 14:36:50 +0200 Daniel Vetter escreveu: > On Tue, Jul 19, 2016 at 01:42:55PM +0200, Daniel Vetter wrote: > > These are the leftovers I could only track down using keep_warnings = > > True. For some of them we might want to update our style guide on how > > to reference structur

Re: [Intel-gfx] [PATCH 1/2] doc/sphinx: Enable keep_warnings

2016-07-22 Thread Markus Heiser
Am 19.07.2016 um 13:42 schrieb Daniel Vetter : > Unfortunately warnings generated after parsing in sphinx can end up > with entirely bogus files and line numbers as sources. Strangely for > outright errors this is not a problem. Trying to convert warnings to > errors also doesn't fix it. > > The

Re: [Intel-gfx] [PATCH 14/18] drm/i915: Reuse legacy breadcrumbs + tail emission

2016-07-22 Thread Joonas Lahtinen
On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > As GEN6+ is now a simple variant on the basic breadcrumbs + tail write, > reuse the common code. > Code motion could always be separate patch for easier review of what functions were changed. Reviewed-by: Joonas Lahtinen > Signed-off-by:

Re: [Intel-gfx] [PATCH 13/18] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal()

2016-07-22 Thread Chris Wilson
On Fri, Jul 22, 2016 at 11:15:59AM +0300, Joonas Lahtinen wrote: > On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > > Rather than pass in the num_dwords that the caller wishes to use after > > the signal command packet, split the breadcrumb emission into two phases > > and have both the sign

Re: [Intel-gfx] [PATCH 12/18] drm/i915: Unify request submission

2016-07-22 Thread Chris Wilson
On Fri, Jul 22, 2016 at 11:03:19AM +0300, Joonas Lahtinen wrote: > On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > > @@ -1904,8 +1898,10 @@ logical_ring_default_vfuncs(struct intel_engine_cs > > *engine) > >  { > >   /* Default vfuncs which can be overriden by each engine. */ > >   eng

Re: [Intel-gfx] [PATCH 13/18] drm/i915: Stop passing caller's num_dwords to engine->semaphore.signal()

2016-07-22 Thread Joonas Lahtinen
On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > Rather than pass in the num_dwords that the caller wishes to use after > the signal command packet, split the breadcrumb emission into two phases > and have both the signal and breadcrumb individiually acquire space on > the ring. This makes t

[Intel-gfx] [PULL] topic/drm-misc

2016-07-22 Thread Daniel Vetter
Hi Dave, Suddenly everyone shows up with their trivial patch series! - piles of if (!ptr) check removals from Markus Elfring - more of_node_put fixes from Peter Chen - make fbdev support really optional in all drivers (except vmwgfx), somehow this fell through the cracks when we did all the hard

Re: [Intel-gfx] [PATCH 12/18] drm/i915: Unify request submission

2016-07-22 Thread Joonas Lahtinen
On ke, 2016-07-20 at 14:12 +0100, Chris Wilson wrote: > Move request submission from emit_request into its own common vfunc > from i915_add_request(). > > Signed-off-by: Chris Wilson > --- >  drivers/gpu/drm/i915/i915_gem_request.c|  7 +++ >  drivers/gpu/drm/i915/i915_guc_submission.c |  

Re: [Intel-gfx] [PATCH v2 3/3] drm/i915: Check for a stuck waiter before a missed interrupt

2016-07-22 Thread Chris Wilson
On Thu, Jul 21, 2016 at 07:57:39AM +0100, Chris Wilson wrote: > As the interrupt wakeup counter only increments when we have a waiter, > before testing to see if that counter is unchanged we have to first > check that we do expect it to change (i.e. we have a waiter). > > Signed-off-by: Chris Wils

[Intel-gfx] ✓ Ro.CI.BAT: success for drm/i915/skl: Finally fix watermarks (rev2)

2016-07-22 Thread Patchwork
== Series Details == Series: drm/i915/skl: Finally fix watermarks (rev2) URL : https://patchwork.freedesktop.org/series/10108/ State : success == Summary == Series 10108v2 drm/i915/skl: Finally fix watermarks http://patchwork.freedesktop.org/api/1.0/series/10108/revisions/2/mbox fi-hsw-i7-47

<    1   2