linux-kernel - Re: [git pull] drm for v4.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d4823dd9-56e7-6b8c-4e2c-d7b48c7413c1@gmail.com>
Date:   Sat, 18 Nov 2017 11:49:27 +0100
From:   Nicolai Hähnle <nhaehnle@...il.com>
To:     christian.koenig@....com,
        Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [git pull] drm for v4.15

On 17.11.2017 20:18, Christian König wrote:
> The obvious alternative which we are working on for a few years now is 
> to improve the input data we get from the hardware people.
> 
> In other words instead of getting a flat list of registers we want the 
> information about where and how many times a hardware block was 
> instantiated.
> 
> But getting that proved much more difficult than we thought and yes we 
> are working on that for multiple years now.

Well, the good news is that at least for the gfx registers, I actually 
have a proof-of-concept script that extracts the required information 
from the hardware sources. Generating e.g. a CB_COLOR_INFO(x) macro 
instead of CB_COLORx_INFO defines from that is not that hard :)

The real challenge is getting this integrated into the right processes 
so we don't have as much of a maintenance burden.

Cheers,
Nicolai
-- 
Lerne, wie die Welt wirklich ist,
Aber vergiss niemals, wie sie sein sollte.