All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: ML dri-devel <dri-devel@lists.freedesktop.org>,
	"Linux-Kernel\@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 9/9] drm/vc4: Add an interface for capturing the GPU state after a hang.
Date: Wed, 02 Dec 2015 11:35:16 -0800	[thread overview]
Message-ID: <87r3j48wzv.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <CACvgo52FXmpJYtjT1nfmOrQZFB3CVTF=J2Zurpw=SULHSU-aAQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

Emil Velikov <emil.l.velikov@gmail.com> writes:

> On 1 December 2015 at 20:35, Eric Anholt <eric@anholt.net> 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 come in handy, despite that some are quite
> intel specific.
>
> On a related note - with the above project in place I'd imagine you
> have (re)considered about having libdrm-vc4 ? Copying hunks around
> might lead to interesting moments (as you have already noticed :-P)
>
> On that note I'll stop now with beating the libdrm drum :-)

The headers and code that I copy between the two userspace locations
will go in libdrm when I have a kernel ABI, but vc4_drm.h can't go in
until merging to the kernel, and there's not a whole lot of point
without that.

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).

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 9/9] drm/vc4: Add an interface for capturing the GPU state after a hang.
Date: Wed, 02 Dec 2015 11:35:16 -0800	[thread overview]
Message-ID: <87r3j48wzv.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <CACvgo52FXmpJYtjT1nfmOrQZFB3CVTF=J2Zurpw=SULHSU-aAQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1529 bytes --]

Emil Velikov <emil.l.velikov@gmail.com> writes:

> On 1 December 2015 at 20:35, Eric Anholt <eric@anholt.net> 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 come in handy, despite that some are quite
> intel specific.
>
> On a related note - with the above project in place I'd imagine you
> have (re)considered about having libdrm-vc4 ? Copying hunks around
> might lead to interesting moments (as you have already noticed :-P)
>
> On that note I'll stop now with beating the libdrm drum :-)

The headers and code that I copy between the two userspace locations
will go in libdrm when I have a kernel ABI, but vc4_drm.h can't go in
until merging to the kernel, and there's not a whole lot of point
without that.

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).

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-12-02 19:35 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 20:35 [PATCH 1/9] drm: Create a driver hook for allocating GEM object structs Eric Anholt
2015-12-01 20:35 ` Eric Anholt
2015-12-01 20:35 ` [PATCH 2/9] drm/vc4: Add a BO cache Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-01 20:35 ` [PATCH 3/9] drm/vc4: Add create and map BO ioctls Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-04 14:29   ` Emil Velikov
2015-12-04 14:29     ` Emil Velikov
2015-12-08  1:16     ` Eric Anholt
2015-12-08  1:16       ` Eric Anholt
2015-12-08  2:56       ` Michel Dänzer
2015-12-08  2:56         ` Michel Dänzer
2015-12-08  4:05         ` Eric Anholt
2015-12-08  4:05           ` Eric Anholt
2015-12-01 20:35 ` [PATCH 4/9] drm/vc4: Add an API for creating GPU shaders in GEM BOs Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-02 11:35   ` Emil Velikov
2015-12-02 11:35     ` Emil Velikov
2015-12-02 19:24     ` Eric Anholt
2015-12-02 19:24       ` Eric Anholt
2015-12-01 20:35 ` [PATCH 5/9] drm/vc4: Fix a typo in a V3D debug register Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-01 20:35 ` [PATCH 6/9] drm/vc4: Bind and initialize the V3D engine Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-01 20:35 ` [PATCH 7/9] drm/vc4: Add support for drawing 3D frames Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-02 11:29   ` Emil Velikov
2015-12-02 11:29     ` Emil Velikov
2015-12-02 19:27     ` Eric Anholt
2015-12-02 19:27       ` Eric Anholt
2015-12-01 20:35 ` [PATCH 8/9] drm/vc4: Add support for async pageflips Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-02 14:05   ` Daniel Stone
2015-12-02 14:05     ` Daniel Stone
2015-12-04  1:42     ` Eric Anholt
2015-12-04  1:42       ` Eric Anholt
2015-12-07 10:13       ` Daniel Stone
2015-12-07 10:13         ` Daniel Stone
2015-12-01 20:35 ` [PATCH 9/9] drm/vc4: Add an interface for capturing the GPU state after a hang Eric Anholt
2015-12-01 20:35   ` Eric Anholt
2015-12-02 11:45   ` Emil Velikov
2015-12-02 11:45     ` Emil Velikov
2015-12-02 19:35     ` Eric Anholt [this message]
2015-12-02 19:35       ` Eric Anholt
2015-12-02 22:26       ` Daniel Vetter
2015-12-02 22:26         ` Daniel Vetter
2015-12-02 22:58         ` Daniel Stone
2015-12-03 11:55           ` Emil Velikov
2015-12-03 11:55             ` Emil Velikov
2015-12-03 11:46       ` Emil Velikov
2015-12-03 11:46         ` Emil Velikov
2015-12-02  8:58 ` [PATCH 1/9] drm: Create a driver hook for allocating GEM object structs Daniel Vetter
2015-12-02  8:58   ` Daniel Vetter

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=87r3j48wzv.fsf@eliezer.anholt.net \
    --to=eric@anholt.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.