All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Oscar Mateo Lozano <oscar.mateo@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Keep the ctx workarounds tightly packed
Date: Fri, 15 Jun 2018 19:19:14 +0300	[thread overview]
Message-ID: <20180615161914.GQ20518@intel.com> (raw)
In-Reply-To: <d564506f-bdea-532b-398a-fb16577dba48@intel.com>

On Fri, Jun 15, 2018 at 09:01:37AM -0700, Oscar Mateo Lozano wrote:
> 
> 
> On 6/15/2018 1:59 AM, Chris Wilson wrote:
> > For each platform, we have a few registers that rewritten with multiple
> > values -- they are not part of a sequence, just different parts of a
> > masked register set at different times (e.g. platform and gen
> > workarounds). Consolidate these into a single register write to keep the
> > table compact.
> >
> > While adjusting the construction of the wa table, make it non fatal so
> > that the driver still loads but keeping the warning and extra details
> > for inspection.
> 
> A while ago I sent a patch 
> (https://patchwork.freedesktop.org/patch/205035/) that uses simple MMIO 
> writes to apply ctx workarounds. This is possible since we now have 
> proper golden contexts, and avoids the need for these patches.
> It also has the advantage that an improperly classified WA doesn't get 
> lost (we still need the classification if we want to properly validate 
> the WAs, but that's a different story).
> Are we sure we prefer to do this instead?

Wouldn't that require PSMI+FSM dance to make sure execlist has
an active context when you write the regs? Can't see anything like that
in the code currently, nor is there anything in the referenced patch.

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2018-06-15 16:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  8:59 [PATCH 1/3] drm/i915: Keep the ctx workarounds tightly packed Chris Wilson
2018-06-15  8:59 ` [PATCH 2/3] drm/i915: Break workaround register emission into batches of 15 Chris Wilson
2018-06-15  8:59 ` [PATCH 3/3] drm/i915: Enable provoking vertex fix on Gen9+ systems Chris Wilson
2018-06-15  9:23 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915: Keep the ctx workarounds tightly packed Patchwork
2018-06-15  9:24 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-06-15  9:39 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-06-15 11:36 ` [PATCH 1/3] " Mika Kuoppala
2018-06-15 16:01 ` Oscar Mateo Lozano
2018-06-15 16:08   ` Chris Wilson
2018-06-15 16:19   ` Ville Syrjälä [this message]
2018-06-15 16:22     ` Chris Wilson
2018-06-15 16:37       ` Ville Syrjälä
2018-06-15 16:43         ` 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=20180615161914.GQ20518@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=oscar.mateo@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.