From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Add a policy note for removing workarounds
Date: Fri, 17 Nov 2017 13:11:28 +0200 [thread overview]
Message-ID: <87fu9d5fdr.fsf@intel.com> (raw)
In-Reply-To: <20171117102635.8689-1-chris@chris-wilson.co.uk>
On Fri, 17 Nov 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Rodrigo gave a persuasive argument for keeping workarounds: that they
> serve as a good guide for the bring up of the next generation. Not only
> do workarounds persist into the early revisions, they show where the
> workarounds were previously added to the code flow and sometimes the old
> workarounds have an explanation that give insight into their wider
> implications.
>
> Based on his suggestion, document the policy that we want to keep the
> workarounds from the current generation to guide the next. Older
> preproduction workarounds we still want to remove to keep the code
> clean.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Acked-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index 57dfaf04d819..fbfa9434c1d1 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -833,6 +833,11 @@ static void i915_workqueues_cleanup(struct drm_i915_private *dev_priv)
> * We don't keep the workarounds for pre-production hardware, so we expect our
> * driver to fail on these machines in one way or another. A little warning on
> * dmesg may help both the user and the bug triagers.
> + *
> + * Our policy for removing pre-production workarounds is to keep the
> + * current gen workarounds as a guide to the bring-up of the next gen
> + * (workarounds have a habit of persisting!). Anything older than that
> + * should be removed along with the complications they introduce.
> */
> static void intel_detect_preproduction_hw(struct drm_i915_private *dev_priv)
> {
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
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-17 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 10:26 [PATCH] drm/i915: Add a policy note for removing workarounds Chris Wilson
2017-11-17 10:53 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-17 11:11 ` Jani Nikula [this message]
2017-11-17 17:33 ` [PATCH] " Rodrigo Vivi
2017-11-17 17:51 ` Chris Wilson
2017-11-17 12:36 ` ✓ Fi.CI.IGT: success for " Patchwork
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=87fu9d5fdr.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@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