All of lore.kernel.org
 help / color / mirror / Atom feed
* V4L2 logging for multiple streams
@ 2021-01-16  4:33 Fritz Koenig
  2021-01-20 10:07 ` Kieran Bingham
  2021-01-28 21:44 ` Nicolas Dufresne
  0 siblings, 2 replies; 5+ messages in thread
From: Fritz Koenig @ 2021-01-16  4:33 UTC (permalink / raw)
  To: Linux Media Mailing List

Hi,

I'm trying to sort some issues with regards to decoding multiple
streams at once.  Logging can be helpful with messages like this:

[105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane

but when I have:

[105188.498697] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
[105188.498715] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
[105188.499116] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
[105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
[105188.500467] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
[105188.500611] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
[105188.501879] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
[105188.502276] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
[105188.502331] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane

I can't tell which stream VIDIOC_STREAMOFF is associated with.  Is
there a logging option that I'm missing that would help indicate which
stream that ioctl is associated with.

Thanks.

-Fritz

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: V4L2 logging for multiple streams
  2021-01-16  4:33 V4L2 logging for multiple streams Fritz Koenig
@ 2021-01-20 10:07 ` Kieran Bingham
  2021-02-06  0:59   ` Fritz Koenig
  2021-01-28 21:44 ` Nicolas Dufresne
  1 sibling, 1 reply; 5+ messages in thread
From: Kieran Bingham @ 2021-01-20 10:07 UTC (permalink / raw)
  To: Fritz Koenig, Linux Media Mailing List

Hi Fritz,

On 16/01/2021 04:33, Fritz Koenig wrote:
> Hi,
> 
> I'm trying to sort some issues with regards to decoding multiple
> streams at once.  Logging can be helpful with messages like this:
> 
> [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> 

The type is telling you useful information there, is that what you are
after?

> but when I have:
> 
> [105188.498697] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> [105188.498715] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> [105188.499116] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> [105188.500467] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> [105188.500611] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> [105188.501879] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> [105188.502276] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> [105188.502331] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> 
> I can't tell which stream VIDIOC_STREAMOFF is associated with.  Is
> there a logging option that I'm missing that would help indicate which
> stream that ioctl is associated with.

The type expresses if it's from an output queue or a capture queue.

  type=vid-out-mplane : Output queue
  type=vid-cap-mplane : Capture queue


That's not so helpful/useful on the UNSUBSCRIBE_EVENT lines though, but
your specific request is regarding STREAMOFF.

I hope that helps you read the logs a little.

--
Kieran

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: V4L2 logging for multiple streams
  2021-01-16  4:33 V4L2 logging for multiple streams Fritz Koenig
  2021-01-20 10:07 ` Kieran Bingham
@ 2021-01-28 21:44 ` Nicolas Dufresne
  2021-02-01 18:53   ` Fritz Koenig
  1 sibling, 1 reply; 5+ messages in thread
From: Nicolas Dufresne @ 2021-01-28 21:44 UTC (permalink / raw)
  To: Fritz Koenig, Linux Media Mailing List

Le vendredi 15 janvier 2021 à 20:33 -0800, Fritz Koenig a écrit :
> Hi,
> 
> I'm trying to sort some issues with regards to decoding multiple
> streams at once.  Logging can be helpful with messages like this:
> 
> [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> 
> but when I have:
> 
> [105188.498697] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> [105188.498715] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> [105188.499116] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> [105188.500467] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> [105188.500611] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> [105188.501879] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> [105188.502276] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> [105188.502331] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> 
> I can't tell which stream VIDIOC_STREAMOFF is associated with.  Is
> there a logging option that I'm missing that would help indicate which
> stream that ioctl is associated with.

I suppose this is m2m driver ? I think it would be nice to trace some instance
ID, otherwise indeed, if you have two stream on the same m2m device node, the
traces get confused.

> 
> Thanks.
> 
> -Fritz



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: V4L2 logging for multiple streams
  2021-01-28 21:44 ` Nicolas Dufresne
@ 2021-02-01 18:53   ` Fritz Koenig
  0 siblings, 0 replies; 5+ messages in thread
From: Fritz Koenig @ 2021-02-01 18:53 UTC (permalink / raw)
  To: Nicolas Dufresne; +Cc: Linux Media Mailing List

On Thu, Jan 28, 2021 at 1:45 PM Nicolas Dufresne <nicolas@ndufresne.ca> wrote:
>
> Le vendredi 15 janvier 2021 à 20:33 -0800, Fritz Koenig a écrit :
> > Hi,
> >
> > I'm trying to sort some issues with regards to decoding multiple
> > streams at once.  Logging can be helpful with messages like this:
> >
> > [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> >
> > but when I have:
> >
> > [105188.498697] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> > [105188.498715] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> > [105188.499116] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> > [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> > [105188.500467] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> > [105188.500611] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> > [105188.501879] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> > [105188.502276] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> > [105188.502331] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> >
> > I can't tell which stream VIDIOC_STREAMOFF is associated with.  Is
> > there a logging option that I'm missing that would help indicate which
> > stream that ioctl is associated with.
>
> I suppose this is m2m driver ? I think it would be nice to trace some instance
> ID, otherwise indeed, if you have two stream on the same m2m device node, the
> traces get confused.
>

Yes, m2m.  Instance doesn't seem to be a concept at that level.  The
driver itself holds an idea of instances (at least on venus).  I was
able to add debugging to trace instances in vdec.c, but I don't see a
generic way to add it.

-Fritz

>
> >
> > Thanks.
> >
> > -Fritz
>
>

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: V4L2 logging for multiple streams
  2021-01-20 10:07 ` Kieran Bingham
@ 2021-02-06  0:59   ` Fritz Koenig
  0 siblings, 0 replies; 5+ messages in thread
From: Fritz Koenig @ 2021-02-06  0:59 UTC (permalink / raw)
  To: kieran.bingham+renesas; +Cc: Linux Media Mailing List

On Wed, Jan 20, 2021 at 2:07 AM Kieran Bingham
<kieran.bingham+renesas@ideasonboard.com> wrote:
>
> Hi Fritz,
>
> On 16/01/2021 04:33, Fritz Koenig wrote:
> > Hi,
> >
> > I'm trying to sort some issues with regards to decoding multiple
> > streams at once.  Logging can be helpful with messages like this:
> >
> > [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> >
>
> The type is telling you useful information there, is that what you are
> after?
>

Sorry, I don't think I explained it well.  Here I'm decoding 3
different streams at the same time, say 1080x720, 640x480, and
320x240.  Nothing that denotes which is which is present in this level
of logging.  I understand the distinction between the CAPTURE and
OUTPUT queues.  I have found that at least for the venus driver, that
information is not exported anywhere.

This was also meant as a more general question of how to separate the
debugging information.  I've done that by creating trampoline
functions that print out the context information before calling
v4l2_m2m_ioctl_streamon/v4l2_m2m_ioctl_streamoff etc.  But it's a
patch that I have to maintain locally.

-Fritz

> > but when I have:
> >
> > [105188.498697] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> > [105188.498715] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> > [105188.499116] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> > [105188.500450] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> > [105188.500467] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> > [105188.500611] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> > [105188.501879] video2: VIDIOC_UNSUBSCRIBE_EVENT: type=0x5, id=0x0, flags=0x0
> > [105188.502276] video2: VIDIOC_STREAMOFF: type=vid-out-mplane
> > [105188.502331] video2: VIDIOC_STREAMOFF: type=vid-cap-mplane
> >
> > I can't tell which stream VIDIOC_STREAMOFF is associated with.  Is
> > there a logging option that I'm missing that would help indicate which
> > stream that ioctl is associated with.
>
> The type expresses if it's from an output queue or a capture queue.
>
>   type=vid-out-mplane : Output queue
>   type=vid-cap-mplane : Capture queue
>
>
> That's not so helpful/useful on the UNSUBSCRIBE_EVENT lines though, but
> your specific request is regarding STREAMOFF.
>
> I hope that helps you read the logs a little.
>
> --
> Kieran

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-02-06  3:23 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-16  4:33 V4L2 logging for multiple streams Fritz Koenig
2021-01-20 10:07 ` Kieran Bingham
2021-02-06  0:59   ` Fritz Koenig
2021-01-28 21:44 ` Nicolas Dufresne
2021-02-01 18:53   ` Fritz Koenig

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.