All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Prepare for larger CSB status FIFO size
Date: Tue, 27 Nov 2018 17:46:43 +0000	[thread overview]
Message-ID: <154334080300.11623.1481147864619869213@skylake-alporthouse-com> (raw)
In-Reply-To: <20181127173845.17403-1-mika.kuoppala@linux.intel.com>

Quoting Mika Kuoppala (2018-11-27 17:38:43)
>  static void reset_csb_pointers(struct intel_engine_execlists *execlists)
>  {
> +       u32 reset_val;
>         /*
>          * After a reset, the HW starts writing into CSB entry [0]. We
>          * therefore have to set our HEAD pointer back one entry so that
> @@ -776,8 +777,19 @@ static void reset_csb_pointers(struct intel_engine_execlists *execlists)
>          * inline comparison of our cached head position against the last HW
>          * write works even before the first interrupt.
>          */
> -       execlists->csb_head = execlists->csb_write_reset;
> -       WRITE_ONCE(*execlists->csb_write, execlists->csb_write_reset);
> +       execlists->csb_head = execlists->csb_entries - 1;
> +
> +       if (execlists_mmio_mode(execlists)) {
> +               const u32 mask = execlists->csb_entries == GEN8_CSB_ENTRIES ?
> +                       GEN8_CSB_WRITE_PTR_MASK :
> +                       GEN11_CSB_WRITE_PTR_MASK;
> +
> +               reset_val = _MASKED_FIELD(mask, execlists->csb_head);
> +       } else {
> +               reset_val = execlists->csb_head;
> +       }

Think: did I need to change this?
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-11-27 17:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 17:38 [PATCH 1/3] drm/i915: Prepare for larger CSB status FIFO size Mika Kuoppala
2018-11-27 17:38 ` [PATCH 2/3] drm/i915/icl: Switch to using 12 deep CSB status FIFO Mika Kuoppala
2018-11-27 17:38 ` [PATCH 3/3] drm/i915: Assert the csb tail is within bounds Mika Kuoppala
2018-11-27 17:48   ` Chris Wilson
2018-11-27 17:46 ` Chris Wilson [this message]
2018-11-27 18:43 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Prepare for larger CSB status FIFO size Patchwork
2018-11-27 19:00 ` [PATCH 1/3] " Daniele Ceraolo Spurio
2018-11-28  1:16 ` ✓ Fi.CI.IGT: success for series starting with [1/3] " Patchwork
2018-12-18 13:24 [PATCH 1/3] " Mika Kuoppala
2018-12-18 13:47 ` Chris Wilson
2018-12-19 12:27   ` Mika Kuoppala
2018-12-19 12:40     ` Chris Wilson
2018-12-19 13:17       ` Mika Kuoppala
2018-12-19 13:22         ` Mika Kuoppala
2018-12-19 13:26       ` Mika Kuoppala

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=154334080300.11623.1481147864619869213@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@linux.intel.com \
    /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.