drm/i915: Do not return stale status / remove impossible WARN
Subsystems (2)
PATCH 1/2 drm/i915: Do not return stale status / remove impossible WARN
From: Tvrtko Ursulin <[email protected]>
Only caller to get_context_status ensures read pointer stays in range so the WARN is impossible. Also, if the WARN would be triggered by a hypothetical new caller stale status would be returned to them.
Maybe it is better to wrap the pointer in the function itself then to avoid both and even results in smaller code.
--- drivers/gpu/drm/i915/intel_lrc.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)
drivers/gpu/drm/i915/intel_lrc.c +6 -9
@@ -507,17 +507,16 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring,return false; } -static void get_context_status (struct intel_engine_cs *ring, -u8 read_pointer, -u32 *status,u32 *context_id) +static u32 get_context_status (struct intel_engine_cs *ring,u8 read_pointer, +u32 *context_id) {struct drm_i915_private *dev_priv = ring->dev->dev_private; -if (WARN_ON (read_pointer >=GEN8_CSB_ENTRIES )) -return ; + read_pointer %=GEN8_CSB_ENTRIES ; - *status =I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); + +return I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); }/**
@@ -547,9 +546,7 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)spin_lock (&ring->execlist_lock);while (read_pointer < write_pointer) { - -get_context_status (ring, ++read_pointer %GEN8_CSB_ENTRIES , - &status, &status_id); + status =get_context_status (ring, ++read_pointer, &status_id);if (status &GEN8_CTX_STATUS_IDLE_ACTIVE )continue ;
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH 2/2 drm/i915: Execlist irq handler micro optimisations
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.
--- drivers/gpu/drm/i915/intel_lrc.c | 91 ++++++++++++++++----------------- drivers/gpu/drm/i915/intel_ringbuffer.h | 1 + 2 files changed, 44 insertions(+), 48 deletions(-)
drivers/gpu/drm/i915/intel_lrc.c +43 -48
@@ -269,6 +269,9 @@ logical_ring_init_platform_invariants(struct intel_engine_cs *ring) {struct drm_device *dev = ring->dev; +if (IS_GEN8 (dev) ||IS_GEN9 (dev)) + ring->idle_lite_restore_wa = ~0 ; + ring->disable_lite_restore_wa = (IS_SKL_REVID (dev,0 ,SKL_REVID_B0 ) ||IS_BXT_REVID (dev,0 ,BXT_REVID_A1 )) && (ring->id ==VCS || ring->id ==VCS2 );
@@ -424,7 +427,7 @@ static void execlists_submit_requests(struct drm_i915_gem_request *rq0,static void execlists_context_unqueue (struct intel_engine_cs *ring) {struct drm_i915_gem_request *req0 =NULL , *req1 =NULL ; -struct drm_i915_gem_request *cursor =NULL , *tmp =NULL ; +struct drm_i915_gem_request *cursor, *tmp;assert_spin_locked (&ring->execlist_lock);
@@ -434,9 +437,6 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring)*/ WARN_ON (!intel_irqs_enabled (ring->dev->dev_private)); -if (list_empty (&ring->execlist_queue)) -return ; -/* Try to read in pairs */ list_for_each_entry_safe (cursor, tmp, &ring->execlist_queue, execlist_link) {
@@ -451,37 +451,35 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring) req0 = cursor; }else { req1 = cursor; +WARN_ON (req1->elsp_submitted);break ; } } -if (IS_GEN8 (ring->dev) ||IS_GEN9 (ring->dev)) { +if (unlikely (!req0)) +return ; + +if (req0->elsp_submitted & ring->idle_lite_restore_wa) {/* -* WaIdleLiteRestore: make sure we never cause a lite -* restore with HEAD==TAIL +* WaIdleLiteRestore: make sure we never cause a lite restore +* with HEAD==TAIL. +* +* Apply the wa NOOPS to prevent ring:HEAD == req:TAIL as we +* resubmit the request. See gen8_emit_request() for where we +* prepare the padding after the end of the request. */ -if (req0->elsp_submitted) { -/* -* Apply the wa NOOPS to prevent ring:HEAD == req:TAIL -* as we resubmit the request. See gen8_emit_request() -* for where we prepare the padding after the end of the -* request. -*/ -struct intel_ringbuffer *ringbuf; +struct intel_ringbuffer *ringbuf; - ringbuf = req0->ctx->engine[ring->id].ringbuf; - req0->tail +=8 ; - req0->tail &= ringbuf->size -1 ; - } + ringbuf = req0->ctx->engine[ring->id].ringbuf; + req0->tail +=8 ; + req0->tail &= ringbuf->size -1 ; } -WARN_ON (req1 && req1->elsp_submitted); -execlists_submit_requests (req0, req1); } -static bool execlists_check_remove_request (struct intel_engine_cs *ring, -u32 request_id) +static unsigned int +execlists_check_remove_request (struct intel_engine_cs *ring,u32 request_id) {struct drm_i915_gem_request *head_req;
@@ -491,20 +489,21 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring, struct drm_i915_gem_request, execlist_link); -if (head_req !=NULL ) { -if (intel_execlists_ctx_id (head_req->ctx, ring) == request_id) { -WARN (head_req->elsp_submitted ==0 , -"Never submitted head request\n" ); +if (!head_req) +return 0 ; + +if (unlikely (intel_execlists_ctx_id (head_req->ctx, ring) != request_id)) +return 0 ; -if (--head_req->elsp_submitted <=0 ) { -list_move_tail (&head_req->execlist_link, - &ring->execlist_retired_req_list); -return true; - } - } - } +WARN (head_req->elsp_submitted ==0 ,"Never submitted head request\n" ); -return false; +if (--head_req->elsp_submitted >0 ) +return 0 ; + +list_move_tail (&head_req->execlist_link, + &ring->execlist_retired_req_list); + +return 1 ; } static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer,
@@ -551,7 +550,7 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)if (status &GEN8_CTX_STATUS_IDLE_ACTIVE )continue ; -if (status &GEN8_CTX_STATUS_PREEMPTED ) { +if (unlikely (status &GEN8_CTX_STATUS_PREEMPTED )) {if (status &GEN8_CTX_STATUS_LITE_RESTORE ) {if (execlists_check_remove_request (ring, status_id))WARN (1 ,"Lite Restored request removed from queue\n" );
@@ -559,21 +558,16 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)WARN (1 ,"Preemption without Lite Restore\n" ); } -if ((status &GEN8_CTX_STATUS_ACTIVE_IDLE ) || - (status &GEN8_CTX_STATUS_ELEMENT_SWITCH )) { -if (execlists_check_remove_request (ring, status_id)) - submit_contexts++; - } +if (status & (GEN8_CTX_STATUS_ACTIVE_IDLE | +GEN8_CTX_STATUS_ELEMENT_SWITCH )) + submit_contexts += +execlists_check_remove_request (ring, status_id); } -if (ring->disable_lite_restore_wa) { -/* Prevent a ctx to preempt itself */ -if ((status &GEN8_CTX_STATUS_ACTIVE_IDLE ) && - (submit_contexts !=0 )) -execlists_context_unqueue (ring); - }else if (submit_contexts !=0 ) { +if (submit_contexts && (!ring->disable_lite_restore_wa || + (ring->disable_lite_restore_wa && (status & +GEN8_CTX_STATUS_ACTIVE_IDLE ))))execlists_context_unqueue (ring); - }spin_unlock (&ring->execlist_lock);
@@ -2028,6 +2022,7 @@ void intel_logical_ring_cleanup(struct intel_engine_cs *ring) ring->status_page.obj =NULL ; } + ring->idle_lite_restore_wa =0 ; ring->disable_lite_restore_wa = false; ring->ctx_desc_template =0 ;
drivers/gpu/drm/i915/intel_ringbuffer.h +1 -0
@@ -272,6 +272,7 @@ struct intel_engine_cs {struct list_head execlist_queue;struct list_head execlist_retired_req_list;u8 next_context_status_buffer; +unsigned int idle_lite_restore_wa;bool disable_lite_restore_wa;u32 ctx_desc_template;u32 irq_keep_mask;/* bitmask for interrupts that should not be masked */
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH 2/2] drm/i915: Execlist irq handler micro optimisations
Quoted 6 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
Quoted 6 lines
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.
Sadly there are panics here to be taken care of before optimisations. :|
Quoted 43 lines
Signed-off-by Tvrtko Ursulin <[email protected]>--- drivers/gpu/drm/i915/intel_lrc.c | 91 ++++++++++++++++----------------- drivers/gpu/drm/i915/intel_ringbuffer.h | 1 + 2 files changed, 44 insertions(+), 48 deletions(-)drivers/gpu/drm/i915/intel_lrc.c +4
-4@@ -269,6 +269,9 @@ logical_ring_init_platform_invariants(struct intel_engine_cs *ring) {struct drm_device *dev = ring->dev; +if (IS_GEN8 (dev) ||IS_GEN9 (dev)) + ring->idle_lite_restore_wa = ~0 ; + ring->disable_lite_restore_wa = (IS_SKL_REVID (dev,0 ,SKL_REVID_B0 ) ||IS_BXT_REVID (dev,0 ,BXT_REVID_A1 )) && (ring->id ==VCS || ring->id ==VCS2 );@@ -424,7 +427,7 @@ static void execlists_submit_requests(struct drm_i915_gem_request *rq0,static void execlists_context_unqueue (struct intel_engine_cs *ring) {struct drm_i915_gem_request *req0 =NULL , *req1 =NULL ; -struct drm_i915_gem_request *cursor =NULL , *tmp =NULL ; +struct drm_i915_gem_request *cursor, *tmp;assert_spin_locked (&ring->execlist_lock);@@ -434,9 +437,6 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring)*/ WARN_ON (!intel_irqs_enabled (ring->dev->dev_private)); -if (list_empty (&ring->execlist_queue)) -return ; -/* Try to read in pairs */ list_for_each_entry_safe (cursor, tmp, &ring->execlist_queue, execlist_link) {@@ -451,37 +451,35 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring) req0 = cursor; }else { req1 = cursor;
drivers/gpu/drm/i915/intel_lrc.c static void execlists_context_unqueue(struct intel_engine_cs *ring) · line 462
Quoted 10 lines
drivers/gpu/drm/i915/intel_lrc.c +5
-1+WARN_ON (req1->elsp_submitted);break ; } } -if (IS_GEN8 (ring->dev) ||IS_GEN9 (ring->dev)) { +if (unlikely (!req0)) +return ; + +if (req0->elsp_submitted & ring->idle_lite_restore_wa) {
If you are going for the microptimsation, just do
if (req->elsp_submitted)
We unconditionally prepare the ringbuffer for the wa and currently apply it everywhere (and future hw will not be taking this path, aiui at least). -Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v2 1/1 drm/i915: Execlist irq handler micro optimisations
In reply to Tvrtko UrsulinFrom: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.
v2:
* Avoid mmio reads when possible. (Chris Wilson)
* Use natural integer size for csb indices.
* Remove useless return value from execlists_update_context.
* Extract 32-bit ppgtt PDPs update so it is out of line and shared with two callers.
* Grab forcewake across all mmio operations to ease the load on uncore lock and use chepear mmio ops.
Version 2 now makes the irq handling code path ~20% smaller on 48-bit PPGTT hardware, and a little bit less elsewhere. Hot paths are mostly in-line now and hammering on the uncore spinlock is greatly reduced together with mmio traffic to an extent.
--- drivers/gpu/drm/i915/intel_lrc.c | 187 +++++++++++++++++--------------- drivers/gpu/drm/i915/intel_ringbuffer.h | 3 +- 2 files changed, 99 insertions(+), 91 deletions(-)
drivers/gpu/drm/i915/intel_lrc.c +97 -90
@@ -269,6 +269,9 @@ logical_ring_init_platform_invariants(struct intel_engine_cs *ring) {struct drm_device *dev = ring->dev; +if (IS_GEN8 (dev) ||IS_GEN9 (dev)) + ring->idle_lite_restore_wa = ~0 ; + ring->disable_lite_restore_wa = (IS_SKL_REVID (dev,0 ,SKL_REVID_B0 ) ||IS_BXT_REVID (dev,0 ,BXT_REVID_A1 )) && (ring->id ==VCS || ring->id ==VCS2 );
@@ -372,8 +375,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0, rq0->elsp_submitted++;/* You must always write both descriptors in the order below. */ -spin_lock (&dev_priv->uncore.lock); -intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL );I915_WRITE_FW (RING_ELSP (ring),upper_32_bits (desc[1 ]));I915_WRITE_FW (RING_ELSP (ring),lower_32_bits (desc[1 ]));
@@ -383,11 +384,18 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0,/* ELSP is a wo register, use another nearby reg for posting */ POSTING_READ_FW (RING_EXECLIST_STATUS_LO (ring)); -intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); -spin_unlock (&dev_priv->uncore.lock); } -static int execlists_update_context (struct drm_i915_gem_request *rq) +static void +execlists_update_context_pdps (struct i915_hw_ppgtt *ppgtt,u32 *reg_state) +{ +ASSIGN_CTX_PDP (ppgtt, reg_state,3 ); +ASSIGN_CTX_PDP (ppgtt, reg_state,2 ); +ASSIGN_CTX_PDP (ppgtt, reg_state,1 ); +ASSIGN_CTX_PDP (ppgtt, reg_state,0 ); +} + +static void execlists_update_context (struct drm_i915_gem_request *rq) {struct intel_engine_cs *ring = rq->ring;struct i915_hw_ppgtt *ppgtt = rq->ctx->ppgtt;
@@ -395,19 +403,13 @@ static int execlists_update_context(struct drm_i915_gem_request *rq) reg_state[CTX_RING_TAIL +1 ] = rq->tail; -if (ppgtt && !USES_FULL_48BIT_PPGTT (ppgtt->base.dev)) { -/* True 32b PPGTT with dynamic page allocation: update PDP -* registers and point the unallocated PDPs to scratch page. -* PML4 is allocated during ppgtt init, so this is not needed -* in 48-bit mode. -*/ -ASSIGN_CTX_PDP (ppgtt, reg_state,3 ); -ASSIGN_CTX_PDP (ppgtt, reg_state,2 ); -ASSIGN_CTX_PDP (ppgtt, reg_state,1 ); -ASSIGN_CTX_PDP (ppgtt, reg_state,0 ); - } - -return 0 ; +/* True 32b PPGTT with dynamic page allocation: update PDP +* registers and point the unallocated PDPs to scratch page. +* PML4 is allocated during ppgtt init, so this is not needed +* in 48-bit mode. +*/ +if (ppgtt && !USES_FULL_48BIT_PPGTT (ppgtt->base.dev)) +execlists_update_context_pdps (ppgtt, reg_state); } static void execlists_submit_requests(struct drm_i915_gem_request *rq0,
@@ -424,7 +426,7 @@ static void execlists_submit_requests(struct drm_i915_gem_request *rq0,static void execlists_context_unqueue (struct intel_engine_cs *ring) {struct drm_i915_gem_request *req0 =NULL , *req1 =NULL ; -struct drm_i915_gem_request *cursor =NULL , *tmp =NULL ; +struct drm_i915_gem_request *cursor, *tmp;assert_spin_locked (&ring->execlist_lock);
@@ -434,9 +436,6 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring)*/ WARN_ON (!intel_irqs_enabled (ring->dev->dev_private)); -if (list_empty (&ring->execlist_queue)) -return ; -/* Try to read in pairs */ list_for_each_entry_safe (cursor, tmp, &ring->execlist_queue, execlist_link) {
@@ -451,37 +450,35 @@ static void execlists_context_unqueue(struct intel_engine_cs *ring) req0 = cursor; }else { req1 = cursor; +WARN_ON (req1->elsp_submitted);break ; } } -if (IS_GEN8 (ring->dev) ||IS_GEN9 (ring->dev)) { +if (unlikely (!req0)) +return ; + +if (req0->elsp_submitted & ring->idle_lite_restore_wa) {/* -* WaIdleLiteRestore: make sure we never cause a lite -* restore with HEAD==TAIL +* WaIdleLiteRestore: make sure we never cause a lite restore +* with HEAD==TAIL. +* +* Apply the wa NOOPS to prevent ring:HEAD == req:TAIL as we +* resubmit the request. See gen8_emit_request() for where we +* prepare the padding after the end of the request. */ -if (req0->elsp_submitted) { -/* -* Apply the wa NOOPS to prevent ring:HEAD == req:TAIL -* as we resubmit the request. See gen8_emit_request() -* for where we prepare the padding after the end of the -* request. -*/ -struct intel_ringbuffer *ringbuf; +struct intel_ringbuffer *ringbuf; - ringbuf = req0->ctx->engine[ring->id].ringbuf; - req0->tail +=8 ; - req0->tail &= ringbuf->size -1 ; - } + ringbuf = req0->ctx->engine[ring->id].ringbuf; + req0->tail +=8 ; + req0->tail &= ringbuf->size -1 ; } -WARN_ON (req1 && req1->elsp_submitted); -execlists_submit_requests (req0, req1); } -static bool execlists_check_remove_request (struct intel_engine_cs *ring, -u32 request_id) +static unsigned int +execlists_check_remove_request (struct intel_engine_cs *ring,u32 request_id) {struct drm_i915_gem_request *head_req;
@@ -491,32 +488,39 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring, struct drm_i915_gem_request, execlist_link); -if (head_req !=NULL ) { -if (intel_execlists_ctx_id (head_req->ctx, ring) == request_id) { -WARN (head_req->elsp_submitted ==0 , -"Never submitted head request\n" ); +if (!head_req) +return 0 ; -if (--head_req->elsp_submitted <=0 ) { -list_move_tail (&head_req->execlist_link, - &ring->execlist_retired_req_list); -return true; - } - } - } +if (unlikely (intel_execlists_ctx_id (head_req->ctx, ring) != request_id)) +return 0 ; + +WARN (head_req->elsp_submitted ==0 ,"Never submitted head request\n" ); + +if (--head_req->elsp_submitted >0 ) +return 0 ; + +list_move_tail (&head_req->execlist_link, + &ring->execlist_retired_req_list); -return false; +return 1 ; }static u32 get_context_status (struct intel_engine_cs *ring,u8 read_pointer,u32 *context_id) {struct drm_i915_private *dev_priv = ring->dev->dev_private; +u32 status; read_pointer %=GEN8_CSB_ENTRIES ; - *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); + status =I915_READ_FW (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); -return I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); +if (status &GEN8_CTX_STATUS_IDLE_ACTIVE ) +return 0 ; + + *context_id =I915_READ_FW (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); + +return status; }/**
@@ -530,28 +534,27 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring) {struct drm_i915_private *dev_priv = ring->dev->dev_private;u32 status_pointer; -u8 read_pointer; -u8 write_pointer; +unsigned int read_pointer, write_pointer;u32 status =0 ;u32 status_id; -u32 submit_contexts =0 ; +unsigned int submit_contexts =0 ; + +spin_lock (&ring->execlist_lock); + +spin_lock (&dev_priv->uncore.lock); +intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL ); - status_pointer =I915_READ (RING_CONTEXT_STATUS_PTR (ring)); + status_pointer =I915_READ_FW (RING_CONTEXT_STATUS_PTR (ring)); read_pointer = ring->next_context_status_buffer; write_pointer =GEN8_CSB_WRITE_PTR (status_pointer);if (read_pointer > write_pointer) write_pointer +=GEN8_CSB_ENTRIES ; -spin_lock (&ring->execlist_lock); -while (read_pointer < write_pointer) { status =get_context_status (ring, ++read_pointer, &status_id); -if (status &GEN8_CTX_STATUS_IDLE_ACTIVE ) -continue ; - -if (status &GEN8_CTX_STATUS_PREEMPTED ) { +if (unlikely (status &GEN8_CTX_STATUS_PREEMPTED )) {if (status &GEN8_CTX_STATUS_LITE_RESTORE ) {if (execlists_check_remove_request (ring, status_id))WARN (1 ,"Lite Restored request removed from queue\n" );
@@ -559,38 +562,37 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)WARN (1 ,"Preemption without Lite Restore\n" ); } -if ((status &GEN8_CTX_STATUS_ACTIVE_IDLE ) || - (status &GEN8_CTX_STATUS_ELEMENT_SWITCH )) { -if (execlists_check_remove_request (ring, status_id)) - submit_contexts++; - } +if (status & (GEN8_CTX_STATUS_ACTIVE_IDLE | +GEN8_CTX_STATUS_ELEMENT_SWITCH )) + submit_contexts += +execlists_check_remove_request (ring, status_id); } -if (ring->disable_lite_restore_wa) { -/* Prevent a ctx to preempt itself */ -if ((status &GEN8_CTX_STATUS_ACTIVE_IDLE ) && - (submit_contexts !=0 )) -execlists_context_unqueue (ring); - }else if (submit_contexts !=0 ) { +if (submit_contexts && (!ring->disable_lite_restore_wa || + (ring->disable_lite_restore_wa && (status & +GEN8_CTX_STATUS_ACTIVE_IDLE ))))execlists_context_unqueue (ring); - } - -spin_unlock (&ring->execlist_lock); - -if (unlikely (submit_contexts >2 )) -DRM_ERROR ("More than two context complete events?\n" ); ring->next_context_status_buffer = write_pointer %GEN8_CSB_ENTRIES ;/* Update the read pointer to the old write pointer. Manual ringbuffer * management ftw </sarcasm> */ -I915_WRITE (RING_CONTEXT_STATUS_PTR (ring), -_MASKED_FIELD (GEN8_CSB_READ_PTR_MASK , - ring->next_context_status_buffer <<8 )); +I915_WRITE_FW (RING_CONTEXT_STATUS_PTR (ring), +_MASKED_FIELD (GEN8_CSB_READ_PTR_MASK , + ring->next_context_status_buffer <<8 )); + +intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); +spin_unlock (&dev_priv->uncore.lock); + +spin_unlock (&ring->execlist_lock); + +if (unlikely (submit_contexts >2 )) +DRM_ERROR ("More than two context complete events?\n" ); }static int execlists_context_queue (struct drm_i915_gem_request *request) { +struct drm_i915_private *dev_priv = request->i915;struct intel_engine_cs *ring = request->ring;struct drm_i915_gem_request *cursor;int num_elements =0 ;
@@ -622,9 +624,16 @@ static int execlists_context_queue(struct drm_i915_gem_request *request) }list_add_tail (&request->execlist_link, &ring->execlist_queue); -if (num_elements ==0 ) +if (num_elements ==0 ) { +spin_lock (&dev_priv->uncore.lock); +intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL ); +execlists_context_unqueue (ring); +intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); +spin_unlock (&dev_priv->uncore.lock); + } +spin_unlock_irq (&ring->execlist_lock);return 0 ;
@@ -2013,6 +2022,7 @@ void intel_logical_ring_cleanup(struct intel_engine_cs *ring) ring->status_page.obj =NULL ; } + ring->idle_lite_restore_wa =0 ; ring->disable_lite_restore_wa = false; ring->ctx_desc_template =0 ;
@@ -2417,10 +2427,7 @@ populate_lr_context(struct intel_context *ctx, struct drm_i915_gem_object *ctx_o* With dynamic page allocation, PDPs may not be allocated at * this point. Point the unallocated PDPs to the scratch page */ -ASSIGN_CTX_PDP (ppgtt, reg_state,3 ); -ASSIGN_CTX_PDP (ppgtt, reg_state,2 ); -ASSIGN_CTX_PDP (ppgtt, reg_state,1 ); -ASSIGN_CTX_PDP (ppgtt, reg_state,0 ); +execlists_update_context_pdps (ppgtt, reg_state); }if (ring->id ==RCS ) {
drivers/gpu/drm/i915/intel_ringbuffer.h +2 -1
@@ -271,7 +271,8 @@ struct intel_engine_cs {spinlock_t execlist_lock;struct list_head execlist_queue;struct list_head execlist_retired_req_list; -u8 next_context_status_buffer; +unsigned int next_context_status_buffer; +unsigned int idle_lite_restore_wa;bool disable_lite_restore_wa;u32 ctx_desc_template;u32 irq_keep_mask;/* bitmask for interrupts that should not be masked */
Signature · 6 lines
1.9.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v2] drm/i915: Execlist irq handler micro optimisations
Quoted 23 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.v2:
* Avoid mmio reads when possible. (Chris Wilson)
* Use natural integer size for csb indices.
* Remove useless return value fromexeclists_update_context.
* Extract 32-bit ppgtt PDPs update so it is out of line and shared with two callers.
* Grab forcewake across all mmio operations to ease the load on uncore lock and use chepear mmio ops.
Quoted 5 lines
Version 2 now makes the irq handling code path ~20% smaller on 48-bit PPGTT hardware, and a little bit less elsewhere. Hot paths are mostly in-line now and hammering on the uncore spinlock is greatly reduced together with mmio traffic to an extent.
Is gem_latency an interesting benchmark for this?
Five runs on vanilla:
747693/1: 9.080us 2.000us 2.000us 121.840us 742108/1: 9.060us 2.520us 2.520us 122.645us 744097/1: 9.060us 2.000us 2.000us 122.372us 744056/1: 9.180us 1.980us 1.980us 122.394us 742610/1: 9.040us 2.560us 2.560us 122.525us
Five runs with this patch series:
786532/1: 10.760us 1.520us 1.520us 115.705us 780735/1: 10.740us 1.580us 1.580us 116.558us 783706/1: 10.800us 1.460us 1.460us 116.280us 784135/1: 10.800us 1.520us 1.520us 116.151us 784037/1: 10.740us 1.520us 1.520us 116.250us
So it looks all got better apart from dispatch latency.
5% more throughput, 30% better consumer and producer latencies, 5% less CPU usage, but 18% worse dispatch latency.
Comments?
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v2] drm/i915: Execlist irq handler micro optimisations
Quoted 26 lines · Tvrtko Ursulin
Quoted 23 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.v2:
* Avoid mmio reads when possible. (Chris Wilson)
* Use natural integer size for csb indices.
* Remove useless return value fromexeclists_update_context.
* Extract 32-bit ppgtt PDPs update so it is out of line and shared with two callers.
* Grab forcewake across all mmio operations to ease the load on uncore lock and use chepear mmio ops.
Quoted 7 lines
Quoted 5 lines
Version 2 now makes the irq handling code path ~20% smaller on 48-bit PPGTT hardware, and a little bit less elsewhere. Hot paths are mostly in-line now and hammering on the uncore spinlock is greatly reduced together with mmio traffic to an extent.
Is
gem_latencyan interesting benchmark for th
Yes, we should be able to detect changes on the order of 100ns and if the results are stable and above the noise, then definitely.
"./gem_latency" sends one batch and then waits up it, so I only the patch to directly affect the dispatch latency. I'd say the wake up latency is solely due to reducing the spinlock contextion.
"./gem_latency -n 100" would queue 100 no-op batches before the measurement. That may help to look at the overhead of handling the context-switch interrupt.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v2] drm/i915: Execlist irq handler micro optimisations
In reply to Tvrtko UrsulinQuoted 23 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.v2:
* Avoid mmio reads when possible. (Chris Wilson)
* Use natural integer size for csb indices.
* Remove useless return value fromexeclists_update_context.
* Extract 32-bit ppgtt PDPs update so it is out of line and shared with two callers.
* Grab forcewake across all mmio operations to ease the load on uncore lock and use chepear mmio ops.
Quoted 5 lines
Version 2 now makes the irq handling code path ~20% smaller on 48-bit PPGTT hardware, and a little bit less elsewhere. Hot paths are mostly in-line now and hammering on the uncore spinlock is greatly reduced together with mmio traffic to an extent.
Did you notice that ring->next_context_status_buffer is redundant as we also have that information to hand in status_pointer?
What's your thinking for
if (req->elsp_submitted & ring->gen8_9)
vs a plain
if (req->elsp_submitted)
?
The tidies look good. Be useful to double check whether gem_latency is behaving as a canary, it's a bit of a puzzle why that first dispatch latency would grow.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v2] drm/i915: Execlist irq handler micro optimisations
Quoted 24 lines · Chris Wilson
Quoted 23 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.v2:
* Avoid mmio reads when possible. (Chris Wilson)
* Use natural integer size for csb indices.
* Remove useless return value fromexeclists_update_context.
* Extract 32-bit ppgtt PDPs update so it is out of line and shared with two callers.
* Grab forcewake across all mmio operations to ease the load on uncore lock and use chepear mmio ops.
Quoted 8 lines
Quoted 5 lines
Version 2 now makes the irq handling code path ~20% smaller on 48-bit PPGTT hardware, and a little bit less elsewhere. Hot paths are mostly in-line now and hammering on the uncore spinlock is greatly reduced together with mmio traffic to an extent.
Did you notice that
ring->next_context_status_bufferis redundant as we also have that information to hand instatus_pointer?
I didn't and don't know that part that well. There might be some future proofing issues around it as well.
Quoted 8 lines
What's your thinking for
if (req->elsp_submitted & ring->gen8_9)vs a plain
if (req->elsp_submitted)?
Another don't know this part that well. Is it not useful to not submit two noops if they are not needed? Do they still end up submitted to the GPU somehow?
Quoted 3 lines
The tidies look good. Be useful to double check whether
gem_latencyis behaving as a canary, it's a bit of a puzzle why that first dispatch latency would grow.
Yes a puzzle, no idea how and why. But "gem_latency -n 100" does not show this regression. I've done a hundred runs and these are the results:
* Throughput up 4.04%
* Dispatch latency down 0.37%
* Consumer and producer latencies down 22.53%
* CPU time down 2.25%
So it all looks good.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [PATCH v2] drm/i915: Execlist irq handler micro optimisations
Quoted 32 lines · Tvrtko Ursulin
Quoted 30 lines · Chris Wilson
Quoted 28 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Assorted changes most likely without any practical effect apart from a tiny reduction in generated code for the interrupt handler and request submission.
* Remove needless initialization.
* Improve cache locality by reorganizing code and/or using branch hints to keep unexpected or error conditions out of line.
* Favor busy submit path vs. empty queue.
* Less branching in hot-paths.v2:
* Avoid mmio reads when possible. (Chris Wilson)
* Use natural integer size for csb indices.
* Remove useless return value fromexeclists_update_context.
* Extract 32-bit ppgtt PDPs update so it is out of line and shared with two callers.
* Grab forcewake across all mmio operations to ease the load on uncore lock and use chepear mmio ops.Version 2 now makes the irq handling code path ~20% smaller on 48-bit PPGTT hardware, and a little bit less elsewhere. Hot paths are mostly in-line now and hammering on the uncore spinlock is greatly reduced together with mmio traffic to an extent.
Quoted 5 lines
Quoted 2 lines
Did you notice that
ring->next_context_status_bufferis redundant as we also have that information to hand instatus_pointer?I didn't and don't know that part that well. There might be some future proofing issues around it as well.
Unlikely :-p
Quoted 4 lines
Quoted 4 lines
What's your thinking for
if (req->elsp_submitted & ring->gen8_9)
Quoted 8 lines
Quoted 4 lines
vs a plain
if (req->elsp_submitted)?
Another don't know this part that well. Is it not useful to not submit two noops if they are not needed? Do they still end up submitted to the GPU somehow?
The command streamer always has to execute them since they lie between the last dispatch TAIL and the next TAIL (in the lrc). All we do here is to tweak the request->tail value, that may or may not be used the next time we write the ELSP (depending on whether we are submitting the same live request again). (The next request's tail will include the noops before it's dispatch.)
Quoted 8 lines
Quoted 3 lines
The tidies look good. Be useful to double check whether
gem_latencyis behaving as a canary, it's a bit of a puzzle why that first dispatch latency would grow.Yes a puzzle, no idea how and why. But "
gem_latency-n 100" does not show this regression. I've done a hundred runs and these are the results:
Quoted 6 lines
* Throughput up 4.04%
* Dispatch latency down 0.37%
* Consumer and producer latencies down 22.53%
* CPU time down 2.25%So it all looks good.
Yup.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 27 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Only caller to
get_context_statusensures read pointer stays in range so the WARN is impossible. Also, if the WARN would be triggered by a hypothetical new caller stale status would be returned to them.Maybe it is better to wrap the pointer in the function itself then to avoid both and even results in smaller code.
Signed-off-by Tvrtko Ursulin <[email protected]>--- drivers/gpu/drm/i915/intel_lrc.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_lrc.c +1
-3@@ -507,17 +507,16 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring,return false; } -static void get_context_status (struct intel_engine_cs *ring, -u8 read_pointer, -u32 *status,u32 *context_id) +static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer,
drivers/gpu/drm/i915/intel_lrc.c static bool execlists_check_remove_request(struct intel_engine_cs *ring, · line 517
Quoted 10 lines
drivers/gpu/drm/i915/intel_lrc.c +2
-3+ u32 *context_id) {struct drm_i915_private *dev_priv = ring->dev->dev_private; -if (WARN_ON (read_pointer >=GEN8_CSB_ENTRIES )) -return ; + read_pointer %=GEN8_CSB_ENTRIES ; - *status =I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer));
Micro-optimising hat says not to even do the uncached, spinlocked mmio read when not required.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 36 lines · Chris Wilson
Quoted 35 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Only caller to
get_context_statusensures read pointer stays in range so the WARN is impossible. Also, if the WARN would be triggered by a hypothetical new caller stale status would be returned to them.Maybe it is better to wrap the pointer in the function itself then to avoid both and even results in smaller code.
Signed-off-by Tvrtko Ursulin <[email protected]>--- drivers/gpu/drm/i915/intel_lrc.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_lrc.c +3
-5@@ -507,17 +507,16 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring,return false; } -static void get_context_status (struct intel_engine_cs *ring, -u8 read_pointer, -u32 *status,u32 *context_id) +static u32 get_context_status (struct intel_engine_cs *ring,u8 read_pointer, +u32 *context_id) {struct drm_i915_private *dev_priv = ring->dev->dev_private; -if (WARN_ON (read_pointer >=GEN8_CSB_ENTRIES )) -return ; + read_pointer %=GEN8_CSB_ENTRIES ;
Quoted 5 lines
drivers/gpu/drm/i915/intel_lrc.c static bool execlists_check_remove_request(struct intel_engine_cs *ring, · line 517
Quoted 2 lines
drivers/gpu/drm/i915/intel_lrc.c +0
-1- *status =I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer));Micro-optimising hat says not to even do the uncached, spinlocked mmio read when not required.
You mean move the forcewake grab out from elsp write to cover all mmio reads? These two patches make the irq handler around 3.7% smaller and moving the forcewake/uncore lock shrinks that by a 1% more. Must be faster as well, if someone could measure it. :)
drivers/gpu/drm/i915/intel_lrc.c +28 -18
@@ -375,8 +375,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0, rq0->elsp_submitted++;/* You must always write both descriptors in the order below. */ -spin_lock (&dev_priv->uncore.lock); -intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL );I915_WRITE_FW (RING_ELSP (ring),upper_32_bits (desc[1 ]));I915_WRITE_FW (RING_ELSP (ring),lower_32_bits (desc[1 ]));
@@ -386,8 +384,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0,/* ELSP is a wo register, use another nearby reg for posting */ POSTING_READ_FW (RING_EXECLIST_STATUS_LO (ring)); -intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); -spin_unlock (&dev_priv->uncore.lock); }static int execlists_update_context (struct drm_i915_gem_request *rq)
@@ -513,9 +509,9 @@ static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer, read_pointer %=GEN8_CSB_ENTRIES ; - *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); + *context_id =I915_READ_FW (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); -return I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); +return I915_READ_FW (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); }/**
@@ -535,15 +531,18 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring)u32 status_id;u32 submit_contexts =0 ; - status_pointer =I915_READ (RING_CONTEXT_STATUS_PTR (ring)); +spin_lock (&ring->execlist_lock); + +spin_lock (&dev_priv->uncore.lock); +intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL ); + + status_pointer =I915_READ_FW (RING_CONTEXT_STATUS_PTR (ring)); read_pointer = ring->next_context_status_buffer; write_pointer =GEN8_CSB_WRITE_PTR (status_pointer);if (read_pointer > write_pointer) write_pointer +=GEN8_CSB_ENTRIES ; -spin_lock (&ring->execlist_lock); -while (read_pointer < write_pointer) { status =get_context_status (ring, ++read_pointer, &status_id);
@@ -569,22 +568,26 @@ void intel_lrc_irq_handler(struct intel_engine_cs *ring) GEN8_CTX_STATUS_ACTIVE_IDLE))))execlists_context_unqueue (ring ); -spin_unlock (&ring->execlist_lock); - -if (unlikely (submit_contexts >2 )) -DRM_ERROR ("More than two context complete events?\n" ); - ring->next_context_status_buffer = write_pointer %GEN8_CSB_ENTRIES ;/* Update the read pointer to the old write pointer. Manual ringbuffer * management ftw </sarcasm> */ -I915_WRITE (RING_CONTEXT_STATUS_PTR (ring), -_MASKED_FIELD (GEN8_CSB_READ_PTR_MASK , - ring->next_context_status_buffer <<8 )); +I915_WRITE_FW (RING_CONTEXT_STATUS_PTR (ring), +_MASKED_FIELD (GEN8_CSB_READ_PTR_MASK , + ring->next_context_status_buffer <<8 )); + +intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); +spin_unlock (&dev_priv->uncore.lock); + +spin_unlock (&ring->execlist_lock); + +if (unlikely (submit_contexts >2 )) +DRM_ERROR ("More than two context complete events?\n" ); }static int execlists_context_queue (struct drm_i915_gem_request *request) { +struct drm_i915_private *dev_priv = request->i915;struct intel_engine_cs *ring = request->ring;struct drm_i915_gem_request *cursor;int num_elements =0 ;
@@ -616,9 +619,16 @@ static int execlists_context_queue(struct drm_i915_gem_request *request) }list_add_tail (&request->execlist_link, &ring->execlist_queue); -if (num_elements ==0 ) +if (num_elements ==0 ) { +spin_lock (&dev_priv->uncore.lock); +intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL ); +execlists_context_unqueue (ring); +intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); +spin_unlock (&dev_priv->uncore.lock); + } +spin_unlock_irq (&ring->execlist_lock);return 0 ;
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 44 lines · Tvrtko Ursulin
Quoted 36 lines · Chris Wilson
Quoted 35 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Only caller to
get_context_statusensures read pointer stays in range so the WARN is impossible. Also, if the WARN would be triggered by a hypothetical new caller stale status would be returned to them.Maybe it is better to wrap the pointer in the function itself then to avoid both and even results in smaller code.
Signed-off-by Tvrtko Ursulin <[email protected]>--- drivers/gpu/drm/i915/intel_lrc.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_lrc.c +3
-5@@ -507,17 +507,16 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring,return false; } -static void get_context_status (struct intel_engine_cs *ring, -u8 read_pointer, -u32 *status,u32 *context_id) +static u32 get_context_status (struct intel_engine_cs *ring,u8 read_pointer, +u32 *context_id) {struct drm_i915_private *dev_priv = ring->dev->dev_private; -if (WARN_ON (read_pointer >=GEN8_CSB_ENTRIES )) -return ; + read_pointer %=GEN8_CSB_ENTRIES ;Quoted 5 lines
drivers/gpu/drm/i915/intel_lrc.c static bool execlists_check_remove_request(struct intel_engine_cs *ring, · line 517
Quoted 2 lines
drivers/gpu/drm/i915/intel_lrc.c +0
-1- *status =I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer));Micro-optimising hat says not to even do the uncached, spinlocked mmio read when not required.
Quoted 4 lines
You mean move the forcewake grab out from elsp write to cover all mmio reads? These two patches make the irq handler around 3.7% smaller and moving the forcewake/uncore lock shrinks that by a 1% more. Must be faster as well, if someone could measure it. :)
If only we already have benchmarks capable of measuring such optimisations!
Quoted 23 lines
drivers/gpu/drm/i915/intel_lrc.c +0
-4@@ -375,8 +375,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0, rq0->elsp_submitted++;/* You must always write both descriptors in the order below. */ -spin_lock (&dev_priv->uncore.lock); -intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL );I915_WRITE_FW (RING_ELSP (ring),upper_32_bits (desc[1 ]));I915_WRITE_FW (RING_ELSP (ring),lower_32_bits (desc[1 ]));@@ -386,8 +384,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0,/* ELSP is a wo register, use another nearby reg for posting */ POSTING_READ_FW (RING_EXECLIST_STATUS_LO (ring)); -intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); -spin_unlock (&dev_priv->uncore.lock); }static int execlists_update_context (struct drm_i915_gem_request *rq)
drivers/gpu/drm/i915/intel_lrc.c static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer, · line 512
Quoted 5 lines
drivers/gpu/drm/i915/intel_lrc.c +1
-1@@ -513,9 +509,9 @@ static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer, read_pointer %=GEN8_CSB_ENTRIES ; - *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); + *context_id =I915_READ_FW (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer));
I was also suggesting that we don't need this read in almost 25% of cases! :)
drivers/gpu/drm/i915/intel_lrc.c static int execlists_context_queue(struct drm_i915_gem_request *request) · line 623
Quoted 7 lines
drivers/gpu/drm/i915/intel_lrc.c +2
-1@@ -616,9 +619,16 @@ static int execlists_context_queue(struct drm_i915_gem_request *request) }list_add_tail (&request->execlist_link, &ring->execlist_queue); -if (num_elements ==0 ) +if (num_elements ==0 ) { +spin_lock (&dev_priv->uncore.lock);
We need the irq variants here.
drivers/gpu/drm/i915/intel_lrc.c static int execlists_context_queue(struct drm_i915_gem_request *request) · line 624
Quoted 1 line
drivers/gpu/drm/i915/intel_lrc.c +1
-0+intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL );
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 45 lines · Chris Wilson
Quoted 44 lines · Tvrtko Ursulin
Quoted 41 lines · Chris Wilson
Quoted 27 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
Only caller to
get_context_statusensures read pointer stays in range so the WARN is impossible. Also, if the WARN would be triggered by a hypothetical new caller stale status would be returned to them.Maybe it is better to wrap the pointer in the function itself then to avoid both and even results in smaller code.
Signed-off-by Tvrtko Ursulin <[email protected]>--- drivers/gpu/drm/i915/intel_lrc.c | 15 ++++++--------- 1 file changed, 6 insertions(+), 9 deletions(-)drivers/gpu/drm/i915/intel_lrc.c +1
-3@@ -507,17 +507,16 @@ static bool execlists_check_remove_request(struct intel_engine_cs *ring,return false; } -static void get_context_status (struct intel_engine_cs *ring, -u8 read_pointer, -u32 *status,u32 *context_id) +static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer,drivers/gpu/drm/i915/intel_lrc.c static bool execlists_check_remove_request(struct intel_engine_cs *ring, · line 517
Quoted 10 lines
drivers/gpu/drm/i915/intel_lrc.c +2
-3+ u32 *context_id) {struct drm_i915_private *dev_priv = ring->dev->dev_private; -if (WARN_ON (read_pointer >=GEN8_CSB_ENTRIES )) -return ; + read_pointer %=GEN8_CSB_ENTRIES ; - *status =I915_READ (RING_CONTEXT_STATUS_BUF_LO (ring, read_pointer)); *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer));Micro-optimising hat says not to even do the uncached, spinlocked mmio read when not required.
Quoted 7 lines
Quoted 4 lines
You mean move the forcewake grab out from elsp write to cover all mmio reads? These two patches make the irq handler around 3.7% smaller and moving the forcewake/uncore lock shrinks that by a 1% more. Must be faster as well, if someone could measure it. :)
If only we already have benchmarks capable of measuring such optimisations!
We do?
Quoted 24 lines
Quoted 24 lines
drivers/gpu/drm/i915/intel_lrc.c +0
-4@@ -375,8 +375,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0, rq0->elsp_submitted++;/* You must always write both descriptors in the order below. */ -spin_lock (&dev_priv->uncore.lock); -intel_uncore_forcewake_get__locked (dev_priv,FORCEWAKE_ALL );I915_WRITE_FW (RING_ELSP (ring),upper_32_bits (desc[1 ]));I915_WRITE_FW (RING_ELSP (ring),lower_32_bits (desc[1 ]));@@ -386,8 +384,6 @@ static void execlists_elsp_write(struct drm_i915_gem_request *rq0,/* ELSP is a wo register, use another nearby reg for posting */ POSTING_READ_FW (RING_EXECLIST_STATUS_LO (ring)); -intel_uncore_forcewake_put__locked (dev_priv,FORCEWAKE_ALL ); -spin_unlock (&dev_priv->uncore.lock); }static int execlists_update_context (struct drm_i915_gem_request *rq)@@ -513,9 +509,9 @@ static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer,
Quoted 7 lines
drivers/gpu/drm/i915/intel_lrc.c static u32 get_context_status(struct intel_engine_cs *ring, u8 read_pointer, · line 512
Quoted 4 lines
drivers/gpu/drm/i915/intel_lrc.c +1
-1read_pointer %=GEN8_CSB_ENTRIES ; - *context_id =I915_READ (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer)); + *context_id =I915_READ_FW (RING_CONTEXT_STATUS_BUF_HI (ring, read_pointer));I was also suggesting that we don't need this read in almost 25% of cases! :)
Oh right, yeah I can do that.
Quoted 9 lines
drivers/gpu/drm/i915/intel_lrc.c static int execlists_context_queue(struct drm_i915_gem_request *request) · line 623
Quoted 7 lines
drivers/gpu/drm/i915/intel_lrc.c +2
-1@@ -616,9 +619,16 @@ static int execlists_context_queue(struct drm_i915_gem_request *request) }list_add_tail (&request->execlist_link, &ring->execlist_queue); -if (num_elements ==0 ) +if (num_elements ==0 ) { +spin_lock (&dev_priv->uncore.lock);We need the irq variants here.
No since the execlist lock further up already disables interrupts.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI✗ Fi.CI.BAT: failure for series starting with [2/2] drm/i915: Execlist irq handler micro optimisations (rev3)
In reply to Tvrtko Ursulin== Summary ==
== Summary ==
Series 3304v3 Series without cover letter
2016-02-12T12:00:45.925088 http://patchwork.freedesktop.org/api/1.0/series/3304/revisions/3/mbox/
Applying: drm/i915: Execlist irq handler micro optimisations Repository lacks necessary blobs to fall back on 3-way merge. Cannot fall back to three-way merge.
Patch failed at 0001 drm/i915: Execlist irq handler micro optimisations
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx