linux-kernel - Re: [PATCH 9/9] drm/vc4: Add an interface for capturing the GPU state after a hang.

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Dec 2015 11:55:01 +0000
From:	Emil Velikov <emil.l.velikov@...il.com>
To:	Daniel Stone <daniel@...ishbar.org>
Cc:	Eric Anholt <eric@...olt.net>,
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
	ML dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH 9/9] drm/vc4: Add an interface for capturing the GPU state
 after a hang.

Hi Dan,

On 2 December 2015 at 22:58, Daniel Stone <daniel@...ishbar.org> wrote:
> Hey,
>
> On 2 December 2015 at 22:26, Daniel Vetter <daniel@...ll.ch> wrote:
>> On Wed, Dec 02, 2015 at 11:35:16AM -0800, Eric Anholt wrote:
>>> Yes, I have thought about basing vc4-gpu-tools off of intel-gpu-tools.
>>> I've actually tried to build and use the kms testing stuff on vc4, and
>>> it was a total bust.  Someone needs to do a lot of work to make igt
>>> useful for non-intel.  If you'd like me to build my vc4 testing inside
>>> of igt, I'd someone to demo one of my tests building inside of igt, with
>>> the test runner working and none of the intel-specific tests reporting
>>> failure, and get me permission to just push code to that repository
>>> (It's hard enough getting piglit tests reviewed, vc4-specific tests and
>>> tools would never get review).
>>
>> Daniel Stone claimed that this Just Works but evidently it doesn't.
>> There's some autoconfig fail where igt wants too much intel crap that just
>> doesn't build on arm. Iirc Daniel had some patches floating around for
>> that.
>
> Yeah, it was working, though with my ARM farm still being in pieces, I
> haven't been able to keep on top of it lately. Apparently the patch to
> disable the ancilliary tools fixes the build, so I'll get that pushed
> when I can actually test it, or for the meantime:
> http://paste.fedoraproject.org/296836/09692714
>
Afaict pretty much all of the binaries "disabled" with this patch are
intel specific. As such please throw a configure switch (enabled by
default) rather than the current build_x86 heuristic, otherwise things
are bound to get very ugly pretty quickly.

> This does still require libpciaccess and libdrm-intel to be built, but
> they _are_ totally possible to build on ARM, without any stupid hacks.
> My first cut at getting igt running on ARM (before Micah took over)
> actually started by eviscerating those as well, but it ended up being
> too much of a yak-shave.
>
The libpciaccess will be a pain although libdrm-intel should be
relatively easier. I doubt people will have major issues if the former
requirement stays forever.

Thanks
Emil
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/