Re: [PATCH] drm/panthor: Don't add write fences to the shared BOs

2024-10-01 Thread Boris Brezillon
On Thu, 5 Sep 2024 09:01:54 +0200 Boris Brezillon wrote: > The only user (the mesa gallium driver) is already assuming explicit > synchronization and doing the export/import dance on shared BOs. The > only reason we were registering ourselves as writers on external BOs > is because Xe, which was

Re: [PATCH] drm/panthor: Don't add write fences to the shared BOs

2024-09-24 Thread Simona Vetter
On Thu, Sep 05, 2024 at 09:01:54AM +0200, Boris Brezillon wrote: > The only user (the mesa gallium driver) is already assuming explicit > synchronization and doing the export/import dance on shared BOs. The > only reason we were registering ourselves as writers on external BOs > is because Xe, whic

Re: [PATCH] drm/panthor: Don't add write fences to the shared BOs

2024-09-05 Thread Liviu Dudau
On Thu, Sep 05, 2024 at 09:01:54AM +0200, Boris Brezillon wrote: > The only user (the mesa gallium driver) is already assuming explicit > synchronization and doing the export/import dance on shared BOs. The > only reason we were registering ourselves as writers on external BOs > is because Xe, whic

Re: [PATCH] drm/panthor: Don't add write fences to the shared BOs

2024-09-05 Thread Steven Price
On 05/09/2024 08:01, Boris Brezillon wrote: > The only user (the mesa gallium driver) is already assuming explicit > synchronization and doing the export/import dance on shared BOs. The > only reason we were registering ourselves as writers on external BOs > is because Xe, which was the reference b

[PATCH] drm/panthor: Don't add write fences to the shared BOs

2024-09-05 Thread Boris Brezillon
The only user (the mesa gallium driver) is already assuming explicit synchronization and doing the export/import dance on shared BOs. The only reason we were registering ourselves as writers on external BOs is because Xe, which was the reference back when we developed Panthor, was doing so. Turns o