public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/4] drm/i915: Skip the execlists CSB scan and rewrite if the ring is untouched
Date: Mon, 23 Jan 2017 13:33:32 +0200	[thread overview]
Message-ID: <1485171212.2790.17.camel@linux.intel.com> (raw)
In-Reply-To: <20170121092815.1431-2-chris@chris-wilson.co.uk>

On la, 2017-01-21 at 09:28 +0000, Chris Wilson wrote:
> If the CSB head/tail pointers are unchanged, we can skip the update of
> the CSB register afterwards.
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>

<SNIP>

> @@ -577,7 +577,7 @@ static void intel_lrc_irq_handler(unsigned long data)
>  
>  	intel_uncore_forcewake_get(dev_priv, engine->fw_domains);
>  
> -	if (!execlists_elsp_idle(engine)) {
> +	if (!execlists_elsp_idle(engine)) do {

Oh dear, not like this. I hope this was a leftover from debugging.

> @@ -587,9 +587,12 @@ static void intel_lrc_irq_handler(unsigned long data)
>  		csb = readl(csb_mmio);
>  		head = GEN8_CSB_READ_PTR(csb);
>  		tail = GEN8_CSB_WRITE_PTR(csb);
> +		if (head == tail)
> +			break;
> +
>  		if (tail < head)
>  			tail += GEN8_CSB_ENTRIES;
> -		while (head < tail) {
> +		do {
>  			unsigned int idx = ++head % GEN8_CSB_ENTRIES;
>  			unsigned int status = readl(buf + 2 * idx);

Theoretically it should not matter, I wonder if this is covered well
enough in CI that we're confident to skip such writes?

Code is;

Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-01-23 11:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-21  9:28 [PATCH 1/4] drm/i915: Only disable execlist preemption for the duration of the request Chris Wilson
2017-01-21  9:28 ` [PATCH 2/4] drm/i915: Skip the execlists CSB scan and rewrite if the ring is untouched Chris Wilson
2017-01-23 11:33   ` Joonas Lahtinen [this message]
2017-01-23 11:47     ` Chris Wilson
2017-01-21  9:28 ` [PATCH 3/4] drm/i915: Dequeue execlists on a new request if any port is available Chris Wilson
2017-01-23 10:56   ` Tvrtko Ursulin
2017-01-23 11:21     ` Chris Wilson
2017-01-21  9:28 ` [PATCH 4/4] drm/i915: Emit dma-fence (and execlists submit) first from signaler Chris Wilson
2017-01-23 10:58   ` Tvrtko Ursulin
2017-01-23 11:37   ` Joonas Lahtinen
2017-01-21 10:54 ` ✗ Fi.CI.BAT: warning for series starting with [1/4] drm/i915: Only disable execlist preemption for the duration of the request Patchwork
2017-01-21 11:02   ` 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=1485171212.2790.17.camel@linux.intel.com \
    --to=joonas.lahtinen@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