From: Imre Deak <imre.deak@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Eero Tamminen <eero.t.tamminen@intel.com>
Subject: Re: [PATCH v3 3/3] drm/i915: Give proper names to MOCS entries
Date: Fri, 01 Jul 2016 16:56:39 +0300 [thread overview]
Message-ID: <1467381399.27367.35.camel@intel.com> (raw)
In-Reply-To: <20160701134941.GH1306@nuc-i3427.alporthouse.com>
On pe, 2016-07-01 at 14:49 +0100, Chris Wilson wrote:
> On Fri, Jul 01, 2016 at 04:40:06PM +0300, Imre Deak wrote:
> > The purpose for each MOCS entry isn't well defined atm. Defining these
> > is important to remove any uncertainty about the use of these entries
> > for example in terms of performance and GPU/CPU coherency.
> >
> > Suggested by Ville.
> >
> > CC: Rong R Yang <rong.r.yang@intel.com>
> > CC: Yakui Zhao <yakui.zhao@intel.com>
> > CC: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > CC: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_mocs.c | 13 +++++++------
> > include/uapi/drm/i915_drm.h | 24 ++++++++++++++++++++++++
> > 2 files changed, 31 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_mocs.c b/drivers/gpu/drm/i915/intel_mocs.c
> > index 927825f..86adc11 100644
> > --- a/drivers/gpu/drm/i915/intel_mocs.c
> > +++ b/drivers/gpu/drm/i915/intel_mocs.c
> > @@ -97,7 +97,8 @@ struct drm_i915_mocs_table {
> > * end.
> > */
> > static const struct drm_i915_mocs_entry skylake_mocs_table[] = {
> > - { /* 0x00000009 */
> > + [I915_MOCS_UNCACHED] = {
> > + /* 0x00000009 */
> > .control_value = LE_CACHEABILITY(LE_UC) |
> > LE_TGT_CACHE(LE_TC_LLC_ELLC) |
> > LE_LRUM(0) | LE_AOM(0) | LE_RSC(0) | LE_SCC(0) |
> > @@ -106,7 +107,7 @@ static const struct drm_i915_mocs_entry skylake_mocs_table[] = {
> > /* 0x0010 */
> > .l3cc_value = L3_ESC(0) | L3_SCC(0) | L3_CACHEABILITY(L3_UC),
> > },
> > - {
> > + [I915_MOCS_AUTO] = {
> > /* 0x00000038 */
> > .control_value = LE_CACHEABILITY(LE_PAGETABLE) |
> > LE_TGT_CACHE(LE_TC_LLC_ELLC) |
> > @@ -115,7 +116,7 @@ static const struct drm_i915_mocs_entry skylake_mocs_table[] = {
> > /* 0x0030 */
> > .l3cc_value = L3_ESC(0) | L3_SCC(0) | L3_CACHEABILITY(L3_WB),
> > },
> > - {
> > + [I915_MOCS_CACHED] = {
> > /* 0x0000003b */
> > .control_value = LE_CACHEABILITY(LE_WB) |
> > LE_TGT_CACHE(LE_TC_LLC_ELLC) |
> > @@ -128,7 +129,7 @@ static const struct drm_i915_mocs_entry skylake_mocs_table[] = {
> >
> > /* NOTE: the LE_TGT_CACHE is not used on Broxton */
> > static const struct drm_i915_mocs_entry broxton_mocs_table[] = {
> > - {
> > + [I915_MOCS_UNCACHED] = {
> > /* 0x00000009 */
> > .control_value = LE_CACHEABILITY(LE_UC) |
> > LE_TGT_CACHE(LE_TC_LLC_ELLC) |
> > @@ -138,7 +139,7 @@ static const struct drm_i915_mocs_entry broxton_mocs_table[] = {
> > /* 0x0010 */
> > .l3cc_value = L3_ESC(0) | L3_SCC(0) | L3_CACHEABILITY(L3_UC),
> > },
> > - {
> > + [I915_MOCS_AUTO] = {
> > /* 0x00000038 */
> > .control_value = LE_CACHEABILITY(LE_PAGETABLE) |
> > LE_TGT_CACHE(LE_TC_LLC_ELLC) |
> > @@ -148,7 +149,7 @@ static const struct drm_i915_mocs_entry broxton_mocs_table[] = {
> > /* 0x0030 */
> > .l3cc_value = L3_ESC(0) | L3_SCC(0) | L3_CACHEABILITY(L3_WB),
> > },
> > - {
> > + [I915_MOCS_CACHED] = {
> > /* 0x00000039 */
> > .control_value = LE_CACHEABILITY(LE_UC) |
> > LE_TGT_CACHE(LE_TC_LLC_ELLC) |
> > diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h
> > index c17d63d..a5d116f 100644
> > --- a/include/uapi/drm/i915_drm.h
> > +++ b/include/uapi/drm/i915_drm.h
> > @@ -62,6 +62,30 @@ extern "C" {
> > #define I915_ERROR_UEVENT "ERROR"
> > #define I915_RESET_UEVENT "RESET"
> >
> > +/*
> > + * MOCS indexes used for GPU surfaces, defining the cacheability of the
> > + * surface data and the coherency for this data wrt. CPU vs. GPU accesses.
> > + */
> > +enum i915_mocs_table_index {
> > + /*
> > + * Not cached anywhere, coherency between CPU and GPU accesses is
> > + * guaranteed.
> > + */
> > + I915_MOCS_UNCACHED,
> > + /*
> > + * Cacheability and coherency controlled by the kernel automatically
> > + * based on the DRM_I915_GEM_SET_CACHING IOCTL setting and the current
> > + * usage of the surface (used for display scanout or not).
> > + */
> > + I915_MOCS_AUTO,
>
> So PTE.
Can change it.
> > + /*
> > + * Cached in all GPU caches available on the platform.
> > + * Coherency between CPU and GPU accesses to the surface is not
> > + * guaranteed without extra synchronization.
> > + */
> > + I915_MOCS_CACHED,
>
> So pretty useless for its current usage then.
This is how it's used in Mesa atm where there is no need for coherency.
Beignet and Libva don't use this entry atm.
--Imre
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-01 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 13:40 [PATCH v3 0/3] drm/i915/bxt: Fix performance due to bogus MOCS entry Imre Deak
2016-07-01 13:40 ` [PATCH v3 1/3] drm/i915/gen9: Clean up MOCS table definitions Imre Deak
2016-07-01 21:23 ` Bish, Jim
2016-07-01 21:47 ` Francisco Jerez
2016-07-12 11:08 ` Imre Deak
2016-07-13 2:10 ` Zhao Yakui
2016-07-01 13:40 ` [PATCH v3 2/3] drm/i915/bxt: Fix inadvertent CPU snooping due to incorrect MOCS config Imre Deak
2016-07-13 2:32 ` Zhao Yakui
2016-07-14 8:33 ` Yang, Rong R
2016-07-01 13:40 ` [PATCH v3 3/3] drm/i915: Give proper names to MOCS entries Imre Deak
2016-07-01 13:49 ` Chris Wilson
2016-07-01 13:56 ` Imre Deak [this message]
2016-07-01 14:32 ` [PATCH v4 " Imre Deak
2016-07-13 2:22 ` [PATCH v3 " Zhao Yakui
2016-07-13 10:04 ` Imre Deak
2016-07-14 1:38 ` Zhao Yakui
2016-07-01 14:54 ` ✗ Ro.CI.BAT: warning for drm/i915/bxt: Fix performance due to bogus MOCS entry Patchwork
2016-07-19 18:15 ` Imre Deak
2016-07-01 15:15 ` ✗ Ro.CI.BAT: warning for drm/i915/bxt: Fix performance due to bogus MOCS entry (rev2) Patchwork
2016-07-18 14:28 ` [PATCH v3 0/3] drm/i915/bxt: Fix performance due to bogus MOCS entry Ville Syrjälä
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=1467381399.27367.35.camel@intel.com \
--to=imre.deak@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=eero.t.tamminen@intel.com \
--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