Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Add GuC support for engine busy stats
Date: Fri, 22 Dec 2017 09:53:46 +0000	[thread overview]
Message-ID: <87a76958-0d85-e6f7-9ae9-f259ed6860ac@linux.intel.com> (raw)
In-Reply-To: <20171129123355.15509-1-tvrtko.ursulin@linux.intel.com>


Hi guys,

Anyone has the bandwidth to review the below tiny patch, or suggest some 
else as potential reviewer?

Truth be told I only tested it lightly, but it passed the perf_pmu unit 
tests. Goal is to bring engine busyness PMU reporting accuracy to the 
same level as execlists.

Regards,

Tvrtko

On 29/11/2017 12:33, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> 
> Wire up the engine busy stats accounting to the GuC submission backend.
> 
> Since there is not context out interrupt we need to place the accounting
> callbacks per-request in order to correctly pair with user interrupts.
> 
> v2: Rebase.
> v3: Commit update.
> 
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> ---
>   drivers/gpu/drm/i915/intel_guc_submission.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_guc_submission.c b/drivers/gpu/drm/i915/intel_guc_submission.c
> index 912ff143d531..d80d2a3214da 100644
> --- a/drivers/gpu/drm/i915/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/intel_guc_submission.c
> @@ -781,6 +781,7 @@ static void guc_dequeue(struct intel_engine_cs *engine)
>   			INIT_LIST_HEAD(&rq->priotree.link);
>   
>   			__i915_gem_request_submit(rq);
> +			intel_engine_context_in(rq->engine);
>   			trace_i915_gem_request_in(rq,
>   						  port_index(port, execlists));
>   			last = rq;
> @@ -813,6 +814,7 @@ static void guc_submission_tasklet(unsigned long data)
>   
>   	rq = port_request(&port[0]);
>   	while (rq && i915_gem_request_completed(rq)) {
> +		intel_engine_context_out(rq->engine);
>   		trace_i915_gem_request_out(rq);
>   		i915_gem_request_put(rq);
>   
> @@ -1453,8 +1455,6 @@ int intel_guc_submission_enable(struct intel_guc *guc)
>   		execlists->tasklet.func = guc_submission_tasklet;
>   		engine->park = guc_submission_park;
>   		engine->unpark = guc_submission_unpark;
> -
> -		engine->flags &= ~I915_ENGINE_SUPPORTS_STATS;
>   	}
>   
>   	return 0;
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-12-22  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 12:33 [PATCH 1/2] drm/i915: Add GuC support for engine busy stats Tvrtko Ursulin
2017-11-29 12:33 ` [PATCH 2/2] drm/i915: HACK enable GuC for testing Tvrtko Ursulin
2017-11-29 13:30 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Add GuC support for engine busy stats Patchwork
2017-11-29 14:10   ` Tvrtko Ursulin
2017-11-30 16:35 ` Patchwork
2017-12-22  9:53 ` Tvrtko Ursulin [this message]
2017-12-22 10:50 ` [PATCH 1/2] " Sagar Arun Kamble
2017-12-22 11:37   ` Tvrtko Ursulin

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=87a76958-0d85-e6f7-9ae9-f259ed6860ac@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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