From: Chris Wilson <chris@chris-wilson.co.uk>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Valtteri Rantala <valtteri.rantala@intel.com>,
Eero Tamminen <eero.t.tamminen@intel.com>,
Michael T Frederick <michael.t.frederick@intel.com>
Subject: Re: [PATCH v2 2/2] drm/i915/bxt: Fix inadvertent CPU snooping due to incorrect MOCS config
Date: Tue, 26 Apr 2016 13:57:26 +0100 [thread overview]
Message-ID: <20160426125726.GJ27856@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1461674662-29353-2-git-send-email-imre.deak@intel.com>
On Tue, Apr 26, 2016 at 03:44:22PM +0300, Imre Deak wrote:
> Setting a write-back cache policy in the MOCS entry definition also
> implies snooping, which has a considerable overhead. This is
> unexpected for a few reasons:
If it is snooping, then I don't see why it is undesirable to have it
available in a mocs setting. If it is bogus and the bit is undefined,
then by all means remove it.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-26 12:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 12:44 [PATCH v2 1/2] drm/i915/gen9: Clean up MOCS table definitions Imre Deak
2016-04-26 12:44 ` [PATCH v2 2/2] drm/i915/bxt: Fix inadvertent CPU snooping due to incorrect MOCS config Imre Deak
2016-04-26 12:57 ` Chris Wilson [this message]
2016-04-26 13:17 ` Imre Deak
2016-04-26 13:23 ` Chris Wilson
2016-04-26 13:43 ` Imre Deak
2016-04-26 13:58 ` Chris Wilson
2016-04-26 14:26 ` Eero Tamminen
2016-04-26 14:30 ` Daniel Vetter
2016-04-26 17:18 ` Eero Tamminen
2016-04-26 17:25 ` Frederick, Michael T
2016-04-27 13:25 ` Eero Tamminen
2016-04-27 14:53 ` Chris Wilson
2016-04-27 18:42 ` Dave Gordon
2016-04-29 8:01 ` Eero Tamminen
2016-04-26 17:57 ` Ville Syrjälä
2016-04-28 8:13 ` Daniel Vetter
2016-04-28 10:48 ` Ville Syrjälä
2016-04-28 14:44 ` Daniel Vetter
2016-04-28 17:21 ` Ville Syrjälä
2016-04-26 14:42 ` Chris Wilson
2016-04-26 16:01 ` Imre Deak
2016-04-28 8:17 ` Daniel Vetter
2016-04-28 8:38 ` Imre Deak
2016-04-28 14:48 ` Daniel Vetter
2016-04-28 17:15 ` Imre Deak
2016-05-02 8:28 ` Daniel Vetter
2016-05-02 11:18 ` Ville Syrjälä
2016-05-02 13:50 ` Imre Deak
2016-04-28 17:25 ` Ville Syrjälä
2016-04-26 13:12 ` Chris Wilson
2016-04-26 16:55 ` ✗ Fi.CI.BAT: failure for series starting with [v2,1/2] drm/i915/gen9: Clean up MOCS table definitions 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=20160426125726.GJ27856@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=eero.t.tamminen@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michael.t.frederick@intel.com \
--cc=valtteri.rantala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.