From: Gustavo Padovan <gustavo@padovan.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: John Einar Reitan <john.reitan@arm.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] sync_file: Return consistent status in SYNC_IOC_FILE_INFO
Date: Mon, 9 Oct 2017 14:28:02 -0300 [thread overview]
Message-ID: <20171009172802.GA26962@jade> (raw)
In-Reply-To: <150755721510.26467.14976900836114227400@mail.alporthouse.com>
2017-10-09 Chris Wilson <chris@chris-wilson.co.uk>:
> Quoting John Einar Reitan (2017-10-09 14:49:36)
> > sync_file_ioctl_fence_info has a race between filling the status
> > of the underlying fences and the overall status of the sync_file.
> > If fence transitions in the time frame between its sync_fill_fence_info
> > and the later dma_fence_is_signaled for the sync_file, the returned
> > information is inconsistent showing non-signaled underlying fences but
> > an overall signaled state.
> >
> > This patch changes sync_file_ioctl_fence_info to track what has been
> > encoded and using that as the overall sync_file status.
> >
> > Tested-by: Vamsidhar Reddy Gaddam <vamsidhar.gaddam@arm.com>
> > Signed-off-by: John Einar Reitan <john.reitan@arm.com>
> > Cc: Sumit Semwal <sumit.semwal@linaro.org>
> > Cc: Gustavo Padovan <gustavo@padovan.org>
> > Cc: dri-devel@lists.freedesktop.org
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Pushed to drm-misc-fixes.
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-10-09 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 13:51 [PATCH] sync_file: Return consistent status in SYNC_IOC_FILE_INFO John Einar Reitan
2017-10-04 10:43 ` Chris Wilson
2017-10-04 12:15 ` John Einar Reitan
2017-10-09 13:49 ` [PATCH v2] " John Einar Reitan
2017-10-09 13:53 ` Chris Wilson
2017-10-09 17:28 ` Gustavo Padovan [this message]
2017-10-10 6:09 ` Chunming Zhou
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=20171009172802.GA26962@jade \
--to=gustavo@padovan.org \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=john.reitan@arm.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.