public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Arun Siluvery <arun.siluvery@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Update WaFlushCoherentL3CacheLinesAtContextSwitch
Date: Mon, 06 Jul 2015 12:52:51 +0100	[thread overview]
Message-ID: <559A6C13.8060900@intel.com> (raw)
In-Reply-To: <20150703154225.GP14231@nuc-i3427.alporthouse.com>

On 03/07/15 16:42, Chris Wilson wrote:
> On Fri, Jul 03, 2015 at 02:27:31PM +0100, Arun Siluvery wrote:
>> In this WA we need to set GEN8_L3SQCREG4[21:21] and reset it after PIPE_CONTROL
>> instruction but there is a slight complication as this is applied in WA batch
>> where the values are only initialized once.
>> Dave identified an issue with the current implementation where the register value
>> is read once at the beginning and it is reused; this patch corrects this by saving
>> the register value to memory, update register with the bit of our interest and
>> restore it back with original value.
>>
>> This implementation uses MI_LOAD_REGISTER_MEM which is currently only used
>> by command parser and was using a default length of 0. This is now updated
>> with correct length and moved to appropriate place.
>>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Dave Gordon <david.s.gordon@intel.com>
>> Signed-off-by: Arun Siluvery <arun.siluvery@linux.intel.com>
>> ---
>>   drivers/gpu/drm/i915/i915_cmd_parser.c |  6 +--
>>   drivers/gpu/drm/i915/i915_reg.h        |  3 +-
>>   drivers/gpu/drm/i915/intel_lrc.c       | 72 +++++++++++++++++++++++++---------
>>   3 files changed, 58 insertions(+), 23 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_cmd_parser.c b/drivers/gpu/drm/i915/i915_cmd_parser.c
>> index 306d9e4..430571b 100644
>> --- a/drivers/gpu/drm/i915/i915_cmd_parser.c
>> +++ b/drivers/gpu/drm/i915/i915_cmd_parser.c
>> @@ -131,7 +131,7 @@ static const struct drm_i915_cmd_descriptor common_cmds[] = {
>>   			.mask = MI_GLOBAL_GTT,
>>   			.expected = 0,
>>   	      }},						       ),
>> -	CMD(  MI_LOAD_REGISTER_MEM,             SMI,   !F,  0xFF,   W | B,
>> +	CMD(  MI_LOAD_REGISTER_MEM(1),             SMI,   !F,  0xFF,   W | B,
>>   	      .reg = { .offset = 1, .mask = 0x007FFFFC },
>>   	      .bits = {{
>>   			.offset = 0,
>> @@ -1021,7 +1021,7 @@ static bool check_cmd(const struct intel_engine_cs *ring,
>>   			 * only MI_LOAD_REGISTER_IMM commands.
>>   			 */
>>   			if (reg_addr == OACONTROL) {
>> -				if (desc->cmd.value == MI_LOAD_REGISTER_MEM) {
>> +				if (desc->cmd.value == MI_LOAD_REGISTER_MEM(1)) {
>
> I had a double take here, but it all comes out in the wash. For one
> moment, I thought the cmd matching had changed, but that has the length
> masked out.
>
> Reviewed-by: Chris Wilson <chris@cris-wilson.co.uk>
>
> Who will start to complain about all the extra frequent register writes,
> probably into common power wells....
> -Chris

Hmm ... that is quite confusing, especially as the actual opcode in the 
instruction stream will be MI_LOAD_REGISTER_MEM(2) on GEN8+. It might 
almost be better to use MI_LOAD_REGISTER_MEM(0) to emphasise that the 
length field is a wildcard and not something that will be matched exactly.

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

  reply	other threads:[~2015-07-06 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 13:27 [PATCH] drm/i915: Update WaFlushCoherentL3CacheLinesAtContextSwitch Arun Siluvery
2015-07-03 15:42 ` Chris Wilson
2015-07-06 11:52   ` Dave Gordon [this message]
2015-07-06 12:24     ` Siluvery, Arun
2015-07-06 12:38     ` Daniel Vetter
2015-07-06 13:16       ` Dave Gordon
2015-07-06 14:33         ` Daniel Vetter
2015-07-06 15:25           ` Dave Gordon
2015-07-06 15:41           ` Chris Wilson
2015-07-10 15:24             ` Dave Gordon
2015-07-05  1:34 ` shuang.he

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=559A6C13.8060900@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=arun.siluvery@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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