From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: Joshua Ashton <joshua@froggi.es>,
amd-gfx@lists.freedesktop.org,
Faith Ekstrand <faith@gfxstrand.net>,
dri-devel@lists.freedesktop.org
Cc: "Faith Ekstrand" <faith.ekstrand@collabora.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Michel Dänzer" <mdaenzer@redhat.com>,
"Bas Nieuwenhuizen" <bas@basnieuwenhuizen.nl>
Subject: Re: [RFC] amdgpu: Add a context flag to disable implicit sync
Date: Thu, 8 Aug 2024 09:57:52 +0200 [thread overview]
Message-ID: <3c887552-282d-403d-8581-4cbcd8ad9069@mailbox.org> (raw)
In-Reply-To: <B37A903E-E670-4548-BDBB-4651D2DC7D15@froggi.es>
On 2024-08-07 21:23, Joshua Ashton wrote:
> I was thinking about this more recently. I was initially considering "maybe this should be a per-BO import," but I couldn't think of anything in the GL model that would actually benefit given its not "true" bindless and there's no update-after-bind there.
>
> Worth others more familiar with GL asking that question to themselves also. I am definitely not totally up on what's possible there.
>
> Overall, I think I am OK with this approach, even though I think mixing implicit and explicit sync is gross, and I want the pain that is implicit sync to just go away forever. :-)
It can never go away, at least not in the drivers which have ever supported it. We can never break compatibility.
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
prev parent reply other threads:[~2024-08-08 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 15:39 [RFC] amdgpu: Add a context flag to disable implicit sync Faith Ekstrand
2024-08-07 19:23 ` Joshua Ashton
2024-08-07 20:25 ` Faith Ekstrand
2024-08-07 20:33 ` Bas Nieuwenhuizen
2024-08-19 14:51 ` Christian König
2024-08-19 14:59 ` Bas Nieuwenhuizen
2024-08-19 16:00 ` Faith Ekstrand
2024-08-08 7:57 ` Michel Dänzer [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=3c887552-282d-403d-8581-4cbcd8ad9069@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bas@basnieuwenhuizen.nl \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=faith.ekstrand@collabora.com \
--cc=faith@gfxstrand.net \
--cc=joshua@froggi.es \
--cc=mdaenzer@redhat.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 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.