From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Steven Price <steven.price@arm.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: [PATCH] drm/panfrost: Add "compute shader only" hint
Date: Wed, 7 Aug 2019 07:19:55 -0700 [thread overview]
Message-ID: <20190807141955.GB3285@kevin> (raw)
In-Reply-To: <cbd704ac-f8fd-a2ed-498c-056be221398b@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1207 bytes --]
Ah-ha! Thank you for the detailed explanation; this makes a lot more
sense now :)
> In practice all this only really matters on the T62x GPU. All other GPUs
> have only one core group[1]. So it only really makes sense to use JS2 on
> the T62x where you want to use both JS1 and JS2 to run two independent
> jobs: one on each core group.
>
> Oh, and there is one hardware workaround (BASE_HW_ISSUE_8987) that uses
> JS2. This is to avoid vertex and compute jobs landing on the same slot.
> This affects T604 "dev15" only and is because some state was not
> properly cleared between jobs.
On my end at least, our work with compute has been focused on
RK3399/T860. In userspace, it's tempting to limit T6xx/T720 to e.g.
OpenGL ES 2.0 (between this/other errata, and of course fake-MRT), at
least for the interim.
For completeness, we'll maybe need to deal with this Eventually, but it
doesn't sound like this needs to be handled right now? (It sounds like
there's no changes needed for compute on T700+, since #8987 doesn't
apply and there's only one core group.). In that case, maybe it's not
worth it to start mucking with the UABI for a feature that may or may
not ever be used.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-08-07 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 19:52 [PATCH] drm/panfrost: Add "compute shader only" hint Alyssa Rosenzweig
2019-08-06 20:01 ` Rob Herring
2019-08-06 20:11 ` Alyssa Rosenzweig
2019-08-06 20:21 ` Rob Herring
2019-08-06 20:25 ` Alyssa Rosenzweig
2019-08-07 11:11 ` Steven Price
2019-08-07 14:19 ` Alyssa Rosenzweig [this message]
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=20190807141955.GB3285@kevin \
--to=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox