From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 15/37] drm/i915: Export i915_request_skip()
Date: Fri, 29 Jun 2018 13:10:32 +0100 [thread overview]
Message-ID: <4dd64d3f-9e87-bd76-bc17-2be39815d843@linux.intel.com> (raw)
In-Reply-To: <20180629075348.27358-15-chris@chris-wilson.co.uk>
On 29/06/2018 08:53, Chris Wilson wrote:
> In the next patch, we will want to start skipping requests on failing to
> complete their payloads. So export the utility function current used to
> make requests inoperable following a failed gpu reset.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/i915_gem.c | 25 +++----------------------
> drivers/gpu/drm/i915/i915_request.c | 21 +++++++++++++++++++++
> drivers/gpu/drm/i915/i915_request.h | 2 ++
> 3 files changed, 26 insertions(+), 22 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> index c13d5b78a02e..8ae293c75ae9 100644
> --- a/drivers/gpu/drm/i915/i915_gem.c
> +++ b/drivers/gpu/drm/i915/i915_gem.c
> @@ -3084,25 +3084,6 @@ int i915_gem_reset_prepare(struct drm_i915_private *dev_priv)
> return err;
> }
>
> -static void skip_request(struct i915_request *request)
> -{
> - void *vaddr = request->ring->vaddr;
> - u32 head;
> -
> - /* As this request likely depends on state from the lost
> - * context, clear out all the user operations leaving the
> - * breadcrumb at the end (so we get the fence notifications).
> - */
> - head = request->head;
> - if (request->postfix < head) {
> - memset(vaddr + head, 0, request->ring->size - head);
> - head = 0;
> - }
> - memset(vaddr + head, 0, request->postfix - head);
> -
> - dma_fence_set_error(&request->fence, -EIO);
> -}
> -
> static void engine_skip_context(struct i915_request *request)
> {
> struct intel_engine_cs *engine = request->engine;
> @@ -3117,10 +3098,10 @@ static void engine_skip_context(struct i915_request *request)
>
> list_for_each_entry_continue(request, &engine->timeline.requests, link)
> if (request->gem_context == hung_ctx)
> - skip_request(request);
> + i915_request_skip(request, -EIO);
>
> list_for_each_entry(request, &timeline->requests, link)
> - skip_request(request);
> + i915_request_skip(request, -EIO);
>
> spin_unlock(&timeline->lock);
> spin_unlock_irqrestore(&engine->timeline.lock, flags);
> @@ -3163,7 +3144,7 @@ i915_gem_reset_request(struct intel_engine_cs *engine,
>
> if (stalled) {
> i915_gem_context_mark_guilty(request->gem_context);
> - skip_request(request);
> + i915_request_skip(request, -EIO);
>
> /* If this context is now banned, skip all pending requests. */
> if (i915_gem_context_is_banned(request->gem_context))
> diff --git a/drivers/gpu/drm/i915/i915_request.c b/drivers/gpu/drm/i915/i915_request.c
> index d618e7127e88..51f28786b0e4 100644
> --- a/drivers/gpu/drm/i915/i915_request.c
> +++ b/drivers/gpu/drm/i915/i915_request.c
> @@ -962,6 +962,27 @@ i915_request_await_object(struct i915_request *to,
> return ret;
> }
>
> +void i915_request_skip(struct i915_request *rq, int error)
> +{
> + void *vaddr = rq->ring->vaddr;
> + u32 head;
> +
> + GEM_BUG_ON(!IS_ERR_VALUE((long)error));
Why not simply error >= 0 ? Error is an integer in this function, and in
dma_fence_set_error. In fact, looking at dma_fence_set_error it is
already checking for valid errno.
> + dma_fence_set_error(&rq->fence, error);
Was at the end before code movement.
> +
> + /*
> + * As this request likely depends on state from the lost
> + * context, clear out all the user operations leaving the
> + * breadcrumb at the end (so we get the fence notifications).
> + */
> + head = rq->infix;
Original assignment is head = rq->head. Looks to be the same but why
change it in code movement patch?
> + if (rq->postfix < head) {
> + memset(vaddr + head, 0, rq->ring->size - head);
> + head = 0;
> + }
> + memset(vaddr + head, 0, rq->postfix - head);
> +}
> +
> /*
> * NB: This function is not allowed to fail. Doing so would mean the the
> * request is not being tracked for completion but the work itself is
> diff --git a/drivers/gpu/drm/i915/i915_request.h b/drivers/gpu/drm/i915/i915_request.h
> index 7ee220ded9c9..a355a081485f 100644
> --- a/drivers/gpu/drm/i915/i915_request.h
> +++ b/drivers/gpu/drm/i915/i915_request.h
> @@ -258,6 +258,8 @@ void i915_request_add(struct i915_request *rq);
> void __i915_request_submit(struct i915_request *request);
> void i915_request_submit(struct i915_request *request);
>
> +void i915_request_skip(struct i915_request *request, int error);
> +
> void __i915_request_unsubmit(struct i915_request *request);
> void i915_request_unsubmit(struct i915_request *request);
>
>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-06-29 12:10 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 7:53 [PATCH 01/37] drm/i915/gtt: Add read only pages to gen8_pte_encode Chris Wilson
2018-06-29 7:53 ` [PATCH 02/37] drm/i915/gtt: Read-only pages for insert_entries on bdw+ Chris Wilson
2018-06-29 7:53 ` [PATCH 03/37] drm/i915: Prevent writing into a read-only object via a GGTT mmap Chris Wilson
2018-06-29 7:53 ` [PATCH 04/37] drm/i915: Reject attempted pwrites into a read-only object Chris Wilson
2018-06-29 7:53 ` [PATCH 05/37] drm/i915/userptr: Enable read-only support on gen8+ Chris Wilson
2018-06-29 7:53 ` [PATCH 06/37] drm/i915: Move rate-limiting request retire to after submission Chris Wilson
2018-06-29 10:00 ` Tvrtko Ursulin
2018-06-29 10:10 ` Chris Wilson
2018-06-29 7:53 ` [PATCH 07/37] drm/i915: Move engine request retirement to intel_engine_cs Chris Wilson
2018-06-29 7:53 ` [PATCH 08/37] drm/i915: Hold request reference for submission until retirement Chris Wilson
2018-06-29 7:53 ` [PATCH 09/37] drm/i915/execlists: Switch to rb_root_cached Chris Wilson
2018-07-11 13:20 ` Tvrtko Ursulin
2018-06-29 7:53 ` [PATCH 10/37] drm/i915: Reserve some priority bits for internal use Chris Wilson
2018-06-29 7:53 ` [PATCH 11/37] drm/i915: Combine multiple internal plists into the same i915_priolist bucket Chris Wilson
2018-06-29 7:53 ` [PATCH 12/37] drm/i915: Priority boost for new clients Chris Wilson
2018-06-29 10:04 ` Tvrtko Ursulin
2018-06-29 10:09 ` Chris Wilson
2018-06-29 10:36 ` Tvrtko Ursulin
2018-06-29 10:41 ` Chris Wilson
2018-06-29 10:51 ` Chris Wilson
2018-06-29 11:10 ` Tvrtko Ursulin
2018-07-02 10:19 ` Tvrtko Ursulin
2018-06-29 7:53 ` [PATCH 13/37] drm/i915: Priority boost switching to an idle ring Chris Wilson
2018-06-29 10:08 ` Tvrtko Ursulin
2018-06-29 10:15 ` Chris Wilson
2018-06-29 10:41 ` Tvrtko Ursulin
2018-06-29 7:53 ` [PATCH 14/37] drm/i915: Refactor export_fence() after i915_vma_move_to_active() Chris Wilson
2018-06-29 12:00 ` Tvrtko Ursulin
2018-06-29 7:53 ` [PATCH 15/37] drm/i915: Export i915_request_skip() Chris Wilson
2018-06-29 12:10 ` Tvrtko Ursulin [this message]
2018-06-29 12:15 ` Chris Wilson
2018-06-29 7:53 ` [PATCH 16/37] drm/i915: Start returning an error from i915_vma_move_to_active() Chris Wilson
2018-06-29 12:17 ` Tvrtko Ursulin
2018-06-29 7:53 ` [PATCH 17/37] drm/i915: Track vma activity per fence.context, not per engine Chris Wilson
2018-06-29 14:54 ` Tvrtko Ursulin
2018-06-29 15:03 ` Chris Wilson
2018-06-29 15:34 ` Chris Wilson
2018-06-29 15:08 ` Tvrtko Ursulin
2018-06-29 15:36 ` Chris Wilson
2018-06-29 15:39 ` Chris Wilson
2018-07-02 9:38 ` Tvrtko Ursulin
2018-06-29 22:03 ` [PATCH v2] " Chris Wilson
2018-06-29 7:53 ` [PATCH 18/37] drm/i915: Track the last-active inside the i915_vma Chris Wilson
2018-06-29 22:01 ` [PATCH v2] " Chris Wilson
2018-06-29 7:53 ` [PATCH 19/37] drm/i915: Stop tracking MRU activity on VMA Chris Wilson
2018-06-29 7:53 ` [PATCH 20/37] drm/i915: Introduce the i915_user_extension_method Chris Wilson
2018-06-29 7:53 ` [PATCH 21/37] drm/i915: Extend CREATE_CONTEXT to allow inheritance ala clone() Chris Wilson
2018-06-29 7:53 ` [PATCH 22/37] drm/i915: Allow contexts to share a single timeline across all engines Chris Wilson
2018-06-29 7:53 ` [PATCH 23/37] drm/i915: Fix I915_EXEC_RING_MASK Chris Wilson
2018-06-29 7:53 ` [PATCH 24/37] drm/i915: Re-arrange execbuf so context is known before engine Chris Wilson
2018-06-29 7:53 ` [PATCH 25/37] drm/i915: Allow a context to define its set of engines Chris Wilson
2018-06-29 7:53 ` [PATCH 26/37] drm/i915/execlists: Flush the tasklet before unpinning Chris Wilson
2018-06-29 7:53 ` [PATCH 27/37] drm/i915/execlists: Refactor out can_merge_rq() Chris Wilson
2018-06-29 7:53 ` [PATCH 28/37] drm/i915: Replace nested subclassing with explicit subclasses Chris Wilson
2018-06-29 7:53 ` [PATCH 29/37] RFC drm/i915: Load balancing across a virtual engine Chris Wilson
2018-06-29 7:53 ` [PATCH 30/37] drm/i915: Introduce i915_address_space.mutex Chris Wilson
2018-06-29 7:53 ` [PATCH 31/37] drm/i915: Move fence register tracking to GGTT Chris Wilson
2018-06-29 7:53 ` [PATCH 32/37] drm/i915: Convert fences to use a GGTT lock rather than struct_mutex Chris Wilson
2018-06-29 7:53 ` [PATCH 33/37] drm/i915: Tidy i915_gem_suspend() Chris Wilson
2018-06-29 7:53 ` [PATCH 34/37] drm/i915: Move fence-reg interface to i915_gem_fence_reg.h Chris Wilson
2018-06-29 7:53 ` [PATCH 35/37] drm/i915: Dynamically allocate the array of drm_i915_gem_fence_reg Chris Wilson
2018-06-29 7:53 ` [PATCH 36/37] drm/i915: Pull all the reset functionality together into i915_reset.c Chris Wilson
2018-06-29 7:53 ` [PATCH 37/37] drm/i915: Remove GPU reset dependence on struct_mutex Chris Wilson
2018-06-29 8:58 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/37] drm/i915/gtt: Add read only pages to gen8_pte_encode Patchwork
2018-06-29 9:14 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-06-29 9:16 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-29 11:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-06-29 22:38 ` ✗ Fi.CI.BAT: failure for series starting with [01/37] drm/i915/gtt: Add read only pages to gen8_pte_encode (rev3) Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dd64d3f-9e87-bd76-bc17-2be39815d843@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).