From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
Cc: Geert Uytterhoeven
<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux-sh list <linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Guennadi Liakhovetski
<g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>
Subject: Re: [PATCH 1/2] [RFC] spi: rspi: Handle dmaengine_prep_slave_sg() failures gracefully
Date: Fri, 11 Jul 2014 14:06:00 +0000 [thread overview]
Message-ID: <2693636.GN1F3EeRMO@avalon> (raw)
In-Reply-To: <CAMuHMdWw6BZn5HnvkxbEbbG+j52YcJhtxHoL=PVjUC0kag=-tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Geert,
On Friday 11 July 2014 15:58:07 Geert Uytterhoeven wrote:
> On Fri, Jul 11, 2014 at 3:27 PM, Laurent Pinchart wrote:
> >> >> AFAIK, descriptors are cleaned up automatically after use, and the
> >> >> only function that takes a dma_async_tx_descriptor is
> >> >> dmaengine_submit(). But indeed, if you don't use them, that doesn't
> >> >> happen. So calling dmaengine_terminate_all() seems appropriate to fix
> >> >> this.
> >> >>
> >> >> But, Documentation/dmaengine.txt says:
> >> >> desc = dmaengine_prep_slave_sg(chan, sgl, nr_sg, direction,
> >> >> flags);
> >> >>
> >> >> Once a descriptor has been obtained, the callback information can
> >> >> be added and the descriptor must then be submitted. Some DMA
> >> >> engine drivers may hold a spinlock between a successful preparation
> >> >> and submission so it is important that these two operations are
> >> >> closely paired.
> >> >>
> >> >> W.r.t. the spinlock, is it safe to call dmaengine_terminate_all() for
> >> >> a prepared but not submitted transfer?
> >> >> Is there another/better way?
> >> >
> >> > Basically, I have no idea. I'm pretty sure some drivers will support
> >> > it, others won't. Reading the code won't help much, as there's no
> >> > available information regarding what the expected behaviour is. Welcome
> >> > to the wonderful world of the undocumented DMA engine API :-)
> >>
> >> I did dive a bit into the code...
> >>
> >> 1. The spinlock comment seems to apply to INTEL_IOATDMA only.
> >>
> >> This driver doesn't implement dma_device.device_control(), so
> >> dmaengine_terminate_all() is a no-op there, and there doesn't seem to
> >> be a way to release a descriptor without submitting it first.
> >>
> >> 2. While I thought dmaengine_terminate_all() would release all
> >> descriptors on shdma, as it calls shdma_chan_ld_cleanup(), it only
> >> releases the descriptors that are at least in submitted state.
> >> Hence after a while, you get
> >>
> >> sh-dma-engine e6700020.dma-controller: No free link descriptor
> >> available
> >>
> >> Interestingly, this contradicts with the comment in
> >> shdma_free_chan_resources():
> >>
> >> /* Prepared and not submitted descriptors can still be on the
> >> queue */
> >> if (!list_empty(&schan->ld_queue))
> >> shdma_chan_ld_cleanup(schan, true);
> >>
> >> As dmaengine_submit() will not start the DMA operation, but merely add it
> >> to the pending queue (starting needs a call to
> >> dma_async_issue_pending()),it seems the right solution is to continue
> >> submitting the request for which preparation succeeded, and then aborting
> >> everything using dmaengine_terminate_all().
> >>
> >> Note that this also means that if submitting the RX request failed, you
> >> should still submit the TX request, as it has been prepared.
> >>
> >> Alternatively, you can interleave prep and submit for both channels,
> >> which
> >> makes the error recovery code less convoluted.
> >
> > How about fixing the DMA API to allow cleaning up a prepared request
> > without submitting it ?
>
> That's another option. But that would require updating all drivers.
Isn't it worth it if the API can be made simpler and more robust ? Even though
the number of drivers to change isn't small, the update could be rolled out
gradually.
I wonder what the rationale for the DMA engine cookie system was, and if it
still applies today. Wouldn't it be easier if slave drivers stored pointers to
the async_tx descriptors instead of storing cookies, and used them in place of
cookies through the whole API ? Slaves would then need to release the
descriptors explicitly, which could occur at any point of time if they were
reference counted.
> Note that only ioat, iop-adma, mv_xor, and ppc4xx do not implement
> .device_control() and/or DMA_TERMINATE_ALL.
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
To: Geert Uytterhoeven <geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
Cc: Geert Uytterhoeven
<geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>,
Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
linux-spi <linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux-sh list <linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Guennadi Liakhovetski
<g.liakhovetski-Mmb7MZpHnFY@public.gmane.org>
Subject: Re: [PATCH 1/2] [RFC] spi: rspi: Handle dmaengine_prep_slave_sg() failures gracefully
Date: Fri, 11 Jul 2014 16:06 +0200 [thread overview]
Message-ID: <2693636.GN1F3EeRMO@avalon> (raw)
In-Reply-To: <CAMuHMdWw6BZn5HnvkxbEbbG+j52YcJhtxHoL=PVjUC0kag=-tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Geert,
On Friday 11 July 2014 15:58:07 Geert Uytterhoeven wrote:
> On Fri, Jul 11, 2014 at 3:27 PM, Laurent Pinchart wrote:
> >> >> AFAIK, descriptors are cleaned up automatically after use, and the
> >> >> only function that takes a dma_async_tx_descriptor is
> >> >> dmaengine_submit(). But indeed, if you don't use them, that doesn't
> >> >> happen. So calling dmaengine_terminate_all() seems appropriate to fix
> >> >> this.
> >> >>
> >> >> But, Documentation/dmaengine.txt says:
> >> >> desc = dmaengine_prep_slave_sg(chan, sgl, nr_sg, direction,
> >> >> flags);
> >> >>
> >> >> Once a descriptor has been obtained, the callback information can
> >> >> be added and the descriptor must then be submitted. Some DMA
> >> >> engine drivers may hold a spinlock between a successful preparation
> >> >> and submission so it is important that these two operations are
> >> >> closely paired.
> >> >>
> >> >> W.r.t. the spinlock, is it safe to call dmaengine_terminate_all() for
> >> >> a prepared but not submitted transfer?
> >> >> Is there another/better way?
> >> >
> >> > Basically, I have no idea. I'm pretty sure some drivers will support
> >> > it, others won't. Reading the code won't help much, as there's no
> >> > available information regarding what the expected behaviour is. Welcome
> >> > to the wonderful world of the undocumented DMA engine API :-)
> >>
> >> I did dive a bit into the code...
> >>
> >> 1. The spinlock comment seems to apply to INTEL_IOATDMA only.
> >>
> >> This driver doesn't implement dma_device.device_control(), so
> >> dmaengine_terminate_all() is a no-op there, and there doesn't seem to
> >> be a way to release a descriptor without submitting it first.
> >>
> >> 2. While I thought dmaengine_terminate_all() would release all
> >> descriptors on shdma, as it calls shdma_chan_ld_cleanup(), it only
> >> releases the descriptors that are at least in submitted state.
> >> Hence after a while, you get
> >>
> >> sh-dma-engine e6700020.dma-controller: No free link descriptor
> >> available
> >>
> >> Interestingly, this contradicts with the comment in
> >> shdma_free_chan_resources():
> >>
> >> /* Prepared and not submitted descriptors can still be on the
> >> queue */
> >> if (!list_empty(&schan->ld_queue))
> >> shdma_chan_ld_cleanup(schan, true);
> >>
> >> As dmaengine_submit() will not start the DMA operation, but merely add it
> >> to the pending queue (starting needs a call to
> >> dma_async_issue_pending()),it seems the right solution is to continue
> >> submitting the request for which preparation succeeded, and then aborting
> >> everything using dmaengine_terminate_all().
> >>
> >> Note that this also means that if submitting the RX request failed, you
> >> should still submit the TX request, as it has been prepared.
> >>
> >> Alternatively, you can interleave prep and submit for both channels,
> >> which
> >> makes the error recovery code less convoluted.
> >
> > How about fixing the DMA API to allow cleaning up a prepared request
> > without submitting it ?
>
> That's another option. But that would require updating all drivers.
Isn't it worth it if the API can be made simpler and more robust ? Even though
the number of drivers to change isn't small, the update could be rolled out
gradually.
I wonder what the rationale for the DMA engine cookie system was, and if it
still applies today. Wouldn't it be easier if slave drivers stored pointers to
the async_tx descriptors instead of storing cookies, and used them in place of
cookies through the whole API ? Slaves would then need to release the
descriptors explicitly, which could occur at any point of time if they were
reference counted.
> Note that only ioat, iop-adma, mv_xor, and ppc4xx do not implement
> .device_control() and/or DMA_TERMINATE_ALL.
--
Regards,
Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-11 14:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 10:26 [PATCH 1/2] [RFC] spi: rspi: Handle dmaengine_prep_slave_sg() failures gracefully Geert Uytterhoeven
2014-07-09 10:26 ` Geert Uytterhoeven
[not found] ` <1404901583-31366-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2014-07-09 10:26 ` [PATCH 2/2] [RFC] spi: sh-msiof: Handle dmaengine_prep_slave_single() " Geert Uytterhoeven
2014-07-09 10:26 ` Geert Uytterhoeven
[not found] ` <1404901583-31366-2-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2014-07-10 11:09 ` Laurent Pinchart
2014-07-10 11:09 ` Laurent Pinchart
2014-07-10 11:05 ` [PATCH 1/2] [RFC] spi: rspi: Handle dmaengine_prep_slave_sg() " Laurent Pinchart
2014-07-10 11:05 ` Laurent Pinchart
2014-07-10 11:36 ` Geert Uytterhoeven
2014-07-10 11:36 ` Geert Uytterhoeven
2014-07-16 21:42 ` Mark Brown
2014-07-16 21:42 ` Mark Brown
2014-07-10 11:08 ` Laurent Pinchart
2014-07-10 11:08 ` Laurent Pinchart
2014-07-10 11:55 ` Geert Uytterhoeven
2014-07-10 11:55 ` Geert Uytterhoeven
[not found] ` <CAMuHMdXj=Y0w39iyY9GPjUJPXC7UgPyeqk7+G+zZeAvGoE1fGg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-10 23:47 ` Laurent Pinchart
2014-07-10 23:47 ` Laurent Pinchart
2014-07-11 13:22 ` Geert Uytterhoeven
2014-07-11 13:22 ` Geert Uytterhoeven
2014-07-11 13:27 ` Laurent Pinchart
2014-07-11 13:27 ` Laurent Pinchart
2014-07-11 13:58 ` Geert Uytterhoeven
2014-07-11 13:58 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWw6BZn5HnvkxbEbbG+j52YcJhtxHoL=PVjUC0kag=-tw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-11 14:06 ` Laurent Pinchart [this message]
2014-07-11 14:06 ` Laurent Pinchart
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=2693636.GN1F3EeRMO@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=dmaengine-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=g.liakhovetski-Mmb7MZpHnFY@public.gmane.org \
--cc=geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org \
--cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
--cc=linux-sh-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.