From: Andi Shyti <andi.shyti@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Restore GT coarse power gating workaround
Date: Fri, 15 Nov 2019 15:20:26 +0200 [thread overview]
Message-ID: <20191115132026.GB1853@intel.intel> (raw)
In-Reply-To: <20191114152621.7235-1-imre.deak@intel.com>
Hi Imre,
On Thu, Nov 14, 2019 at 05:26:21PM +0200, Imre Deak wrote:
> The workaround to disable coarse power gating is still needed on SKL
> GT3/GT4 machines and since the RC6 context corruption was discovered by
> the hardware team also on all GEN9 machines. Restore applying the
> workaround.
>
> Fixes: c113236718e8 ("drm/i915: Extract GT render sleep (rc6) management")
> Testcase: igt/intel_gt_pm_late_selftests/live_rc6_ctx
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Andi Shyti <andi.shyti@intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
Acked-by: Andi Shyti <andi.shyti@intel.com>
Thanks,
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Restore GT coarse power gating workaround
Date: Fri, 15 Nov 2019 15:20:26 +0200 [thread overview]
Message-ID: <20191115132026.GB1853@intel.intel> (raw)
Message-ID: <20191115132026.0O68EbfKHxXO8x7Gf69bVxhuc4pqoI5XqZpJ8DRyFqI@z> (raw)
In-Reply-To: <20191114152621.7235-1-imre.deak@intel.com>
Hi Imre,
On Thu, Nov 14, 2019 at 05:26:21PM +0200, Imre Deak wrote:
> The workaround to disable coarse power gating is still needed on SKL
> GT3/GT4 machines and since the RC6 context corruption was discovered by
> the hardware team also on all GEN9 machines. Restore applying the
> workaround.
>
> Fixes: c113236718e8 ("drm/i915: Extract GT render sleep (rc6) management")
> Testcase: igt/intel_gt_pm_late_selftests/live_rc6_ctx
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Andi Shyti <andi.shyti@intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
Acked-by: Andi Shyti <andi.shyti@intel.com>
Thanks,
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-15 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 15:26 [PATCH] drm/i915: Restore GT coarse power gating workaround Imre Deak
2019-11-14 15:26 ` [Intel-gfx] " Imre Deak
2019-11-14 15:43 ` Chris Wilson
2019-11-14 15:43 ` [Intel-gfx] " Chris Wilson
2019-11-14 15:55 ` Imre Deak
2019-11-14 15:55 ` [Intel-gfx] " Imre Deak
2019-11-14 16:17 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-11-14 16:17 ` [Intel-gfx] " Patchwork
2019-11-14 17:04 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-14 17:04 ` [Intel-gfx] " Patchwork
2019-11-15 13:20 ` Andi Shyti [this message]
2019-11-15 13:20 ` [Intel-gfx] [PATCH] " Andi Shyti
2019-11-15 15:47 ` ✓ Fi.CI.IGT: success for " Patchwork
2019-11-15 15:47 ` [Intel-gfx] " 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=20191115132026.GB1853@intel.intel \
--to=andi.shyti@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