On Tue, Nov 04, 2014 at 11:00:46AM -0800, Rodrigo Vivi wrote:
> just a warn/heads-up: I had listed this one for -collector but got a
> conflict because skl latency retrieval didn't get merged yet.
I carry those in my SKL branch and will resend them as part of stage1
upstreaming, I think you can dr
just a warn/heads-up: I had listed this one for -collector but got a
conflict because skl latency retrieval didn't get merged yet.
On Fri, Sep 5, 2014 at 5:53 AM, Damien Lespiau wrote:
> Ville had 2 comments on the SKL memory latency patch that are better addressed
> as separate patches on top.
>
Ville had 2 comments on the SKL memory latency patch that are better addressed
as separate patches on top.
Patch 1: SKL unifies the plane hw and their latencies to fech data from memory
is identical. So SKL only needs a single array. We save some room by using
anymous union/structs. However, last
