From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Marek Olšák" <maraeo@gmail.com>,
"Michel Dänzer" <michel@daenzer.net>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Jason Ekstrand" <jason@jlekstrand.net>,
"ML Mesa-dev" <mesa-dev@lists.freedesktop.org>
Subject: Re: [Mesa-dev] Linux Graphics Next: Userspace submission update
Date: Wed, 9 Jun 2021 15:58:26 +0200 [thread overview]
Message-ID: <1478737b-88aa-a24a-d2d7-cd3716df0cb0@gmail.com> (raw)
In-Reply-To: <YMC/4IhCePCu57HU@phenom.ffwll.local>
Am 09.06.21 um 15:19 schrieb Daniel Vetter:
> [SNIP]
>> Yeah, we call this the lightweight and the heavyweight tlb flush.
>>
>> The lighweight can be used when you are sure that you don't have any of the
>> PTEs currently in flight in the 3D/DMA engine and you just need to
>> invalidate the TLB.
>>
>> The heavyweight must be used when you need to invalidate the TLB *AND* make
>> sure that no concurrently operation moves new stuff into the TLB.
>>
>> The problem is for this use case we have to use the heavyweight one.
> Just for my own curiosity: So the lightweight flush is only for in-between
> CS when you know access is idle? Or does that also not work if userspace
> has a CS on a dma engine going at the same time because the tlb aren't
> isolated enough between engines?
More or less correct, yes.
The problem is a lightweight flush only invalidates the TLB, but doesn't
take care of entries which have been handed out to the different engines.
In other words what can happen is the following:
1. Shader asks TLB to resolve address X.
2. TLB looks into its cache and can't find address X so it asks the
walker to resolve.
3. Walker comes back with result for address X and TLB puts that into
its cache and gives it to Shader.
4. Shader starts doing some operation using result for address X.
5. You send lightweight TLB invalidate and TLB throws away cached values
for address X.
6. Shader happily still uses whatever the TLB gave to it in step 3 to
accesses address X
See it like the shader has their own 1 entry L0 TLB cache which is not
affected by the lightweight flush.
The heavyweight flush on the other hand sends out a broadcast signal to
everybody and only comes back when we are sure that an address is not in
use any more.
Christian.
> -Daniel
>
next prev parent reply other threads:[~2021-06-09 13:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 21:51 Linux Graphics Next: Userspace submission update Marek Olšák
2021-05-28 14:41 ` Christian König
2021-05-28 22:25 ` Marek Olšák
2021-05-29 3:33 ` Marek Olšák
2021-05-31 8:25 ` Christian König
2021-06-01 9:02 ` Michel Dänzer
2021-06-01 10:21 ` Christian König
2021-06-01 10:49 ` Michel Dänzer
2021-06-01 12:10 ` [Mesa-dev] " Christian König
2021-06-01 12:30 ` Daniel Vetter
2021-06-01 12:51 ` Christian König
2021-06-01 13:01 ` Marek Olšák
2021-06-01 13:24 ` Michel Dänzer
2021-06-02 8:57 ` Daniel Stone
2021-06-02 9:34 ` Marek Olšák
2021-06-02 9:38 ` Marek Olšák
2021-06-02 18:48 ` Daniel Vetter
2021-06-02 18:52 ` Christian König
2021-06-02 19:19 ` Daniel Vetter
2021-06-04 7:00 ` Christian König
2021-06-04 8:57 ` Daniel Vetter
2021-06-04 11:27 ` Christian König
2021-06-09 13:19 ` Daniel Vetter
2021-06-09 13:58 ` Christian König [this message]
2021-06-09 18:31 ` Daniel Vetter
2021-06-10 15:59 ` Marek Olšák
2021-06-10 16:33 ` Christian König
2021-06-14 17:10 ` Marek Olšák
2021-06-14 17:13 ` Christian König
2021-06-17 16:48 ` Daniel Vetter
2021-06-17 18:28 ` Marek Olšák
2021-06-17 19:04 ` Daniel Vetter
2021-06-17 19:23 ` Marek Olšák
2021-06-03 3:16 ` Marek Olšák
2021-06-03 7:47 ` Daniel Vetter
2021-06-03 8:20 ` Marek Olšák
2021-06-03 10:03 ` Daniel Vetter
2021-06-03 10:55 ` Marek Olšák
2021-06-03 11:22 ` Daniel Vetter
2021-06-03 17:52 ` Marek Olšák
2021-06-03 19:18 ` Daniel Vetter
2021-06-04 5:26 ` Marek Olšák
2021-06-02 9:44 ` Christian König
2021-06-02 9:58 ` Marek Olšák
2021-06-02 10:06 ` Christian König
2021-06-01 13:18 ` Michel Dänzer
2021-06-01 17:39 ` Michel Dänzer
2021-06-01 17:42 ` Daniel Stone
2021-06-02 8:09 ` Michel Dänzer
2021-06-02 19:20 ` 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=1478737b-88aa-a24a-d2d7-cd3716df0cb0@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
--cc=maraeo@gmail.com \
--cc=mesa-dev@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).