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 wrote: > Hey, > > On 2 December 2015 at 22:26, Daniel Vetter 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

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

On 2 December 2015 at 19:35, Eric Anholt wrote: > Emil Velikov writes: > >> On 1 December 2015 at 20:35, Eric Anholt wrote: >>> This can be parsed with vc4-gpu-tools tools for trying to figure out >>> what was going on. >>> >> I might be pushing my luck here ... have you thought about basing >>

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

On 2 December 2015 at 19:35, Eric Anholt wrote: > Emil Velikov writes: > >> On 1 December 2015 at 20:35, Eric Anholt wrote: >>> This can be parsed with vc4-gpu-tools tools for trying to figure out >>> what was going on. >>> >> I might

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 wrote: > Hey, > > On 2 December 2015 at 22:26, Daniel Vetter 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.

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

Hey, On 2 December 2015 at 22:26, Daniel Vetter 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.

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

On Wed, Dec 02, 2015 at 11:35:16AM -0800, Eric Anholt wrote: > Emil Velikov writes: > > > On 1 December 2015 at 20:35, Eric Anholt wrote: > >> This can be parsed with vc4-gpu-tools tools for trying to figure out > >> what was going on. > >> > > I might be pushing my luck here ... have you

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

Emil Velikov writes: > On 1 December 2015 at 20:35, Eric Anholt wrote: >> This can be parsed with vc4-gpu-tools tools for trying to figure out >> what was going on. >> > I might be pushing my luck here ... have you thought about basing > (forking) vc4-gpu-tools of intel-gpu-tools ? I'd imagine

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

On 1 December 2015 at 20:35, Eric Anholt wrote: > This can be parsed with vc4-gpu-tools tools for trying to figure out > what was going on. > I might be pushing my luck here ... have you thought about basing (forking) vc4-gpu-tools of intel-gpu-tools ? I'd imagine that the macros and helpers will

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

Emil Velikov writes: > On 1 December 2015 at 20:35, Eric Anholt wrote: >> This can be parsed with vc4-gpu-tools tools for trying to figure out >> what was going on. >> > I might be pushing my luck here ... have you thought about basing > (forking)

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

Hey, On 2 December 2015 at 22:26, Daniel Vetter 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

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

On Wed, Dec 02, 2015 at 11:35:16AM -0800, Eric Anholt wrote: > Emil Velikov writes: > > > On 1 December 2015 at 20:35, Eric Anholt wrote: > >> This can be parsed with vc4-gpu-tools tools for trying to figure out > >> what was going on. > >> > > I might

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

On 1 December 2015 at 20:35, Eric Anholt wrote: > This can be parsed with vc4-gpu-tools tools for trying to figure out > what was going on. > I might be pushing my luck here ... have you thought about basing (forking) vc4-gpu-tools of intel-gpu-tools ? I'd imagine that the macros

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

This can be parsed with vc4-gpu-tools tools for trying to figure out what was going on. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_drv.c | 2 + drivers/gpu/drm/vc4/vc4_drv.h | 4 + drivers/gpu/drm/vc4/vc4_gem.c | 185 ++

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

This can be parsed with vc4-gpu-tools tools for trying to figure out what was going on. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_drv.c | 2 + drivers/gpu/drm/vc4/vc4_drv.h | 4 + drivers/gpu/drm/vc4/vc4_gem.c | 185 ++