public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Nick Hoath <nicholas.hoath@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
	"Lespiau, Damien" <damien.lespiau@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 03/10] drm/i915: gen 9 h/w w/a (WaDisablePartialInstShootdown)
Date: Fri, 06 Feb 2015 09:36:08 +0000	[thread overview]
Message-ID: <54D48B08.3080603@intel.com> (raw)
In-Reply-To: <20150206085217.GD14009@phenom.ffwll.local>

On 06/02/2015 08:52, Daniel Vetter wrote:
> On Thu, Feb 05, 2015 at 05:51:46PM +0000, Damien Lespiau wrote:
>> On Thu, Feb 05, 2015 at 10:47:18AM +0000, Nick Hoath wrote:
>>> From: "Hoath, Nicholas" <nicholas.hoath@intel.com>
>>>
>>> Add:
>>> WaDisablePartialInstShootdown
>>
>> Just an editor note: that's not really additional information compared
>> to the subject of the patch. Also subject message could be a bit more
>> direct and mention SKL:
>>
>>    drm/i915/skl: Implement WaDisablePartialInstShootdown
>
> Well it's gen9 but yeah. The commit message body should explain the
> commit (e.g. more details on impact), but for w/a that's only really
> required if there's been an outside report.
So an empty body is ok if the subject has sufficient information?
>
>>> v1: Dont add WaDisableThreadStallDopClockGating as not SKL WA. (Found by Damien Lespiau)
>>
>> v2, v1 was the original patch. Commit messages should also be wrapped
Ah, I thought we were software engineers so started counting at 0 :)
>> like emails, so 90 chars is too long.
>>
>> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
>
> Frobbed commit while applying.
> -Daniel
>>
>>> Signed-off-by: Nick Hoath <nicholas.hoath@intel.com>
>>> ---
>>>   drivers/gpu/drm/i915/intel_ringbuffer.c | 7 +++++++
>>>   1 file changed, 7 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
>>> index fbfe65a..b869f1c 100644
>>> --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
>>> +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
>>> @@ -875,6 +875,13 @@ static int chv_init_workarounds(struct intel_engine_cs *ring)
>>>
>>>   static int gen9_init_workarounds(struct intel_engine_cs *ring)
>>>   {
>>> +	struct drm_device *dev = ring->dev;
>>> +	struct drm_i915_private *dev_priv = dev->dev_private;
>>> +
>>> +	/* WaDisablePartialInstShootdown:skl */
>>> +	WA_SET_BIT_MASKED(GEN8_ROW_CHICKEN,
>>> +			  PARTIAL_INSTRUCTION_SHOOTDOWN_DISABLE);
>>> +
>>>   	return 0;
>>>   }
>>>
>>> --
>>> 2.1.1
>>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-02-06  9:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 10:47 [PATCH 00/10] drm/i915: HardWare WorkArounds for gen 9 Nick Hoath
2015-02-05 10:47 ` [PATCH 01/10] drm/i915: ring w/a initialisation " Nick Hoath
2015-02-05 17:39   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 02/10] drm/i915: ring w/a gen 9 revision definitions Nick Hoath
2015-02-05 17:46   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 03/10] drm/i915: gen 9 h/w w/a (WaDisablePartialInstShootdown) Nick Hoath
2015-02-05 17:51   ` Damien Lespiau
2015-02-06  8:52     ` Daniel Vetter
2015-02-06  9:36       ` Nick Hoath [this message]
2015-02-09 18:10         ` Daniel Vetter
2015-02-05 10:47 ` [PATCH 04/10] drm/i915: gen 9 h/w w/a (WaDisableDgMirrorFixInHalfSliceChicken5) Nick Hoath
2015-02-05 17:55   ` Damien Lespiau
2015-02-05 17:57     ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 05/10] drm/i915: gen 9 h/w w/a (syncing dependencies between camera and graphics) Nick Hoath
2015-02-05 18:00   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 06/10] drm/i915: gen 9 h/w w/a (WaDisableSDEUnitClockGating) Nick Hoath
2015-02-05 18:01   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 07/10] drm/i915: gen 9 h/w w/a (WaEnableYV12BugFixInHalfSliceChicken7) Nick Hoath
2015-02-05 18:04   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 08/10] drm/i915: gen 9 h/w w/a (Wa4x4STCOptimizationDisable) Nick Hoath
2015-02-05 18:05   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 09/10] drm/i915: gen 9 h/w w/a (WaForceEnableNonCoherent) Nick Hoath
2015-02-05 18:10   ` Damien Lespiau
2015-02-05 10:47 ` [PATCH 10/10] drm/i915: gen 9 h/w w/a (WaEnableForceRestoreInCtxtDescForVCS) Nick Hoath
2015-02-05 17:27   ` shuang.he
2015-02-05 18:17   ` Damien Lespiau

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=54D48B08.3080603@intel.com \
    --to=nicholas.hoath@intel.com \
    --cc=damien.lespiau@intel.com \
    --cc=daniel@ffwll.ch \
    --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