Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rogozhkin, Dmitry V" <dmitry.v.rogozhkin@intel.com>
To: "Deak, Imre" <imre.deak@intel.com>
Cc: "Intel-gfx@lists.freedesktop.org" <Intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH v5] drm/i915: Restore GT performance in headless mode with DMC loaded
Date: Tue, 5 Dec 2017 19:01:25 +0000	[thread overview]
Message-ID: <1512471518.30829.1.camel@intel.com> (raw)
In-Reply-To: <20171205130940.7dbsml2nkm43o7vs@ideak-desk.fi.intel.com>

On Tue, 2017-12-05 at 15:09 +0200, Imre Deak wrote:
> On Sat, Dec 02, 2017 at 02:05:42AM +0200, Rogozhkin, Dmitry V wrote:
> > On Thu, 2017-11-30 at 13:19 +0200, Imre Deak wrote:
> > > > > +#define NEEDS_CSR_GT_PERF_WA(dev_priv) \
> > > > > +       (HAS_CSR(dev_priv) && IS_GEN9(dev_priv) && !
> > > IS_SKYLAKE(dev_priv))
> > > 
> > > Nitpick: could be just !IS_SKYLAKE(), but works in the above way too.
> > > For all other platforms the GT_IRQ domain won't be mapped making
> > > display_power_get/put on those just a domain ref inc/dec, otherwise a
> > > nop.
> > 
> > Why not +&& !IS_BROXTON(dev_priv) by the way?
> 
> We have the same slow-down problem on APL/BXT (and we don't have the DC6
> corruption problem there).

Ok, this makes sense now. Thank you for clarification.

> 
> --Imre

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

  reply	other threads:[~2017-12-05 19:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 10:59 [PATCH] drm/i915: Restore GT performance in headless mode with DMC loaded Tvrtko Ursulin
2017-11-29 11:10 ` Chris Wilson
2017-11-29 12:29   ` Imre Deak
2017-11-29 11:12 ` Daniel Vetter
2017-11-29 11:34   ` Tvrtko Ursulin
2017-11-29 11:40     ` Chris Wilson
2017-11-29 11:53       ` Tvrtko Ursulin
2017-11-29 11:59         ` Chris Wilson
2017-11-29 14:15           ` Imre Deak
2017-11-29 12:47     ` Daniel Vetter
2017-11-29 11:22 ` ✗ Fi.CI.BAT: warning for drm/i915: Restore GT performance in headless mode with DMC loaded (rev3) Patchwork
2017-11-29 14:18 ` [PATCH] drm/i915: Restore GT performance in headless mode with DMC loaded Imre Deak
2017-11-29 14:30 ` [PATCH v4] " Tvrtko Ursulin
2017-11-29 15:06   ` Imre Deak
2017-11-29 15:21     ` Tvrtko Ursulin
2017-11-29 17:28       ` Imre Deak
2017-11-30  8:34         ` Tvrtko Ursulin
2017-11-30  9:18   ` [PATCH v5] " Tvrtko Ursulin
2017-11-30  9:45     ` Chris Wilson
2017-11-30  9:55       ` Tvrtko Ursulin
2017-11-30 11:19       ` Imre Deak
2017-12-01 23:58         ` Rogozhkin, Dmitry V
2017-12-05 13:08           ` Imre Deak
2017-12-05 13:28             ` [PATCH v6] " Tvrtko Ursulin
2017-12-05 13:35               ` Chris Wilson
2017-12-08 10:46                 ` Imre Deak
2017-12-02  0:05         ` [PATCH v5] " Rogozhkin, Dmitry V
2017-12-05 13:09           ` Imre Deak
2017-12-05 19:01             ` Rogozhkin, Dmitry V [this message]
2017-11-30 15:56 ` ✗ Fi.CI.BAT: warning for drm/i915: Restore GT performance in headless mode with DMC loaded (rev5) Patchwork
2017-12-05 15:06 ` ✗ Fi.CI.BAT: failure for drm/i915: Restore GT performance in headless mode with DMC loaded (rev6) Patchwork
2017-12-05 17:42 ` ✗ Fi.CI.BAT: warning " 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=1512471518.30829.1.camel@intel.com \
    --to=dmitry.v.rogozhkin@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=imre.deak@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