From: "Marek Olšák" <maraeo@gmail.com>
To: "amd-gfx mailing list" <amd-gfx@lists.freedesktop.org>,
"Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>,
"Michel Dänzer" <michel@daenzer.net>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>
Subject: Re: amdgpu doesn't do implicit sync, requires drivers to do it in IBs
Date: Mon, 25 May 2020 18:07:14 -0400 [thread overview]
Message-ID: <CAAxE2A7wy4CBevdHwQzGgYFZHkEUP4Fokj2CzET9GmJWHA+kww@mail.gmail.com> (raw)
In-Reply-To: <CAAxE2A5Kv9oB7TnoAKSLfuB7unYZzgggSY=BaNyHZq0Fvi+5Qw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 651 bytes --]
If a user mode driver is changed to rely on the existence of implicit sync,
it results in corruption and flickering as reported here:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2950
Marek
On Mon, May 25, 2020 at 6:05 PM Marek Olšák <maraeo@gmail.com> wrote:
> Hi Christian,
>
> Bas and Michel wanted to discuss this. The main disadvantage of no
> implicit (pipeline) sync within the same queue is that we get lower
> performance and lower GPU utilization in some cases.
>
> We actually never really needed the kernel to have implicit sync, because
> all user mode drivers contained hacks to work without it.
>
> Marek
>
[-- Attachment #1.2: Type: text/html, Size: 1110 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-05-25 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 22:05 amdgpu doesn't do implicit sync, requires drivers to do it in IBs Marek Olšák
2020-05-25 22:07 ` Marek Olšák [this message]
2020-05-28 9:11 ` Christian König
2020-05-28 10:06 ` Michel Dänzer
2020-05-28 14:39 ` Christian König
2020-05-28 16:06 ` Marek Olšák
2020-05-28 18:12 ` Christian König
2020-05-28 19:35 ` Marek Olšák
2020-05-29 9:05 ` Christian König
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=CAAxE2A7wy4CBevdHwQzGgYFZHkEUP4Fokj2CzET9GmJWHA+kww@mail.gmail.com \
--to=maraeo@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bas@basnieuwenhuizen.nl \
--cc=ckoenig.leichtzumerken@gmail.com \
--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 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.