On Mon, Mar 9, 2020 at 11:21 AM Christian König
wrote:
>
> Am 05.03.20 um 16:54 schrieb Jason Ekstrand:
> > On Thu, Mar 5, 2020 at 7:06 AM Christian König
> > wrote:
> >> [SNIP]
> >> Well as far as I can see this won't work because it would break the
> >> semantics of the timeline sync.
> > I'm
Am 05.03.20 um 16:54 schrieb Jason Ekstrand:
On Thu, Mar 5, 2020 at 7:06 AM Christian König wrote:
[SNIP]
Well as far as I can see this won't work because it would break the
semantics of the timeline sync.
I'm not 100% convinced it has to. We already have support for the
seqno regressing and
On Thu, Mar 5, 2020 at 7:06 AM Christian König wrote:
>
> Am 04.03.20 um 17:41 schrieb Jason Ekstrand:
> > On Wed, Mar 4, 2020 at 10:27 AM Jason Ekstrand wrote:
> >> On Wed, Mar 4, 2020 at 2:34 AM Christian König
> >> wrote:
> >>> Am 03.03.20 um 20:10 schrieb Jason Ekstrand:
> On Thu, Feb
Am 04.03.20 um 17:41 schrieb Jason Ekstrand:
On Wed, Mar 4, 2020 at 10:27 AM Jason Ekstrand wrote:
On Wed, Mar 4, 2020 at 2:34 AM Christian König wrote:
Am 03.03.20 um 20:10 schrieb Jason Ekstrand:
On Thu, Feb 27, 2020 at 2:28 AM Christian König
wrote:
[SNIP]
For reference see what dance i
On Wed, Mar 4, 2020 at 10:27 AM Jason Ekstrand wrote:
>
> On Wed, Mar 4, 2020 at 2:34 AM Christian König
> wrote:
> >
> > Am 03.03.20 um 20:10 schrieb Jason Ekstrand:
> > > On Thu, Feb 27, 2020 at 2:28 AM Christian König
> > > wrote:
> > >> [SNIP]
> > >>> However, I'm not sure what the best way
On Wed, Mar 4, 2020 at 2:34 AM Christian König wrote:
>
> Am 03.03.20 um 20:10 schrieb Jason Ekstrand:
> > On Thu, Feb 27, 2020 at 2:28 AM Christian König
> > wrote:
> >> [SNIP]
> >>> However, I'm not sure what the best way is to do garbage collection on
> >>> that so that we don't get an impossi
Am 03.03.20 um 20:10 schrieb Jason Ekstrand:
On Thu, Feb 27, 2020 at 2:28 AM Christian König
wrote:
[SNIP]
However, I'm not sure what the best way is to do garbage collection on
that so that we don't get an impossibly list of fence arrays.
Exactly yes. That's also the reason why the dma_fence
On Thu, Feb 27, 2020 at 2:28 AM Christian König
wrote:
>
> Am 26.02.20 um 17:46 schrieb Bas Nieuwenhuizen:
> > On Wed, Feb 26, 2020 at 4:29 PM Jason Ekstrand wrote:
> >> On Wed, Feb 26, 2020 at 4:05 AM Daniel Vetter wrote:
> >>> On Wed, Feb 26, 2020 at 10:16:05AM +0100, Christian König wrote:
>
Vulkan WSI user of the new API:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4037
On Tue, Mar 3, 2020 at 1:03 PM Jason Ekstrand wrote:
>
> Explicit synchronization is the future. At least, that seems to be what
> most userspace APIs are agreeing on at this point. However, most of
Explicit synchronization is the future. At least, that seems to be what
most userspace APIs are agreeing on at this point. However, most of our
Linux APIs (both userspace and kernel UAPI) are currently built around
implicit synchronization with dma-buf. While work is ongoing to change
many of th
Am 26.02.20 um 17:46 schrieb Bas Nieuwenhuizen:
On Wed, Feb 26, 2020 at 4:29 PM Jason Ekstrand wrote:
On Wed, Feb 26, 2020 at 4:05 AM Daniel Vetter wrote:
On Wed, Feb 26, 2020 at 10:16:05AM +0100, Christian König wrote:
[SNIP]
Just imagine that you access some DMA-buf with a shader and that
Explicit synchronization is the future. At least, that seems to be what
most userspace APIs are agreeing on at this point. However, most of our
Linux APIs (both userspace and kernel UAPI) are currently built around
implicit synchronization with dma-buf. While work is ongoing to change
many of th
On Wed, Feb 26, 2020 at 4:29 PM Jason Ekstrand wrote:
>
> On Wed, Feb 26, 2020 at 4:05 AM Daniel Vetter wrote:
> >
> > On Wed, Feb 26, 2020 at 10:16:05AM +0100, Christian König wrote:
> > > Hi Jason,
> > >
> > > Am 26.02.20 um 00:58 schrieb Jason Ekstrand:
> > > > Explicit synchronization is the
On Wed, Feb 26, 2020 at 4:05 AM Daniel Vetter wrote:
>
> On Wed, Feb 26, 2020 at 10:16:05AM +0100, Christian König wrote:
> > Hi Jason,
> >
> > Am 26.02.20 um 00:58 schrieb Jason Ekstrand:
> > > Explicit synchronization is the future. At least, that seems to be what
> > > most userspace APIs are
On Wed, Feb 26, 2020 at 10:16:05AM +0100, Christian König wrote:
> Hi Jason,
>
> Am 26.02.20 um 00:58 schrieb Jason Ekstrand:
> > Explicit synchronization is the future. At least, that seems to be what
> > most userspace APIs are agreeing on at this point. However, most of our
> > Linux APIs (bo
Hi Jason,
Am 26.02.20 um 00:58 schrieb Jason Ekstrand:
Explicit synchronization is the future. At least, that seems to be what
most userspace APIs are agreeing on at this point. However, most of our
Linux APIs (both userspace and kernel UAPI) are currently built around
implicit synchronization
Explicit synchronization is the future. At least, that seems to be what
most userspace APIs are agreeing on at this point. However, most of our
Linux APIs (both userspace and kernel UAPI) are currently built around
implicit synchronization with dma-buf. While work is ongoing to change
many of th
17 matches
Mail list logo
