public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Eero Tamminen <eero.t.tamminen@intel.com>
Subject: Re: [PATCH v3 0/3] drm/i915/bxt: Fix performance due to bogus MOCS entry
Date: Mon, 18 Jul 2016 17:28:59 +0300	[thread overview]
Message-ID: <20160718142859.GL4329@intel.com> (raw)
In-Reply-To: <1467380406-11954-1-git-send-email-imre.deak@intel.com>

On Fri, Jul 01, 2016 at 04:40:03PM +0300, Imre Deak wrote:
> This is v3 of [1] addressing Ville's and Chris' comments. On Daniel's
> request I also discussed about these changes with Rong R Yang from the
> Beignet and Yakui Zhao from the Libva team, they are CC'd.
> 
> Rong, Yakui please add your Acked-by/Tested-by if you are ok with the
> changes.
> 
> I suggest merging these patches for 4.7, via drm-intel-fixes.
> 
> [1] https://lists.freedesktop.org/archives/intel-gfx/2016-April/094056.html
> 
> 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>
> 
> Imre Deak (3):
>   drm/i915/gen9: Clean up MOCS table definitions
>   drm/i915/bxt: Fix inadvertent CPU snooping due to incorrect MOCS
>     config
>   drm/i915: Give proper names to MOCS entries

Patches lgtm
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> 
>  drivers/gpu/drm/i915/intel_mocs.c | 89 +++++++++++++++++++++++++++------------
>  include/uapi/drm/i915_drm.h       | 24 +++++++++++
>  2 files changed, 86 insertions(+), 27 deletions(-)
> 
> -- 
> 2.5.0

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2016-07-18 14:29 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
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 ` Ville Syrjälä [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=20160718142859.GL4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=eero.t.tamminen@intel.com \
    --cc=imre.deak@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