From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Oscar Mateo <oscar.mateo@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC PATCH v6 0/6] Refactor HW workaround code
Date: Thu, 9 Nov 2017 15:43:35 +0200 [thread overview]
Message-ID: <20171109134335.GM10981@intel.com> (raw)
In-Reply-To: <1510185589-9100-1-git-send-email-oscar.mateo@intel.com>
On Wed, Nov 08, 2017 at 03:59:43PM -0800, Oscar Mateo wrote:
> Until we agree on a design, I have removed all new code to save the actual list
> of WAs and dump it in debugfs. For the moment, only shuffle things arounds until
> most WAs are in the same file (and classified correctly according to the type
> of WA).
>
> From previous versions of these series:
>
> Currently, deciding how/where to apply new workarounds is challenging. Often,
> workarounds end up applied incorrectly and get lost under certain circumstances
> (e.g. a context switch or a GPU reset). This is a proposal to attempt to
> eliminate some of this pain, by clarifying the current classification of
> workarounds (context saved/restored, global registers, whitelisting, BB),
> putting them together on the same file, and improving the existing validation
> infrastructure (debugfs/i-g-t).
>
> Oscar Mateo (6):
> drm/i915: Remove Gen9 WAs with no effect
> drm/i915: Move a bunch of workaround-related code to its own file
> drm/i915: Split out functions for different kinds of workarounds
> drm/i915: Move WA BB stuff to the workarounds file as well
> drm/i915: Create a new category of display WAs
> drm/i915: Classify GT & Display WAs correctly
>
> drivers/gpu/drm/i915/Makefile | 3 +-
> drivers/gpu/drm/i915/i915_gem.c | 3 +
> drivers/gpu/drm/i915/i915_gem_context.c | 5 +
> drivers/gpu/drm/i915/i915_reg.h | 3 -
> drivers/gpu/drm/i915/intel_engine_cs.c | 682 --------------
> drivers/gpu/drm/i915/intel_lrc.c | 264 +-----
> drivers/gpu/drm/i915/intel_pm.c | 312 +------
> drivers/gpu/drm/i915/intel_ringbuffer.c | 5 +-
> drivers/gpu/drm/i915/intel_ringbuffer.h | 3 -
> drivers/gpu/drm/i915/intel_workarounds.c | 1432 ++++++++++++++++++++++++++++++
> drivers/gpu/drm/i915/intel_workarounds.h | 40 +
Maybe we should call that intel_gt_workarounds.c? Or
i915_something_workarounds.c? We could then add a separate
intel_display_workarounds.c for the display stuff.
> 11 files changed, 1503 insertions(+), 1249 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/intel_workarounds.c
> create mode 100644 drivers/gpu/drm/i915/intel_workarounds.h
>
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-11-09 13:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 23:59 [RFC PATCH v6 0/6] Refactor HW workaround code Oscar Mateo
2017-11-08 23:59 ` [RFC PATCH 1/6] drm/i915: Remove Gen9 WAs with no effect Oscar Mateo
2017-11-09 11:42 ` Mika Kuoppala
2017-11-09 11:48 ` Chris Wilson
2017-11-12 14:35 ` Chris Wilson
2017-11-08 23:59 ` [RFC PATCH 2/6] drm/i915: Move a bunch of workaround-related code to its own file Oscar Mateo
2017-11-08 23:59 ` [RFC PATCH 3/6] drm/i915: Split out functions for different kinds of workarounds Oscar Mateo
2017-11-08 23:59 ` [RFC PATCH 4/6] drm/i915: Move WA BB stuff to the workarounds file as well Oscar Mateo
2017-11-08 23:59 ` [RFC PATCH 5/6] drm/i915: Create a new category of display WAs Oscar Mateo
2017-11-08 23:59 ` [RFC PATCH 6/6] drm/i915: Classify GT & Display WAs correctly Oscar Mateo
2017-11-09 0:19 ` ✓ Fi.CI.BAT: success for Refactor HW workaround code (rev7) Patchwork
2017-11-09 1:11 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-09 13:43 ` Ville Syrjälä [this message]
2017-11-11 0:25 ` [RFC PATCH v6 0/6] Refactor HW workaround code Oscar Mateo
2018-02-01 9:32 ` 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=20171109134335.GM10981@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox