From: Daniel Vetter <daniel@ffwll.ch>
To: Chia-I Wu <olvaffe@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: fix wait ioctl with negative timeout
Date: Tue, 21 Oct 2014 17:03:29 +0200 [thread overview]
Message-ID: <20141021150328.GO26941@phenom.ffwll.local> (raw)
In-Reply-To: <CAPaKu7Q-d2VzN0XVOCuQQf52+Q2ysjUCCKFX56TxDn1y7G9hfA@mail.gmail.com>
On Mon, Oct 13, 2014 at 12:40:48AM +0800, Chia-I Wu wrote:
> On Sun, Oct 12, 2014 at 1:21 AM, Chia-I Wu <olvaffe@gmail.com> wrote:
>
> > When timeout_ns is negative, it really means to wait indefinitely instead
> > of
> > returning immediately. But since userspace can no longer rely on that, I
> > am
> > not sure if there is any point fixing it.
> >
> Note that userspace may use GL_TIMEOUT_IGNORED for timeout_ns to wait
> indefinitely. The macro is defined to
>
> #define GL_TIMEOUT_IGNORED 0xFFFFFFFFFFFFFFFFull
>
> Prior to 3.17, the kernel would behave as expected. But on 3.17, it would
> return immediately with -ETIME if the bo is busy.
That sounds like a regression, for which we need a testcase in igt and a
special-case in our wait ioctl to make sure that we have an infinite
timeout for this input value. Can you please take care of both?
I guess we could also restore the bevahiour for negative timeouts, just
for the sake of it. Would again need a testcase though. Also note that
I've recently refactored the wait ioctl testcase, so adding new subtests
should be a lot easier now.
Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-10-21 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 17:21 [PATCH] drm/i915: fix wait ioctl with negative timeout Chia-I Wu
2014-10-12 16:40 ` Chia-I Wu
2014-10-21 15:03 ` Daniel Vetter [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=20141021150328.GO26941@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=olvaffe@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox