public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Peter Antoine <peter.antoine@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [for-CI-v2] drm/i915/mocs: Program MOCS for all engines on init
Date: Fri, 15 Apr 2016 10:16:25 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1604151016090.3791@peterant-linux2> (raw)
In-Reply-To: <20160414100603.GG5683@nuc-i3427.alporthouse.com>

Thanks for tidying up and pushing.
Peter.

On Thu, 14 Apr 2016, Chris Wilson wrote:

> On Wed, Apr 13, 2016 at 03:03:25PM +0100, Chris Wilson wrote:
>> From: Peter Antoine <peter.antoine@intel.com>
>>
>> Allow for the MOCS to be programmed for all engines.
>> Currently we program the MOCS when the first render batch
>> goes through. This works on most platforms but fails on
>> platforms that do not run a render batch early,
>> i.e. headless servers. The patch now programs all initialised engines
>> on init and the RCS is programmed again within the initial batch. This
>> is done for predictable consistency with regards to the hardware
>> context.
>>
>> Hardware context loading sets the values of the MOCS for RCS
>> and L3CC. Programming them from within the batch makes sure that
>> the render context is valid, no matter what the previous state of
>> the saved-context was.
>>
>> v2: posted correct version to the mailing list.
>> v3: moved programming to within engine->init_hw() (Chris Wilson)
>> v4: code formatting and white-space changes. (Chris Wilson)
>>
>> Testcase: igt/gem_mocs_settings
>> Signed-off-by: Peter Antoine <peter.antoine@intel.com>
>> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> And pushed, finally. Thanks for the patch and test cases.
> -Chris
>
>

--
    Peter Antoine (Android Graphics Driver Software Engineer)
    ---------------------------------------------------------------------
    Intel Corporation (UK) Limited
    Registered No. 1134945 (England)
    Registered Office: Pipers Way, Swindon SN3 1RJ
    VAT No: 860 2173 47
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-04-15  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13 14:03 [for-CI-v2] drm/i915/mocs: Program MOCS for all engines on init Chris Wilson
2016-04-14  7:54 ` ✗ Fi.CI.BAT: failure for drm/i915/mocs: Program MOCS for all engines on init (rev8) Patchwork
2016-04-14 10:06 ` [for-CI-v2] drm/i915/mocs: Program MOCS for all engines on init Chris Wilson
2016-04-15  9:16   ` Peter Antoine [this message]
2016-04-15 11:26     ` Chris Wilson
2016-04-20 14:50       ` Dave Gordon

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=alpine.DEB.2.10.1604151016090.3791@peterant-linux2 \
    --to=peter.antoine@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