From: "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"cpaul@redhat.com" <cpaul@redhat.com>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 3/8] drm/i915/kbl: KBL also needs to run the SAGV code
Date: Wed, 14 Sep 2016 13:32:45 +0000 [thread overview]
Message-ID: <1473859963.2435.103.camel@intel.com> (raw)
In-Reply-To: <87sht2redy.fsf@intel.com>
Em Qua, 2016-09-14 às 12:59 +0300, Jani Nikula escreveu:
> On Tue, 13 Sep 2016, "Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
> wrote:
> >
> > I got confirmation from the Hardware guys that KBL does need to run
> > the
> > SAGV code, and it has the same latency as SKL. Also, all SKL
> > production
> > steppings need to run the SAGV code.
>
> Can you get confirmation what's the first shipped production
> stepping?
https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-skl
-vol04-configurations.pdf#page=15
But I have to admit that I still have pre-prod machines and it would be
very convenient to me if they keep working :)
>
> BR,
> Jani.
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-09-14 13:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 0:52 [PATCH 0/8] SKL/KBL watermark fixes Paulo Zanoni
2016-09-07 0:52 ` [PATCH 1/8] drm/i915: SAGV is not SKL-only, so rename a few things Paulo Zanoni
2016-09-07 16:05 ` Lyude
2016-09-09 20:16 ` Zanoni, Paulo R
2016-09-07 0:52 ` [PATCH 2/8] drm/i915: introduce intel_has_sagv() Paulo Zanoni
2016-09-07 16:12 ` Lyude
2016-09-08 8:59 ` Jani Nikula
2016-09-08 14:43 ` Lyude Paul
2016-09-09 8:06 ` Jani Nikula
2016-09-09 19:51 ` Zanoni, Paulo R
2016-09-10 10:49 ` Ville Syrjälä
2016-09-12 9:48 ` Jani Nikula
2016-09-07 0:52 ` [PATCH 3/8] drm/i915/kbl: KBL also needs to run the SAGV code Paulo Zanoni
2016-09-07 16:11 ` Ville Syrjälä
2016-09-07 16:17 ` Lyude
2016-09-13 19:34 ` Zanoni, Paulo R
2016-09-14 9:59 ` Jani Nikula
2016-09-14 13:32 ` Zanoni, Paulo R [this message]
2016-09-15 7:15 ` Jani Nikula
2016-09-07 0:52 ` [PATCH 4/8] drm/i915/gen9: fix the WaWmMemoryReadLatency implementation Paulo Zanoni
2016-09-13 12:28 ` Maarten Lankhorst
2016-09-07 0:52 ` [PATCH 5/8] drm/i915/gen9: minimum scanlines for Y tile is not always 4 Paulo Zanoni
2016-09-07 23:03 ` Lyude
2016-09-13 20:22 ` Zanoni, Paulo R
2016-09-07 0:52 ` [PATCH 6/8] drm/i915/gen9: fix plane_blocks_per_line on watermarks calculations Paulo Zanoni
2016-09-07 0:52 ` [PATCH 7/8] drm/i915/gen9: fix the watermark res_blocks value Paulo Zanoni
2016-09-07 0:52 ` [PATCH 8/8] drm/i915/gen9: implement missing case for SKL watermarks calculation Paulo Zanoni
2016-09-07 1:24 ` ✗ Fi.CI.BAT: warning for SKL/KBL watermark fixes Patchwork
2016-09-07 23:54 ` [PATCH 0/8] " Lyude
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=1473859963.2435.103.camel@intel.com \
--to=paulo.r.zanoni@intel.com \
--cc=cpaul@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ville.syrjala@linux.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;
as well as URLs for NNTP newsgroup(s).