On Thursday 03 November 2016, Jason Ekstrand wrote:
> On Thu, Nov 3, 2016 at 2:53 AM, Chris Wilson
> wrote:
>
> > On Wed, Nov 02, 2016 at 05:15:52PM -0700, Jason Ekstrand wrote:
> > > @@ -1562,22 +1580,98 @@ VkResult anv_WaitForFences(
> > > * best we can do is to clamp the timeout to INT64_
On Thu 03 Nov 2016, Jason Ekstrand wrote:
>
>
> On Thu, Nov 3, 2016 at 10:59 AM, Chad Versace
> wrote:
>
> On Wed 02 Nov 2016, Jason Ekstrand wrote:
> > @@ -1116,6 +1117,11 @@ VkResult anv_QueueSubmit(
> > result = anv_device_execbuf(device, &fence->execbuf, &fence_bo);
>
On Thu, Nov 3, 2016 at 10:59 AM, Chad Versace
wrote:
> On Wed 02 Nov 2016, Jason Ekstrand wrote:
> > Our previous fence implementation was very simple. Fences had two
> states:
> > signaled and unsignaled. However, this didn't properly handle all of the
> > edge-cases that we need to handle. I
On Wed 02 Nov 2016, Jason Ekstrand wrote:
> Our previous fence implementation was very simple. Fences had two states:
> signaled and unsignaled. However, this didn't properly handle all of the
> edge-cases that we need to handle. In order to handle the case where the
> client calls vkGetFenceSta
On Thu, Nov 3, 2016 at 2:53 AM, Chris Wilson
wrote:
> On Wed, Nov 02, 2016 at 05:15:52PM -0700, Jason Ekstrand wrote:
> > @@ -1562,22 +1580,98 @@ VkResult anv_WaitForFences(
> > * best we can do is to clamp the timeout to INT64_MAX. This limits
> the
> > * maximum timeout from 584 year
On Wed, Nov 02, 2016 at 05:15:52PM -0700, Jason Ekstrand wrote:
> @@ -1562,22 +1580,98 @@ VkResult anv_WaitForFences(
> * best we can do is to clamp the timeout to INT64_MAX. This limits the
> * maximum timeout from 584 years to 292 years - likely not a big deal.
> */
> - if (time
Our previous fence implementation was very simple. Fences had two states:
signaled and unsignaled. However, this didn't properly handle all of the
edge-cases that we need to handle. In order to handle the case where the
client calls vkGetFenceStatus on a fence that has not yet been submitted
via
