public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org, "Antoine,
	Peter" <peter.antoine@intel.com>
Subject: Re: [for-CI-v2] drm/i915/mocs: Program MOCS for all engines on init
Date: Wed, 20 Apr 2016 15:50:07 +0100	[thread overview]
Message-ID: <5717971F.5080703@intel.com> (raw)
In-Reply-To: <20160415112647.GM19990@nuc-i3427.alporthouse.com>

On 15/04/16 12:26, Chris Wilson wrote:
> On Fri, Apr 15, 2016 at 10:16:25AM +0100, Peter Antoine wrote:
>> Thanks for tidying up and pushing.
>
> Fwiw, I extended the test to demonstrate that !rcs engines are also
> suspectible to the same pollution where one process can affect the
> register settings of an another.
> -Chris

Try INSTPM, bits 6 and 7 . The hardware saves & restores it properly 
(AFAICT) but the driver muddles up settings from different contexts :(

.Dave.

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

      reply	other threads:[~2016-04-20 14:50 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
2016-04-15 11:26     ` Chris Wilson
2016-04-20 14:50       ` Dave Gordon [this message]

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=5717971F.5080703@intel.com \
    --to=david.s.gordon@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=peter.antoine@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