From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/execlists: Emit i915_trace_request_out for preemption
Date: Tue, 1 May 2018 15:37:57 +0100 [thread overview]
Message-ID: <6c5ad10e-96d5-a52b-1b09-22d809d36187@linux.intel.com> (raw)
In-Reply-To: <20180501134114.29216-1-chris@chris-wilson.co.uk>
On 01/05/2018 14:41, Chris Wilson wrote:
> Move the tracepoint into the common execlists_context_schedule_out() and
> call it from preemption completion as well. A small bit of refactoring
> code should help with when tracing, or else we end up with requests
> mysteriously disappearing and some being emitted to HW multiple times.
>
> Reported-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
> drivers/gpu/drm/i915/intel_lrc.c | 19 +++++++++----------
> 1 file changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
> index 57396a2a6ea2..ffc74f562f77 100644
> --- a/drivers/gpu/drm/i915/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/intel_lrc.c
> @@ -398,10 +398,11 @@ execlists_context_schedule_in(struct i915_request *rq)
> }
>
> static inline void
> -execlists_context_schedule_out(struct i915_request *rq)
> +execlists_context_schedule_out(struct i915_request *rq, unsigned long status)
> {
> intel_engine_context_out(rq->engine);
> - execlists_context_status_change(rq, INTEL_CONTEXT_SCHEDULE_OUT);
> + execlists_context_status_change(rq, status);
> + trace_i915_request_out(rq);
> }
>
> static void
> @@ -772,12 +773,10 @@ execlists_cancel_port_requests(struct intel_engine_execlists * const execlists)
> intel_engine_get_seqno(rq->engine));
>
> GEM_BUG_ON(!execlists->active);
> - intel_engine_context_out(rq->engine);
> -
> - execlists_context_status_change(rq,
> - i915_request_completed(rq) ?
> - INTEL_CONTEXT_SCHEDULE_OUT :
> - INTEL_CONTEXT_SCHEDULE_PREEMPTED);
> + execlists_context_schedule_out(rq,
> + i915_request_completed(rq) ?
> + INTEL_CONTEXT_SCHEDULE_OUT :
> + INTEL_CONTEXT_SCHEDULE_PREEMPTED);
>
> i915_request_put(rq);
>
> @@ -1105,8 +1104,8 @@ static void execlists_submission_tasklet(unsigned long data)
> */
> GEM_BUG_ON(!i915_request_completed(rq));
>
> - execlists_context_schedule_out(rq);
> - trace_i915_request_out(rq);
> + execlists_context_schedule_out(rq,
> + INTEL_CONTEXT_SCHEDULE_OUT);
> i915_request_put(rq);
>
> GEM_TRACE("%s completed ctx=%d\n",
>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
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-05-01 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 13:41 [PATCH 1/2] drm/i915/execlists: Emit i915_trace_request_out for preemption Chris Wilson
2018-05-01 13:41 ` [PATCH 2/2] drm/i915: Include completed status in request tracepoints Chris Wilson
2018-05-01 14:41 ` Tvrtko Ursulin
2018-05-01 14:46 ` Chris Wilson
2018-05-01 14:58 ` [PATCH v2] drm/i915: Include completed status in HW " Chris Wilson
2018-05-01 15:25 ` Tvrtko Ursulin
2018-05-01 14:02 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/execlists: Emit i915_trace_request_out for preemption Patchwork
2018-05-01 14:37 ` Tvrtko Ursulin [this message]
2018-05-01 15:05 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-01 15:06 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/execlists: Emit i915_trace_request_out for preemption (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-05-01 15:13 [PATCH 1/2] drm/i915/execlists: Emit i915_trace_request_out for preemption Chris Wilson
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=6c5ad10e-96d5-a52b-1b09-22d809d36187@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.