public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org,
	Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	david.emett@broadcom.com, thomas.spurden@broadcom.com
Subject: Re: [PATCH v2 3/5] drm/v3d: Add support for compute shader dispatch.
Date: Wed, 17 Apr 2019 14:53:33 -0700	[thread overview]
Message-ID: <87v9zc1eoy.fsf@anholt.net> (raw)
In-Reply-To: <20190416225856.20264-4-eric@anholt.net>

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

Eric Anholt <eric@anholt.net> writes:

> The compute shader dispatch interface is pretty simple -- just pass in
> the regs that userspace has passed us, with no CLs to run.  However,
> with no CL to run it means that we need to do manual cache flushing of
> the L2 after the HW execution completes (for SSBO, atomic, and
> image_load_store writes that are the output of compute shaders).
>
> This doesn't yet expose the L2 cache's ability to have a region of the
> address space not write back to memory (which could be used for
> shared_var storage).
>
> So far, the Mesa side has been tested on V3D v4.2 simpenrose (passing
> the ES31 tests), and on the kernel side on 7278 (failing atomic
> compswap tests in a way that doesn't reproduce on simpenrose).

Fixed the compswap issue in Mesa.  Looks like cmpxchg needed the TYPE
field set to vec2 instead of 32-bit, since there are two values written
to TMUD.  The spec says the field is ignored, but that doesn't seem to
be the case.

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

  reply	other threads:[~2019-04-17 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 22:58 [PATCH v2 0/5] V3D CSD support, implicit sync fix Eric Anholt
2019-04-16 22:58 ` [PATCH v2 1/5] drm/v3d: Switch the type of job-> to reduce casting Eric Anholt
2019-04-16 22:58 ` [PATCH v2 2/5] drm/v3d: Refactor job management Eric Anholt
2019-04-16 22:58 ` [PATCH v2 3/5] drm/v3d: Add support for compute shader dispatch Eric Anholt
2019-04-17 21:53   ` Eric Anholt [this message]
2019-04-16 22:58 ` [PATCH v2 4/5] drm/v3d: Drop reservation of a shared slot in the dma-buf reservations Eric Anholt
2019-04-16 22:58 ` [PATCH v2 5/5] drm/v3d: Add missing implicit synchronization Eric Anholt

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=87v9zc1eoy.fsf@anholt.net \
    --to=eric@anholt.net \
    --cc=david.emett@broadcom.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=thomas.spurden@broadcom.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