From: Hans Verkuil <hverkuil@xs4all.nl>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
linux-media@vger.kernel.org,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Pawel Osciak <pawel@osciak.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH/RFC v2 1/2] v4l: vb2: Don't return POLLERR during transient buffer underruns
Date: Mon, 15 Sep 2014 13:14:51 +0200 [thread overview]
Message-ID: <5416CA2B.1080004@xs4all.nl> (raw)
In-Reply-To: <2394481.2zcs5YKt7z@avalon>
On 06/06/2014 03:42 PM, Laurent Pinchart wrote:
> On Friday 06 June 2014 11:58:18 Hans Verkuil wrote:
>> On 06/06/2014 11:50 AM, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 06/05/2014 02:23 PM, Laurent Pinchart wrote:
>>>> The V4L2 specification states that
>>>>
>>>> "When the application did not call VIDIOC_QBUF or VIDIOC_STREAMON yet
>>>> the poll() function succeeds, but sets the POLLERR flag in the revents
>>>> field."
>>>>
>>>> The vb2_poll() function sets POLLERR when the queued buffers list is
>>>> empty, regardless of whether this is caused by the stream not being
>>>> active yet, or by a transient buffer underrun.
>>>>
>>>> Bring the implementation in line with the specification by returning
>>>> POLLERR only when the queue is not streaming. Buffer underruns during
>>>> streaming are not treated specially anymore and just result in poll()
>>>> blocking until the next event.
>>>
>>> After your patch the implementation is still not inline with the spec,
>>> queuing buffers, then starting a thread doing the poll, then doing the
>>> streamon in the main thread will still cause the poll to return POLLERR,
>>> even though buffers are queued, which according to the spec should be
>>> enough for the poll to block.
>>>
>>> The correct check would be:
>>>
>>> if (list_empty(&q->queued_list) && !vb2_is_streaming(q))
>>>
>>> eturn res | POLLERR;
>>
>> Good catch! I should have seen that :-(
Urgh. This breaks vbi capture tools like alevt and mtt. These rely on poll
returning POLLERR if buffers are queued but STREAMON has not been called yet.
See bug report https://bugzilla.kernel.org/show_bug.cgi?id=84401
The spec also clearly says that poll should return POLLERR if STREAMON
was not called.
But that would clash with this multi-thread example.
Hans, was this based on actual code that needed this?
I am inclined to update alevt and mtt: all that is needed to make it work
is a single line that explicitly calls the vbi handler before entering the
main loop. This is effectively the same as what happens when the first
select gets a POLLERR.
We maintain alevt (dvb-apps) and mtt (xawtv3), so that's easy enough to
fix.
Note that the spec is now definitely out-of-sync since poll no longer returns
POLLERR if buffers are queued but STREAMON wasn't called.
Regards,
Hans
>
> I'll update the patch accordingly.
>
>> v4l2-compliance should certainly be extended to test this as well.
>>
>> Regards,
>>
>> Hans
>>
>>> Regards,
>>>
>>> Hans
>>>
>>>> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>>> Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
>>>> ---
>>>>
>>>> drivers/media/v4l2-core/videobuf2-core.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/media/v4l2-core/videobuf2-core.c
>>>> b/drivers/media/v4l2-core/videobuf2-core.c index 349e659..fd428e0 100644
>>>> --- a/drivers/media/v4l2-core/videobuf2-core.c
>>>> +++ b/drivers/media/v4l2-core/videobuf2-core.c
>>>> @@ -2533,9 +2533,9 @@ unsigned int vb2_poll(struct vb2_queue *q, struct
>>>> file *file, poll_table *wait)>>
>>>> }
>>>>
>>>> /*
>>>>
>>>> - * There is nothing to wait for if no buffers have already been
> queued.
>>>> + * There is nothing to wait for if the queue isn't streaming.
>>>>
>>>> */
>>>>
>>>> - if (list_empty(&q->queued_list))
>>>> + if (!vb2_is_streaming(q))
>>>>
>>>> return res | POLLERR;
>>>>
>>>> if (list_empty(&q->done_list))
>
next prev parent reply other threads:[~2014-09-15 11:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:23 [PATCH/RFC v2 0/2] vb2: Report POLLERR for fatal errors only Laurent Pinchart
2014-06-05 12:23 ` [PATCH/RFC v2 1/2] v4l: vb2: Don't return POLLERR during transient buffer underruns Laurent Pinchart
2014-06-06 5:15 ` Pawel Osciak
2014-06-06 9:50 ` Hans de Goede
2014-06-06 9:58 ` Hans Verkuil
2014-06-06 13:42 ` Laurent Pinchart
2014-09-15 11:14 ` Hans Verkuil [this message]
2014-09-15 12:02 ` Mauro Carvalho Chehab
2014-09-15 12:49 ` Laurent Pinchart
2014-09-15 12:56 ` Nicolas Dufresne
2014-09-15 13:55 ` Mauro Carvalho Chehab
2014-09-15 14:33 ` Nicolas Dufresne
2014-09-15 15:51 ` Mauro Carvalho Chehab
2014-09-16 10:29 ` Laurent Pinchart
2014-09-16 11:18 ` Hans Verkuil
2014-09-16 12:19 ` Laurent Pinchart
2014-06-05 12:23 ` [PATCH/RFC v2 2/2] v4l: vb2: Add fatal error condition flag Laurent Pinchart
2014-06-06 5:31 ` Pawel Osciak
2014-06-06 9:19 ` Laurent Pinchart
2014-06-06 9:31 ` Hans Verkuil
2014-06-06 9:46 ` Laurent Pinchart
2014-06-06 9:55 ` Hans Verkuil
2014-06-06 13:42 ` Laurent Pinchart
2014-06-06 13:45 ` Hans Verkuil
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=5416CA2B.1080004@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=hdegoede@redhat.com \
--cc=kyungmin.park@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=nicolas.dufresne@collabora.com \
--cc=pawel@osciak.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;
as well as URLs for NNTP newsgroup(s).