All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Deepak S <deepak.s@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Restrict GPU boost to the RCS engine
Date: Tue, 8 Jul 2014 07:38:45 +0100	[thread overview]
Message-ID: <20140708063845.GB26405@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <53BCC764.2010108@linux.intel.com>

On Wed, Jul 09, 2014 at 10:09:00AM +0530, Deepak S wrote:
> 
> On Monday 07 July 2014 02:35 PM, Daniel Vetter wrote:
> >On Tue, Jun 24, 2014 at 05:22:17PM +0530, Deepak S wrote:
> >>Hi Chris/Daniel,
> >>
> >>The patch is  helping in some of the side-effects due to gpu boost. I
> >>still need to get more data. I will keep the thread updated.
> >Ping. Might as well review it, too.
> >-Daniel
> >
> >>Thanks
> >>Deepak
> >>
> >>On Thursday 12 June 2014 03:02 PM, Daniel Vetter wrote:
> >>>Adding Deepak for testing, this hopefully alleviates the bad
> >>>side-effects of the gpu booster he's seeing.
> >>>-Daniel
> >>>
> >>>On Thu, Jun 12, 2014 at 11:28 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >>>>Make the assumption that media workloads are not as latency sensitive
> >>>>for __wait_seqno, and that upclocking the GPU does not affect the BLT
> >>>>engine. Under that assumption, we only wait to forcibly upclock the GPU
> >>>>when we are stalling for results from the render pipeline.
> >>>>
> >>>>Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> >>>>---
> >>>>  drivers/gpu/drm/i915/i915_gem.c | 2 +-
> >>>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>>
> >>>>diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
> >>>>index 5951618a6b08..242b595a0403 100644
> >>>>--- a/drivers/gpu/drm/i915/i915_gem.c
> >>>>+++ b/drivers/gpu/drm/i915/i915_gem.c
> >>>>@@ -1409,7 +1409,7 @@ static int __wait_seqno(struct intel_engine_cs *ring, u32 seqno,
> >>>>
> >>>>         timeout_expire = timeout ? jiffies + timespec_to_jiffies_timeout(timeout) : 0;
> >>>>
> >>>>-       if (INTEL_INFO(dev)->gen >= 6 && can_wait_boost(file_priv)) {
> >>>>+       if (INTEL_INFO(dev)->gen >= 6 && ring->id == RCS && can_wait_boost(file_priv)) {
> >>>>                 gen6_rps_boost(dev_priv);
> >>>>                 if (file_priv)
> >>>>                         mod_delayed_work(dev_priv->wq,
> >>>>--
> >>>>2.0.0
> >>>>
> >>>>_______________________________________________
> >>>>Intel-gfx mailing list
> >>>>Intel-gfx@lists.freedesktop.org
> >>>>http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> >>>
> Sorry for the delayed response. I am fine with this patch. This is helping us in some of the workload senarios.
> 
> Just one concern here. Since we are avoiding boost for Media related workload, we might end up running GPU at RPn. Which might impact media workload.
> I think we need another patch to run GPU at RPe if the boost is not enabled for media.

That should already be taken care of by the normal upclocking logic.
Except that byt is still using those original ineffectual values for
reclocking....
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2014-07-08  6:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  9:28 [PATCH] drm/i915: Restrict GPU boost to the RCS engine Chris Wilson
2014-06-12  9:32 ` Daniel Vetter
2014-06-21  3:13   ` Deepak S
2014-06-24 11:52   ` Deepak S
2014-07-07  9:05     ` Daniel Vetter
2014-07-09  4:39       ` Deepak S
2014-07-08  6:38         ` Chris Wilson [this message]
2014-07-08  8:25         ` Daniel Vetter
2014-12-17 15:12 ` Chris Wilson
2014-12-17 17:02   ` Daniel Vetter
2014-12-17 17:37     ` Chris Wilson

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=20140708063845.GB26405@nuc-i3427.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=deepak.s@linux.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 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.