drm/i915: Untangle execlist tracking
Subsystems (2)
cover drm/i915: Untangle execlist tracking
This patchset merges execlist queue items in to gem requests. It does this by using the reference count added by the "Replace seqno values with request structures" patchset to ensure that the gem request is available for the whole execlist submission lifespan.
v2: merge intel_ctx_submit_request and drm_i915_gem_request, rebase changes &
add cover letter
v3: Rebase over upstreamed "Replace seqno values with request structures" and add overzealous freeing fix.
Issue: VIZ-4274
Nick Hoath (4):
drm/i915: execlist request keeps ptr/ref to gem_request drm/i915: Removed duplicate members from submit_request drm/i915: Remove FIXME_lrc_ctx backpointer
drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request
drivers/gpu/drm/i915/i915_debugfs.c | 4 +- drivers/gpu/drm/i915/i915_drv.h | 24 +++++++ drivers/gpu/drm/i915/i915_gem.c | 11 ++- drivers/gpu/drm/i915/intel_lrc.c | 123 +++++++++++++++++++------------- drivers/gpu/drm/i915/intel_lrc.h | 18 +++-- drivers/gpu/drm/i915/intel_ringbuffer.h | 15 ++-- 6 files changed, 122 insertions(+), 73 deletions(-)
Signature · 6 lines
2.1.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 1/4 drm/i915: execlist request keeps ptr/ref to gem_request
Add a reference and pointer from the execlist queue item to the associated gem request. For execlist requests that don't have a request, create one as a placeholder.
Issue: VIZ-4274
v1: Rebase after upstream of "Replace seqno values with request structures" patchset.
--- drivers/gpu/drm/i915/intel_lrc.c | 31 +++++++++++++++++++++++++------ drivers/gpu/drm/i915/intel_lrc.h | 6 +++++- 2 files changed, 30 insertions(+), 7 deletions(-)
drivers/gpu/drm/i915/intel_lrc.c +25 -6
@@ -535,7 +535,8 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)static int execlists_context_queue (struct intel_engine_cs *ring,struct intel_context *to, -u32 tail) +u32 tail, +struct drm_i915_gem_request *request) {struct intel_ctx_submit_request *req =NULL , *cursor;struct drm_i915_private *dev_priv = ring->dev->dev_private;
@@ -554,6 +555,21 @@ static int execlists_context_queue(struct intel_engine_cs *ring, req->ring = ring; req->tail = tail; +if (!request) { +/* +* If there isn't a request associated with this submission, +* create one as a temporary holder. +*/ +WARN (1 ,"execlist context submission without request" ); + request =kzalloc (sizeof (*request),GFP_KERNEL ); +if (request ==NULL ) +return -ENOMEM ; + request->ctx = to; + request->ring = ring; + } + req->request = request; +i915_gem_request_reference (request); +intel_runtime_pm_get (dev_priv);spin_lock_irqsave (&ring->execlist_lock, flags);
@@ -767,6 +783,7 @@ void intel_execlists_retire_requests(struct intel_engine_cs *ring)intel_lr_context_unpin (ring, ctx);intel_runtime_pm_put (dev_priv);i915_gem_context_unreference (req->ctx); +i915_gem_request_unreference (req->request);list_del (&req->execlist_link);kfree (req); }
@@ -819,7 +836,8 @@ int logical_ring_flush_all_caches(struct intel_ringbuffer *ringbuf)* on a queue waiting for the ELSP to be ready to accept a new context submission. At that * point, the tail *inside* the context is updated and the ELSP written to. */ -void intel_logical_ring_advance_and_submit (struct intel_ringbuffer *ringbuf) +void intel_logical_ring_advance_and_submit (struct intel_ringbuffer *ringbuf, +struct drm_i915_gem_request *request) {struct intel_engine_cs *ring = ringbuf->ring;struct intel_context *ctx = ringbuf->FIXME_lrc_ctx;
@@ -829,7 +847,7 @@ void intel_logical_ring_advance_and_submit(struct intel_ringbuffer *ringbuf)if (intel_ring_stopped (ring))return ; -execlists_context_queue (ring, ctx, ringbuf->tail); +execlists_context_queue (ring, ctx, ringbuf->tail, request); } static int intel_lr_context_pin(struct intel_engine_cs *ring,
@@ -973,7 +991,7 @@ static int logical_ring_wait_for_space(struct intel_ringbuffer *ringbuf,return ret;/* Force the context submission in case we have been skipping it */ -intel_logical_ring_advance_and_submit (ringbuf); +intel_logical_ring_advance_and_submit (ringbuf,NULL );/* With GEM the hangcheck timer should kick us out of the loop, * leaving it early runs the risk of corrupting GEM state (due
@@ -1311,7 +1329,8 @@ static void gen8_set_seqno(struct intel_engine_cs *ring, u32 seqno)intel_write_status_page (ring,I915_GEM_HWS_INDEX , seqno); } -static int gen8_emit_request (struct intel_ringbuffer *ringbuf) +static int gen8_emit_request (struct intel_ringbuffer *ringbuf, +struct drm_i915_gem_request *request) {struct intel_engine_cs *ring = ringbuf->ring;u32 cmd;
@@ -1333,7 +1352,7 @@ static int gen8_emit_request(struct intel_ringbuffer *ringbuf) i915_gem_request_get_seqno(ring->outstanding_lazy_request));intel_logical_ring_emit (ringbuf,MI_USER_INTERRUPT );intel_logical_ring_emit (ringbuf,MI_NOOP ); -intel_logical_ring_advance_and_submit (ringbuf); +intel_logical_ring_advance_and_submit (ringbuf, request);return 0 ; }
drivers/gpu/drm/i915/intel_lrc.h +5 -1
@@ -39,7 +39,9 @@ void intel_logical_ring_cleanup(struct intel_engine_cs *ring);int intel_logical_rings_init (struct drm_device *dev);int logical_ring_flush_all_caches (struct intel_ringbuffer *ringbuf); -void intel_logical_ring_advance_and_submit (struct intel_ringbuffer *ringbuf); +void intel_logical_ring_advance_and_submit ( +struct intel_ringbuffer *ringbuf, +struct drm_i915_gem_request *request);/** * intel_logical_ring_advance() - advance the ringbuffer tail * @ringbuf: Ringbuffer to advance.
@@ -110,6 +112,8 @@ struct intel_ctx_submit_request {struct list_head execlist_link;int elsp_submitted; + +struct drm_i915_gem_request *request; };void intel_lrc_irq_handler (struct intel_engine_cs *ring);
Signature · 6 lines
2.1.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/4 drm/i915: Removed duplicate members from submit_request
In reply to Nick HoathWhere there were duplicate variables for the tail, context and ring (engine) in the gem request and the execlist queue item, use the one from the request and remove the duplicate from the execlist queue item.
Issue: VIZ-4274
v1: Rebase
--- drivers/gpu/drm/i915/i915_debugfs.c | 4 ++-- drivers/gpu/drm/i915/i915_gem.c | 2 +- drivers/gpu/drm/i915/intel_lrc.c | 20 +++++++++----------- drivers/gpu/drm/i915/intel_lrc.h | 4 ---- 4 files changed, 12 insertions(+), 18 deletions(-)
drivers/gpu/drm/i915/i915_debugfs.c +2 -2
@@ -1915,11 +1915,11 @@ static int i915_execlists(struct seq_file *m, void *data)if (head_req) {struct drm_i915_gem_object *ctx_obj; - ctx_obj = head_req->ctx->engine[ring_id].state; + ctx_obj = head_req->request->ctx->engine[ring_id].state;seq_printf (m,"\tHead request id: %u\n" ,intel_execlists_ctx_id (ctx_obj));seq_printf (m,"\tHead request tail: %u\n" , - head_req->tail); + head_req->request->tail); }seq_putc (m,'\n' );
drivers/gpu/drm/i915/i915_gem.c +1 -1
@@ -2666,7 +2666,7 @@ static void i915_gem_reset_ring_cleanup(struct drm_i915_private *dev_priv, execlist_link);list_del (&submit_req->execlist_link);intel_runtime_pm_put (dev_priv); -i915_gem_context_unreference (submit_req->ctx); +i915_gem_context_unreference (submit_req->request->ctx);kfree (submit_req); }
drivers/gpu/drm/i915/intel_lrc.c +9 -11
@@ -418,7 +418,7 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring) execlist_link) {if (!req0) { req0 = cursor; - }else if (req0->ctx == cursor->ctx) { + }else if (req0->request->ctx == cursor->request->ctx) {/* Same ctx: ignore first request, as second request * will update tail past first request's workload */ cursor->elsp_submitted = req0->elsp_submitted;
@@ -434,9 +434,9 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring)WARN_ON (req1 && req1->elsp_submitted); -execlists_submit_contexts (ring, req0->ctx, req0->tail, - req1 ? req1->ctx :NULL , - req1 ? req1->tail :0 ); +execlists_submit_contexts (ring, req0->request->ctx, req0->request->tail, + req1 ? req1->request->ctx :NULL , + req1 ? req1->request->tail :0 ); req0->elsp_submitted++;if (req1)
@@ -456,7 +456,7 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring,if (head_req !=NULL ) {struct drm_i915_gem_object *ctx_obj = - head_req->ctx->engine[ring->id].state; + head_req->request->ctx->engine[ring->id].state;if (intel_execlists_ctx_id (ctx_obj) == request_id) {WARN (head_req->elsp_submitted ==0 ,"Never submitted head request\n" );
@@ -552,9 +552,6 @@ static int execlists_context_queue(struct intel_engine_cs *ring,if (to != ring->default_context)intel_lr_context_pin (ring, to); - req->ring = ring; - req->tail = tail; -if (!request) {/* * If there isn't a request associated with this submission,
@@ -569,6 +566,7 @@ static int execlists_context_queue(struct intel_engine_cs *ring, } req->request = request;i915_gem_request_reference (request); +i915_gem_context_reference (req->request->ctx);intel_runtime_pm_get (dev_priv);
@@ -585,7 +583,7 @@ static int execlists_context_queue(struct intel_engine_cs *ring, struct intel_ctx_submit_request, execlist_link); -if (to == tail_req->ctx) { +if (to == tail_req->request->ctx) {WARN (tail_req->elsp_submitted !=0 ,"More than 2 already-submitted reqs queued\n" );list_del (&tail_req->execlist_link);
@@ -775,14 +773,14 @@ void intel_execlists_retire_requests(struct intel_engine_cs *ring)spin_unlock_irqrestore (&ring->execlist_lock, flags);list_for_each_entry_safe (req, tmp, &retired_list, execlist_link) { -struct intel_context *ctx = req->ctx; +struct intel_context *ctx = req->request->ctx;struct drm_i915_gem_object *ctx_obj = ctx->engine[ring->id].state;if (ctx_obj && (ctx != ring->default_context))intel_lr_context_unpin (ring, ctx);intel_runtime_pm_put (dev_priv); -i915_gem_context_unreference (req->ctx); +i915_gem_context_unreference (ctx);i915_gem_request_unreference (req->request);list_del (&req->execlist_link);kfree (req);
drivers/gpu/drm/i915/intel_lrc.h +0 -4
@@ -105,10 +105,6 @@ u32 intel_execlists_ctx_id(struct drm_i915_gem_object *ctx_obj);* All accesses to the queue are mediated by a spinlock (ring->execlist_lock). */ struct intel_ctx_submit_request { -struct intel_context *ctx; -struct intel_engine_cs *ring; -u32 tail; -struct list_head execlist_link;int elsp_submitted;
Signature · 6 lines
2.1.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 3/4 drm/i915: Remove FIXME_lrc_ctx backpointer
In reply to Nick HoathThe first pass implementation of execlists required a backpointer to the context to be held in the intel_ringbuffer. However the context pointer is available higher in the call stack. Remove the backpointer from the ring buffer structure and instead pass it down through the call stack.
v2: Integrate this changeset with the removal of duplicate request/execlist queue item members.
v3: Rebase
--- drivers/gpu/drm/i915/i915_gem.c | 7 ++-- drivers/gpu/drm/i915/intel_lrc.c | 68 ++++++++++++++++++++------------- drivers/gpu/drm/i915/intel_lrc.h | 8 +++- drivers/gpu/drm/i915/intel_ringbuffer.h | 15 ++++---- 4 files changed, 57 insertions(+), 41 deletions(-)
drivers/gpu/drm/i915/i915_gem.c +3 -4
@@ -2432,8 +2432,7 @@ int __i915_add_request(struct intel_engine_cs *ring,return -ENOMEM ;if (i915.enable_execlists) { -struct intel_context *ctx = request->ctx; - ringbuf = ctx->engine[ring->id].ringbuf; + ringbuf = request->ctx->engine[ring->id].ringbuf; }else ringbuf = ring->buffer;
@@ -2446,7 +2445,7 @@ int __i915_add_request(struct intel_engine_cs *ring,* what. */ if (i915.enable_execlists) { - ret =logical_ring_flush_all_caches (ringbuf); + ret =logical_ring_flush_all_caches (ringbuf, request->ctx);if (ret)return ret; }else {
@@ -2463,7 +2462,7 @@ int __i915_add_request(struct intel_engine_cs *ring, request_ring_position =intel_ring_get_tail (ringbuf);if (i915.enable_execlists) { - ret = ring->emit_request (ringbuf); + ret = ring->emit_request (ringbuf, request->ctx, request);if (ret)return ret; }else {
drivers/gpu/drm/i915/intel_lrc.c +41 -27
270 lines not on this page · raw message
drivers/gpu/drm/i915/intel_lrc.h +6 -2
@@ -38,9 +38,11 @@ void intel_logical_ring_stop(struct intel_engine_cs *ring);void intel_logical_ring_cleanup (struct intel_engine_cs *ring);int intel_logical_rings_init (struct drm_device *dev); -int logical_ring_flush_all_caches (struct intel_ringbuffer *ringbuf); +int logical_ring_flush_all_caches (struct intel_ringbuffer *ringbuf, +struct intel_context *ctx);void intel_logical_ring_advance_and_submit (struct intel_ringbuffer *ringbuf, +struct intel_context *ctx,struct drm_i915_gem_request *request);/** * intel_logical_ring_advance() - advance the ringbuffer tail
@@ -63,7 +65,9 @@ static inline void intel_logical_ring_emit(struct intel_ringbuffer *ringbuf,iowrite32 (data, ringbuf->virtual_start + ringbuf->tail); ringbuf->tail +=4 ; } -int intel_logical_ring_begin (struct intel_ringbuffer *ringbuf,int num_dwords); +int intel_logical_ring_begin (struct intel_ringbuffer *ringbuf, +struct intel_context *ctx, +int num_dwords);/* Logical Ring Contexts */ int intel_lr_context_render_state_init(struct intel_engine_cs *ring,
drivers/gpu/drm/i915/intel_ringbuffer.h +7 -8
@@ -99,13 +99,6 @@ struct intel_ringbuffer {struct intel_engine_cs *ring; -/* -* FIXME: This backpointer is an artifact of the history of how the -* execlist patches came into being. It will get removed once the basic -* code has landed. -*/ -struct intel_context *FIXME_lrc_ctx; -u32 head;u32 tail;int space;
@@ -123,6 +116,8 @@ struct intel_ringbuffer {u32 last_retired_head; }; +struct intel_context ; + struct intel_engine_cs { const char *name; enum intel_ring_id {
@@ -239,11 +234,15 @@ struct intel_engine_cs {struct list_head execlist_retired_req_list;u8 next_context_status_buffer;u32 irq_keep_mask;/* bitmask for interrupts that should not be masked */ -int (*emit_request)(struct intel_ringbuffer *ringbuf); +int (*emit_request)(struct intel_ringbuffer *ringbuf, +struct intel_context *ctx, +struct drm_i915_gem_request *request);int (*emit_flush)(struct intel_ringbuffer *ringbuf, +struct intel_context *ctx,u32 invalidate_domains,u32 flush_domains);int (*emit_bb_start)(struct intel_ringbuffer *ringbuf, +struct intel_context *ctx,u64 offset,unsigned flags);/**
Signature · 6 lines
2.1.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 4/4 drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request
In reply to Nick HoathMove all remaining elements that were unique to execlists queue items in to the associated request.
Issue: VIZ-4274
v2: Rebase. Fixed issue of overzealous freeing of request.
--- drivers/gpu/drm/i915/i915_debugfs.c | 8 +++---- drivers/gpu/drm/i915/i915_drv.h | 24 ++++++++++++++++++++ drivers/gpu/drm/i915/i915_gem.c | 6 ++--- drivers/gpu/drm/i915/intel_lrc.c | 44 +++++++++++++++---------------------- 4 files changed, 49 insertions(+), 33 deletions(-)
drivers/gpu/drm/i915/i915_debugfs.c +4 -4
@@ -1875,7 +1875,7 @@ static int i915_execlists(struct seq_file *m, void *data)intel_runtime_pm_get (dev_priv);for_each_ring (ring, dev_priv, ring_id) { -struct intel_ctx_submit_request *head_req =NULL ; +struct drm_i915_gem_request *head_req =NULL ;int count =0 ;unsigned long flags;
@@ -1908,18 +1908,18 @@ static int i915_execlists(struct seq_file *m, void *data)list_for_each (cursor, &ring->execlist_queue) count++; head_req =list_first_entry_or_null (&ring->execlist_queue, - struct intel_ctx_submit_request, execlist_link); + struct drm_i915_gem_request, execlist_link);spin_unlock_irqrestore (&ring->execlist_lock, flags);seq_printf (m,"\t%d requests in queue\n" , count);if (head_req) {struct drm_i915_gem_object *ctx_obj; - ctx_obj = head_req->request->ctx->engine[ring_id].state; + ctx_obj = head_req->ctx->engine[ring_id].state;seq_printf (m,"\tHead request id: %u\n" ,intel_execlists_ctx_id (ctx_obj));seq_printf (m,"\tHead request tail: %u\n" , - head_req->request->tail); + head_req->tail); }seq_putc (m,'\n' );
drivers/gpu/drm/i915/i915_drv.h +24 -0
@@ -2036,6 +2036,30 @@ struct drm_i915_gem_request {struct list_head client_list;uint32_t uniq; + +/** +* The ELSP only accepts two elements at a time, so we queue +* context/tail pairs on a given queue (ring->execlist_queue) until the +* hardware is available. The queue serves a double purpose: we also use +* it to keep track of the up to 2 contexts currently in the hardware +* (usually one in execution and the other queued up by the GPU): We +* only remove elements from the head +* of the queue when the hardware informs us that an element has been +* completed. +* +* All accesses to the queue are mediated by a spinlock +* (ring->execlist_lock). +*/ + +/** Execlist link in the submission queue.*/ +struct list_head execlist_link; + +/** Execlists workqueue for processing this request in a bottom half */ +struct work_struct work; + +/** Execlists no. of times this request has been sent to the ELSP */ +int elsp_submitted; + };void i915_gem_request_free (struct kref *req_ref);
drivers/gpu/drm/i915/i915_gem.c +3 -3
@@ -2658,14 +2658,14 @@ static void i915_gem_reset_ring_cleanup(struct drm_i915_private *dev_priv,* pinned in place. */ while (!list_empty (&ring->execlist_queue)) { -struct intel_ctx_submit_request *submit_req; +struct drm_i915_gem_request *submit_req; submit_req =list_first_entry (&ring->execlist_queue, - struct intel_ctx_submit_request, + struct drm_i915_gem_request, execlist_link);list_del (&submit_req->execlist_link);intel_runtime_pm_put (dev_priv); -i915_gem_context_unreference (submit_req->request->ctx); +i915_gem_context_unreference (submit_req->ctx);kfree (submit_req); }
drivers/gpu/drm/i915/intel_lrc.c +18 -26
128 lines not on this page · raw message
Signature · 6 lines
2.1.1 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request
-------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 364/364 364/364
ILK +3-3 360/366 360/366
SNB 448/450 448/450 IVB 497/498 497/498 BYT 289/289 289/289 HSW 563/564 563/564 BDW 417/417 417/417 -------------------------------------Detailed------------------------------------- Platform Test drm-intel-nightly Series Applied ILK igt_drv_suspend_fence-restore-untiled DMESG_WARN(1, M26)PASS(10, M37M26) PASS(1, M26) ILK igt_kms_flip_bcs-flip-vs-modeset-interruptible DMESG_WARN(1, M26)PASS(10, M37M26) PASS(1, M26) *ILK igt_kms_flip_flip-vs-dpms-interruptible PASS(1, M26) DMESG_WARN(1, M26) *ILK igt_kms_flip_plain-flip-fb-recreate-interruptible PASS(1, M26) DMESG_WARN(1, M26) ILK igt_kms_flip_rcs-flip-vs-dpms DMESG_WARN(1, M26)PASS(9, M37M26) PASS(1, M26) *ILK igt_kms_flip_vblank-vs-hang PASS(1, M26) DMESG_WARN(1, M26)
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list [email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request
In reply to Nick HoathQuoted 18 lines · Nick Hoath
drivers/gpu/drm/i915/i915_drv.h +10
-0@@ -2036,6 +2036,30 @@ struct drm_i915_gem_request {struct list_head client_list;uint32_t uniq; + +/** +* The ELSP only accepts two elements at a time, so we queue +* context/tail pairs on a given queue (ring->execlist_queue) until the +* hardware is available. The queue serves a double purpose: we also use +* it to keep track of the up to 2 contexts currently in the hardware +* (usually one in execution and the other queued up by the GPU): We +* only remove elements from the head +* of the queue when the hardware informs us that an element has been +* completed.
drivers/gpu/drm/i915/i915_drv.h struct drm_i915_gem_request { · line 2058
Quoted 10 lines
drivers/gpu/drm/i915/i915_drv.h +10
-0+* +* All accesses to the queue are mediated by a spinlock +* (ring->execlist_lock). +*/ + +/** Execlist link in the submission queue.*/ +struct list_head execlist_link; + +/** Execlists workqueue for processing this request in a bottom half */ +struct work_struct work;
Hm I've thought this would drop out with the other rework we've had floating around. It's also not used anywhere, so I guess it disappeared for real and is just a leftover from rebasing?
Otherwise I guess this is ready for final review I think. -Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 4/4] drm/i915: Subsume intel_ctx_submit_request in to drm_i915_gem_request
Quoted 25 lines · Daniel Vetter
Quoted 24 lines · Nick Hoath
drivers/gpu/drm/i915/i915_drv.h +16
-0@@ -2036,6 +2036,30 @@ struct drm_i915_gem_request {struct list_head client_list;uint32_t uniq; + +/** +* The ELSP only accepts two elements at a time, so we queue +* context/tail pairs on a given queue (ring->execlist_queue) until the +* hardware is available. The queue serves a double purpose: we also use +* it to keep track of the up to 2 contexts currently in the hardware +* (usually one in execution and the other queued up by the GPU): We +* only remove elements from the head +* of the queue when the hardware informs us that an element has been +* completed. +* +* All accesses to the queue are mediated by a spinlock +* (ring->execlist_lock). +*/ + +/** Execlist link in the submission queue.*/
Quoted 8 lines
drivers/gpu/drm/i915/i915_drv.h struct drm_i915_gem_request { · line 2058
Quoted 4 lines
drivers/gpu/drm/i915/i915_drv.h +4
-0+struct list_head execlist_link; + +/** Execlists workqueue for processing this request in a bottom half */ +struct work_struct work;Hm I've thought this would drop out with the other rework we've had floating around. It's also not used anywhere, so I guess it disappeared for real and is just a leftover from rebasing?
And a plea from your maintainer: I've asked for exactly this in my reply, but there was no reply from you nor any mention about anything in the in-patch changelog. So I had to digg through all the patches and the old thread to figure out again what it is my subconscious told me is missing.
This isn't efficient, so please always acknowledge review feedbacka and questions either with a reply or in the commit message changelogs (there it needs the name of the reviewer in case there was lots of feedback.)
Thanks, Daniel
Signature · 7 lines
Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx