From: Qiang Liu <hidden> Date: 2012-07-16 04:30:10
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma descriptor,
all descriptors will be released whatever is acked or no-acked by async_tx,
so there is a potential race condition when dma engine is uesd by others
clients (e.g. when enable NET_DMA to offload TCP).
In our case, a race condition which is raised when use both of talitos
and dmaengine to offload xor is because napi scheduler will sync all
pending requests in dma channels, it affects the process of raid operations
due to ack_tx is not checked in fsl dma. The no-acked descriptor is freed
which is submitted just now, as a dependent tx, this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
---
drivers/dma/fsldma.c | 378 +++++++++++++++++++++++++++++--------------------
drivers/dma/fsldma.h | 1 +
2 files changed, 225 insertions(+), 154 deletions(-)
@@ -400,6 +400,217 @@ out_splice:list_splice_tail_init(&desc->tx_list,&chan->ld_pending);}+/**+*fsl_chan_xfer_ld_queue-transferanypendingtransactions+*@chan:FreescaleDMAchannel+*+*HARDWARESTATE:idle+*LOCKING:mustholdchan->desc_lock+*/+staticvoidfsl_chan_xfer_ld_queue(structfsldma_chan*chan)+{+structfsl_desc_sw*desc;++/*+*Ifthelistofpendingdescriptorsisempty,thenwe+*don'tneedtodoanyworkatall+*/+if(list_empty(&chan->ld_pending)){+chan_dbg(chan,"no pending LDs\n");+return;+}++/*+*TheDMAcontrollerisnotidle,whichmeansthattheinterrupt+*handlerwillstartanyqueuedtransactionswhenitrunsafter+*thistransactionfinishes+*/+if(!chan->idle){+chan_dbg(chan,"DMA controller still busy\n");+return;+}++/*+*Iftherearesomelinkdescriptorswhichhavenotbeen+*transferred,weneedtostartthecontroller+*/++/*+*Moveallelementsfromthequeueofpendingtransactions+*ontothelistofrunningtransactions+*/+chan_dbg(chan,"idle, starting controller\n");+desc=list_first_entry(&chan->ld_pending,structfsl_desc_sw,node);+list_splice_tail_init(&chan->ld_pending,&chan->ld_running);++/*+*The85xxDMAcontrollerdoesn'tclearthechannelstartbit+*automaticallyattheendofatransfer.Thereforewemustclear+*itinsoftwarebeforestartingthetransfer.+*/+if((chan->feature&FSL_DMA_IP_MASK)==FSL_DMA_IP_85XX){+u32mode;++mode=DMA_IN(chan,&chan->regs->mr,32);+mode&=~FSL_DMA_MR_CS;+DMA_OUT(chan,&chan->regs->mr,mode,32);+}++/*+*Programthedescriptor'saddressintotheDMAcontroller,+*thenstarttheDMAtransaction+*/+set_cdar(chan,desc->async_tx.phys);+get_cdar(chan);++dma_start(chan);+chan->idle=false;+}++staticint+fsldma_clean_completed_descriptor(structfsldma_chan*chan)+{+structfsl_desc_sw*desc,*_desc;++/* Run the callback for each descriptor, in order */+list_for_each_entry_safe(desc,_desc,&chan->ld_completed,node){++if(async_tx_test_ack(&desc->async_tx)){+/* Remove from the list of transactions */+list_del(&desc->node);+#ifdef FSL_DMA_LD_DEBUG+chan_dbg(chan,"LD %p free\n",desc);+#endif+dma_pool_free(chan->desc_pool,desc,+desc->async_tx.phys);+}+}++return0;+}++/**+*fsldma_run_tx_complete_actions-cleanupandfreeasinglelinkdescriptor+*@chan:FreescaleDMAchannel+*@desc:descriptortocleanupandfree+*@cookie:FreescaleDMAtransactionidentifier+*+*ThisfunctionisusedonadescriptorwhichhasbeenexecutedbytheDMA+*controller.Itwillrunanycallbacks,submitanydependencies,andthen+*freethedescriptor.+*/+staticdma_cookie_tfsldma_run_tx_complete_actions(structfsl_desc_sw*desc,+structfsldma_chan*chan,dma_cookie_tcookie)+{+structdma_async_tx_descriptor*txd=&desc->async_tx;+structdevice*dev=chan->common.device->dev;+dma_addr_tsrc=get_desc_src(chan,desc);+dma_addr_tdst=get_desc_dst(chan,desc);+u32len=get_desc_cnt(chan,desc);++BUG_ON(txd->cookie<0);++if(txd->cookie>0){+cookie=txd->cookie;++/* Run the link descriptor callback function */+if(txd->callback){+#ifdef FSL_DMA_LD_DEBUG+chan_dbg(chan,"LD %p callback\n",desc);+#endif+txd->callback(txd->callback_param);+}++/* Unmap the dst buffer, if requested */+if(!(txd->flags&DMA_COMPL_SKIP_DEST_UNMAP)){+if(txd->flags&DMA_COMPL_DEST_UNMAP_SINGLE)+dma_unmap_single(dev,dst,len,DMA_FROM_DEVICE);+else+dma_unmap_page(dev,dst,len,DMA_FROM_DEVICE);+}++/* Unmap the src buffer, if requested */+if(!(txd->flags&DMA_COMPL_SKIP_SRC_UNMAP)){+if(txd->flags&DMA_COMPL_SRC_UNMAP_SINGLE)+dma_unmap_single(dev,src,len,DMA_TO_DEVICE);+else+dma_unmap_page(dev,src,len,DMA_TO_DEVICE);+}+}++/* Run any dependencies */+dma_run_dependencies(txd);++returncookie;+}++staticint+fsldma_clean_running_descriptor(structfsl_desc_sw*desc,+structfsldma_chan*chan)+{+/* Remove from the list of transactions */+list_del(&desc->node);+/* the client is allowed to attach dependent operations+*until'ack'isset+*/+if(!async_tx_test_ack(&desc->async_tx)){+/* move this slot to the completed */+list_add_tail(&desc->node,&chan->ld_completed);+return0;+}++dma_pool_free(chan->desc_pool,desc,+desc->async_tx.phys);+return0;+}++staticvoidfsldma_cleanup_descriptor(structfsldma_chan*chan)+{+structfsl_desc_sw*desc,*_desc;+dma_cookie_tcookie=0;+dma_addr_tcurr_phys=get_cdar(chan);+intidle=dma_is_idle(chan);+intseen_current=0;++fsldma_clean_completed_descriptor(chan);++/* Run the callback for each descriptor, in order */+list_for_each_entry_safe(desc,_desc,&chan->ld_running,node){+/* do not advance past the current descriptor loaded into the+*hardwarechannel,subsequentdescriptorsareeitherin+*processorhavenotbeensubmitted+*/+if(seen_current)+break;++/* stop the search if we reach the current descriptor and the+*channelisbusy+*/+if(desc->async_tx.phys==curr_phys){+seen_current=1;+if(!idle)+break;+}++cookie=fsldma_run_tx_complete_actions(desc,chan,cookie);++if(fsldma_clean_running_descriptor(desc,chan))+break;++}++/*+*Startanypendingtransactionsautomatically+*+*Intheidealcase,wekeeptheDMAcontrollerbusywhilewego+*aheadandfreethedescriptorsbelow.+*/+fsl_chan_xfer_ld_queue(chan);++if(cookie>0)+chan->common.completed_cookie=cookie;+}+staticdma_cookie_tfsl_dma_tx_submit(structdma_async_tx_descriptor*tx){structfsldma_chan*chan=to_fsl_chan(tx->chan);
@@ -811,124 +1024,6 @@ static int fsl_dma_device_control(struct dma_chan *dchan,}/**-*fsldma_cleanup_descriptor-cleanupandfreeasinglelinkdescriptor-*@chan:FreescaleDMAchannel-*@desc:descriptortocleanupandfree-*-*ThisfunctionisusedonadescriptorwhichhasbeenexecutedbytheDMA-*controller.Itwillrunanycallbacks,submitanydependencies,andthen-*freethedescriptor.-*/-staticvoidfsldma_cleanup_descriptor(structfsldma_chan*chan,-structfsl_desc_sw*desc)-{-structdma_async_tx_descriptor*txd=&desc->async_tx;-structdevice*dev=chan->common.device->dev;-dma_addr_tsrc=get_desc_src(chan,desc);-dma_addr_tdst=get_desc_dst(chan,desc);-u32len=get_desc_cnt(chan,desc);--/* Run the link descriptor callback function */-if(txd->callback){-#ifdef FSL_DMA_LD_DEBUG-chan_dbg(chan,"LD %p callback\n",desc);-#endif-txd->callback(txd->callback_param);-}--/* Run any dependencies */-dma_run_dependencies(txd);--/* Unmap the dst buffer, if requested */-if(!(txd->flags&DMA_COMPL_SKIP_DEST_UNMAP)){-if(txd->flags&DMA_COMPL_DEST_UNMAP_SINGLE)-dma_unmap_single(dev,dst,len,DMA_FROM_DEVICE);-else-dma_unmap_page(dev,dst,len,DMA_FROM_DEVICE);-}--/* Unmap the src buffer, if requested */-if(!(txd->flags&DMA_COMPL_SKIP_SRC_UNMAP)){-if(txd->flags&DMA_COMPL_SRC_UNMAP_SINGLE)-dma_unmap_single(dev,src,len,DMA_TO_DEVICE);-else-dma_unmap_page(dev,src,len,DMA_TO_DEVICE);-}--#ifdef FSL_DMA_LD_DEBUG-chan_dbg(chan,"LD %p free\n",desc);-#endif-dma_pool_free(chan->desc_pool,desc,txd->phys);-}--/**-*fsl_chan_xfer_ld_queue-transferanypendingtransactions-*@chan:FreescaleDMAchannel-*-*HARDWARESTATE:idle-*LOCKING:mustholdchan->desc_lock-*/-staticvoidfsl_chan_xfer_ld_queue(structfsldma_chan*chan)-{-structfsl_desc_sw*desc;--/*-*Ifthelistofpendingdescriptorsisempty,thenwe-*don'tneedtodoanyworkatall-*/-if(list_empty(&chan->ld_pending)){-chan_dbg(chan,"no pending LDs\n");-return;-}--/*-*TheDMAcontrollerisnotidle,whichmeansthattheinterrupt-*handlerwillstartanyqueuedtransactionswhenitrunsafter-*thistransactionfinishes-*/-if(!chan->idle){-chan_dbg(chan,"DMA controller still busy\n");-return;-}--/*-*Iftherearesomelinkdescriptorswhichhavenotbeen-*transferred,weneedtostartthecontroller-*/--/*-*Moveallelementsfromthequeueofpendingtransactions-*ontothelistofrunningtransactions-*/-chan_dbg(chan,"idle, starting controller\n");-desc=list_first_entry(&chan->ld_pending,structfsl_desc_sw,node);-list_splice_tail_init(&chan->ld_pending,&chan->ld_running);--/*-*The85xxDMAcontrollerdoesn'tclearthechannelstartbit-*automaticallyattheendofatransfer.Thereforewemustclear-*itinsoftwarebeforestartingthetransfer.-*/-if((chan->feature&FSL_DMA_IP_MASK)==FSL_DMA_IP_85XX){-u32mode;--mode=DMA_IN(chan,&chan->regs->mr,32);-mode&=~FSL_DMA_MR_CS;-DMA_OUT(chan,&chan->regs->mr,mode,32);-}--/*-*Programthedescriptor'saddressintotheDMAcontroller,-*thenstarttheDMAtransaction-*/-set_cdar(chan,desc->async_tx.phys);-get_cdar(chan);--dma_start(chan);-chan->idle=false;-}--/***fsl_dma_memcpy_issue_pending-IssuetheDMAstartcommand*@chan:FreescaleDMAchannel*/
@@ -1035,53 +1136,21 @@ static irqreturn_t fsldma_chan_irq(int irq, void *data)staticvoiddma_do_tasklet(unsignedlongdata){structfsldma_chan*chan=(structfsldma_chan*)data;-structfsl_desc_sw*desc,*_desc;-LIST_HEAD(ld_cleanup);unsignedlongflags;chan_dbg(chan,"tasklet entry\n");spin_lock_irqsave(&chan->desc_lock,flags);-/* update the cookie if we have some descriptors to cleanup */-if(!list_empty(&chan->ld_running)){-dma_cookie_tcookie;--desc=to_fsl_desc(chan->ld_running.prev);-cookie=desc->async_tx.cookie;-dma_cookie_complete(&desc->async_tx);--chan_dbg(chan,"completed_cookie=%d\n",cookie);-}--/*-*movethedescriptorstoatemporarylistsowecandropthelock-*duringtheentirecleanupoperation-*/-list_splice_tail_init(&chan->ld_running,&ld_cleanup);+/* Run all cleanup for this descriptor */+fsldma_cleanup_descriptor(chan);/* the hardware is now idle and ready for more */chan->idle=true;-/*-*Startanypendingtransactionsautomatically-*-*Intheidealcase,wekeeptheDMAcontrollerbusywhilewego-*aheadandfreethedescriptorsbelow.-*/fsl_chan_xfer_ld_queue(chan);spin_unlock_irqrestore(&chan->desc_lock,flags);-/* Run the callback for each descriptor, in order */-list_for_each_entry_safe(desc,_desc,&ld_cleanup,node){--/* Remove from the list of transactions */-list_del(&desc->node);--/* Run all cleanup for this descriptor */-fsldma_cleanup_descriptor(chan,desc);-}-chan_dbg(chan,"tasklet exit\n");}
@@ -1262,6 +1331,7 @@ static int __devinit fsl_dma_chan_probe(struct fsldma_device *fdev,spin_lock_init(&chan->desc_lock);INIT_LIST_HEAD(&chan->ld_pending);INIT_LIST_HEAD(&chan->ld_running);+INIT_LIST_HEAD(&chan->ld_completed);chan->idle=true;chan->common.device=&fdev->common;
From: Ira W. Snyder <hidden> Date: 2012-07-16 20:01:29
On Mon, Jul 16, 2012 at 12:08:29PM +0800, Qiang Liu wrote:
quoted hunk
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma descriptor,
all descriptors will be released whatever is acked or no-acked by async_tx,
so there is a potential race condition when dma engine is uesd by others
clients (e.g. when enable NET_DMA to offload TCP).
In our case, a race condition which is raised when use both of talitos
and dmaengine to offload xor is because napi scheduler will sync all
pending requests in dma channels, it affects the process of raid operations
due to ack_tx is not checked in fsl dma. The no-acked descriptor is freed
which is submitted just now, as a dependent tx, this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
---
drivers/dma/fsldma.c | 378 +++++++++++++++++++++++++++++--------------------
drivers/dma/fsldma.h | 1 +
2 files changed, 225 insertions(+), 154 deletions(-)
Please add a note about the locking requirements here, and for the other
new functions you've added.
You call this function from two places:
1) fsldma_cleanup_descriptor() - called with mod->desc_lock held
2) fsl_tx_status() - WITHOUT mod->desc_lock held
One of them is definitely wrong, and I'd bet that it is #2. You're
modifying ld_completed without a lock.
+static int
+fsldma_clean_completed_descriptor(struct fsldma_chan *chan)
+{
+ struct fsl_desc_sw *desc, *_desc;
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_completed, node) {
+
+ if (async_tx_test_ack(&desc->async_tx)) {
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p free\n", desc);
+#endif
+ dma_pool_free(chan->desc_pool, desc,
+ desc->async_tx.phys);
+ }
+ }
+
+ return 0;
+}
+
+/**
+ * fsldma_run_tx_complete_actions - cleanup and free a single link descriptor
+ * @chan: Freescale DMA channel
+ * @desc: descriptor to cleanup and free
+ * @cookie: Freescale DMA transaction identifier
+ *
+ * This function is used on a descriptor which has been executed by the DMA
+ * controller. It will run any callbacks, submit any dependencies, and then
+ * free the descriptor.
+ */
+static dma_cookie_t fsldma_run_tx_complete_actions(struct fsl_desc_sw *desc,
+ struct fsldma_chan *chan, dma_cookie_t cookie)
+{
+ struct dma_async_tx_descriptor *txd = &desc->async_tx;
+ struct device *dev = chan->common.device->dev;
+ dma_addr_t src = get_desc_src(chan, desc);
+ dma_addr_t dst = get_desc_dst(chan, desc);
+ u32 len = get_desc_cnt(chan, desc);
+
+ BUG_ON(txd->cookie < 0);
+
+ if (txd->cookie > 0) {
+ cookie = txd->cookie;
+
+ /* Run the link descriptor callback function */
+ if (txd->callback) {
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p callback\n", desc);
+#endif
+ txd->callback(txd->callback_param);
+ }
+
+ /* Unmap the dst buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
+ if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
+ dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
+ else
+ dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
+ }
+
+ /* Unmap the src buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
+ if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
+ dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
+ else
+ dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
+ }
+ }
+
+ /* Run any dependencies */
+ dma_run_dependencies(txd);
+
+ return cookie;
+}
+
+static int
+fsldma_clean_running_descriptor(struct fsl_desc_sw *desc,
+ struct fsldma_chan *chan)
+{
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+ /* the client is allowed to attach dependent operations
+ * until 'ack' is set
+ */
This comment is does not follow the coding style. It should be:
/*
* the client is allowed to attech dependent operations
* until 'ack' is set
*/
+ if (!async_tx_test_ack(&desc->async_tx)) {
+ /* move this slot to the completed */
Perhaps a better comment would be:
Move this descriptor to the list of descriptors which is complete, but
still awaiting the 'ack' bit to be set.
This should all be on one line. It is less than 80 characters wide.
+ return 0;
+}
+
Locking notes please.
+static void fsldma_cleanup_descriptor(struct fsldma_chan *chan)
+{
+ struct fsl_desc_sw *desc, *_desc;
+ dma_cookie_t cookie = 0;
+ dma_addr_t curr_phys = get_cdar(chan);
+ int idle = dma_is_idle(chan);
+ int seen_current = 0;
+
+ fsldma_clean_completed_descriptor(chan);
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_running, node) {
+ /* do not advance past the current descriptor loaded into the
+ * hardware channel, subsequent descriptors are either in
+ * process or have not been submitted
+ */
Coding style.
+ if (seen_current)
+ break;
+
+ /* stop the search if we reach the current descriptor and the
+ * channel is busy
+ */
Coding style.
+ if (desc->async_tx.phys == curr_phys) {
+ seen_current = 1;
+ if (!idle)
+ break;
+ }
+
This trick where you try to look at the hardware state to determine how
much to clean up has been a source of headaches in the past versions of
this driver.
It is much easier to reason about the state of the hardware and avoid
race conditions if you complete entire blocks of descriptors after the
hardware interrupts you to tell you it is finished.
This is the philosophy employed by the driver before your modifications:
ld_pending: a block of descriptors which is ready to run as soon as the
hardware becomes idle.
ld_running: a block of descriptors which is being executed by the
hardware.
quoted hunk
+ cookie = fsldma_run_tx_complete_actions(desc, chan, cookie);
+
+ if (fsldma_clean_running_descriptor(desc, chan))
+ break;
+
+ }
+
+ /*
+ * Start any pending transactions automatically
+ *
+ * In the ideal case, we keep the DMA controller busy while we go
+ * ahead and free the descriptors below.
+ */
+ fsl_chan_xfer_ld_queue(chan);
+
+ if (cookie > 0)
+ chan->common.completed_cookie = cookie;
+}
+
static dma_cookie_t fsl_dma_tx_submit(struct dma_async_tx_descriptor *tx)
{
struct fsldma_chan *chan = to_fsl_chan(tx->chan);
@@ -811,124 +1024,6 @@ static int fsl_dma_device_control(struct dma_chan *dchan, } /**- * fsldma_cleanup_descriptor - cleanup and free a single link descriptor- * @chan: Freescale DMA channel- * @desc: descriptor to cleanup and free- *- * This function is used on a descriptor which has been executed by the DMA- * controller. It will run any callbacks, submit any dependencies, and then- * free the descriptor.- */-static void fsldma_cleanup_descriptor(struct fsldma_chan *chan,- struct fsl_desc_sw *desc)-{- struct dma_async_tx_descriptor *txd = &desc->async_tx;- struct device *dev = chan->common.device->dev;- dma_addr_t src = get_desc_src(chan, desc);- dma_addr_t dst = get_desc_dst(chan, desc);- u32 len = get_desc_cnt(chan, desc);-- /* Run the link descriptor callback function */- if (txd->callback) {-#ifdef FSL_DMA_LD_DEBUG- chan_dbg(chan, "LD %p callback\n", desc);-#endif- txd->callback(txd->callback_param);- }-- /* Run any dependencies */- dma_run_dependencies(txd);-- /* Unmap the dst buffer, if requested */- if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {- if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)- dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);- else- dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);- }-- /* Unmap the src buffer, if requested */- if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {- if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)- dma_unmap_single(dev, src, len, DMA_TO_DEVICE);- else- dma_unmap_page(dev, src, len, DMA_TO_DEVICE);- }--#ifdef FSL_DMA_LD_DEBUG- chan_dbg(chan, "LD %p free\n", desc);-#endif- dma_pool_free(chan->desc_pool, desc, txd->phys);-}--/**- * fsl_chan_xfer_ld_queue - transfer any pending transactions- * @chan : Freescale DMA channel- *- * HARDWARE STATE: idle- * LOCKING: must hold chan->desc_lock- */-static void fsl_chan_xfer_ld_queue(struct fsldma_chan *chan)-{- struct fsl_desc_sw *desc;-- /*- * If the list of pending descriptors is empty, then we- * don't need to do any work at all- */- if (list_empty(&chan->ld_pending)) {- chan_dbg(chan, "no pending LDs\n");- return;- }-- /*- * The DMA controller is not idle, which means that the interrupt- * handler will start any queued transactions when it runs after- * this transaction finishes- */- if (!chan->idle) {- chan_dbg(chan, "DMA controller still busy\n");- return;- }-- /*- * If there are some link descriptors which have not been- * transferred, we need to start the controller- */-- /*- * Move all elements from the queue of pending transactions- * onto the list of running transactions- */- chan_dbg(chan, "idle, starting controller\n");- desc = list_first_entry(&chan->ld_pending, struct fsl_desc_sw, node);- list_splice_tail_init(&chan->ld_pending, &chan->ld_running);-- /*- * The 85xx DMA controller doesn't clear the channel start bit- * automatically at the end of a transfer. Therefore we must clear- * it in software before starting the transfer.- */- if ((chan->feature & FSL_DMA_IP_MASK) == FSL_DMA_IP_85XX) {- u32 mode;-- mode = DMA_IN(chan, &chan->regs->mr, 32);- mode &= ~FSL_DMA_MR_CS;- DMA_OUT(chan, &chan->regs->mr, mode, 32);- }-- /*- * Program the descriptor's address into the DMA controller,- * then start the DMA transaction- */- set_cdar(chan, desc->async_tx.phys);- get_cdar(chan);-- dma_start(chan);- chan->idle = false;-}--/** * fsl_dma_memcpy_issue_pending - Issue the DMA start command * @chan : Freescale DMA channel */
You've made status from a very quick operation (compare two cookies)
into a potentially long running operation. It may now run callbacks,
unmap pages, etc.
I note that Documentation/crypto/async-tx-api.txt section 3.6
"Constraints" does say that async_*() functions cannot be called from
IRQ context. However, the DMAEngine API itself does not have anything to
say about IRQ context.
I expect fsl_tx_status() to be quick, and not potentially call other
arbitrary code.
Is it possible to leave this function unchanged?
Also note that if you leave this function unchanged, the locking error
pointed out above (fsldma_clean_completed_descriptor() is not called
with the lock held) goes away.
@@ -1035,53 +1136,21 @@ static irqreturn_t fsldma_chan_irq(int irq, void *data) static void dma_do_tasklet(unsigned long data) { struct fsldma_chan *chan = (struct fsldma_chan *)data;- struct fsl_desc_sw *desc, *_desc;- LIST_HEAD(ld_cleanup); unsigned long flags; chan_dbg(chan, "tasklet entry\n"); spin_lock_irqsave(&chan->desc_lock, flags);- /* update the cookie if we have some descriptors to cleanup */- if (!list_empty(&chan->ld_running)) {- dma_cookie_t cookie;-- desc = to_fsl_desc(chan->ld_running.prev);- cookie = desc->async_tx.cookie;- dma_cookie_complete(&desc->async_tx);-- chan_dbg(chan, "completed_cookie=%d\n", cookie);- }-- /*- * move the descriptors to a temporary list so we can drop the lock- * during the entire cleanup operation- */- list_splice_tail_init(&chan->ld_running, &ld_cleanup);+ /* Run all cleanup for this descriptor */+ fsldma_cleanup_descriptor(chan); /* the hardware is now idle and ready for more */ chan->idle = true;- /*- * Start any pending transactions automatically- *- * In the ideal case, we keep the DMA controller busy while we go- * ahead and free the descriptors below.- */ fsl_chan_xfer_ld_queue(chan); spin_unlock_irqrestore(&chan->desc_lock, flags);- /* Run the callback for each descriptor, in order */- list_for_each_entry_safe(desc, _desc, &ld_cleanup, node) {-- /* Remove from the list of transactions */- list_del(&desc->node);-- /* Run all cleanup for this descriptor */- fsldma_cleanup_descriptor(chan, desc);- }- chan_dbg(chan, "tasklet exit\n"); }
On Mon, Jul 16, 2012 at 12:08 PM, Qiang Liu [off-list ref] wrote:
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma descriptor,
all descriptors will be released whatever is acked or no-acked by async_tx,
so there is a potential race condition when dma engine is uesd by others
clients (e.g. when enable NET_DMA to offload TCP).
In our case, a race condition which is raised when use both of talitos
and dmaengine to offload xor is because napi scheduler will sync all
pending requests in dma channels, it affects the process of raid operations
due to ack_tx is not checked in fsl dma. The no-acked descriptor is freed
which is submitted just now, as a dependent tx, this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
Also separate the function ordering change and real code change into
different patches when you work on the next patch set.
- Leo
From: Liu Qiang-B32616 <hidden> Date: 2012-07-17 07:06:40
-----Original Message-----
From: Ira W. Snyder [mailto:iws@ovro.caltech.edu]
Sent: Tuesday, July 17, 2012 4:01 AM
To: Liu Qiang-B32616
Cc: linux-crypto@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Phillips
Kim-R1AAHA; herbert@gondor.hengli.com.au; davem@davemloft.net; Dan
Williams; Vinod Koul; Li Yang-R58472
Subject: Re: [PATCH v3 3/4] fsl-dma: change release process of dma
descriptor for supporting async_tx
=20
On Mon, Jul 16, 2012 at 12:08:29PM +0800, Qiang Liu wrote:
quoted
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma
descriptor, all descriptors will be released whatever is acked or
no-acked by async_tx, so there is a potential race condition when dma
engine is uesd by others clients (e.g. when enable NET_DMA to offload
TCP).
quoted
In our case, a race condition which is raised when use both of talitos
and dmaengine to offload xor is because napi scheduler will sync all
pending requests in dma channels, it affects the process of raid
operations due to ack_tx is not checked in fsl dma. The no-acked
descriptor is freed which is submitted just now, as a dependent tx,
this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
---
drivers/dma/fsldma.c | 378 +++++++++++++++++++++++++++++-------------
+ list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
+
+ /*
+ * The 85xx DMA controller doesn't clear the channel start bit
+ * automatically at the end of a transfer. Therefore we must clear
+ * it in software before starting the transfer.
+ */
+ if ((chan->feature & FSL_DMA_IP_MASK) =3D=3D FSL_DMA_IP_85XX) {
+ u32 mode;
+
+ mode =3D DMA_IN(chan, &chan->regs->mr, 32);
+ mode &=3D ~FSL_DMA_MR_CS;
+ DMA_OUT(chan, &chan->regs->mr, mode, 32);
+ }
+
+ /*
+ * Program the descriptor's address into the DMA controller,
+ * then start the DMA transaction
+ */
+ set_cdar(chan, desc->async_tx.phys);
+ get_cdar(chan);
+
+ dma_start(chan);
+ chan->idle =3D false;
+}
+
=20
Please add a note about the locking requirements here, and for the other
new functions you've added.
=20
You call this function from two places:
=20
1) fsldma_cleanup_descriptor() - called with mod->desc_lock held
2) fsl_tx_status() - WITHOUT mod->desc_lock held
=20
One of them is definitely wrong, and I'd bet that it is #2. You're
modifying ld_completed without a lock.
Yes, My bad, I will correct it.
=20
quoted
+static int
+fsldma_clean_completed_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_completed, node) {
+
+ if (async_tx_test_ack(&desc->async_tx)) {
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p free\n", desc); #endif
+ dma_pool_free(chan->desc_pool, desc,
+ desc->async_tx.phys);
+ }
+ }
+
+ return 0;
+}
+
+/**
+ * fsldma_run_tx_complete_actions - cleanup and free a single link
+descriptor
+ * @chan: Freescale DMA channel
+ * @desc: descriptor to cleanup and free
+ * @cookie: Freescale DMA transaction identifier
+ *
+ * This function is used on a descriptor which has been executed by
+the DMA
+ * controller. It will run any callbacks, submit any dependencies,
+and then
+ * free the descriptor.
+ */
+static dma_cookie_t fsldma_run_tx_complete_actions(struct fsl_desc_sw
*desc,
quoted
+ struct fsldma_chan *chan, dma_cookie_t cookie) {
+ struct dma_async_tx_descriptor *txd =3D &desc->async_tx;
+ struct device *dev =3D chan->common.device->dev;
+ dma_addr_t src =3D get_desc_src(chan, desc);
+ dma_addr_t dst =3D get_desc_dst(chan, desc);
+ u32 len =3D get_desc_cnt(chan, desc);
+
+ BUG_ON(txd->cookie < 0);
+
+ if (txd->cookie > 0) {
+ cookie =3D txd->cookie;
+
+ /* Run the link descriptor callback function */
+ if (txd->callback) {
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p callback\n", desc); #endif
+ txd->callback(txd->callback_param);
+ }
+
+ /* Unmap the dst buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
+ if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
+ dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
+ else
+ dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
+ }
+
+ /* Unmap the src buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
+ if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
+ dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
+ else
+ dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
+ }
+ }
+
+ /* Run any dependencies */
+ dma_run_dependencies(txd);
+
+ return cookie;
+}
+
+static int
+fsldma_clean_running_descriptor(struct fsl_desc_sw *desc,
+ struct fsldma_chan *chan)
+{
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+ /* the client is allowed to attach dependent operations
+ * until 'ack' is set
+ */
=20
This comment is does not follow the coding style. It should be:
=20
/*
* the client is allowed to attech dependent operations
* until 'ack' is set
*/
Fine, I will correct it in v4. Include another 2 places related to coding s=
tyle.
Thanks.
=20
quoted
+ if (!async_tx_test_ack(&desc->async_tx)) {
+ /* move this slot to the completed */
=20
Perhaps a better comment would be:
=20
Move this descriptor to the list of descriptors which is complete, but
still awaiting the 'ack' bit to be set.
=20
This should all be on one line. It is less than 80 characters wide.
=20
Accept.
quoted
+ return 0;
+}
+
=20
Locking notes please.
I will add it in v4, please check. Thanks.
=20
quoted
+static void fsldma_cleanup_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+ dma_cookie_t cookie =3D 0;
+ dma_addr_t curr_phys =3D get_cdar(chan);
+ int idle =3D dma_is_idle(chan);
+ int seen_current =3D 0;
+
+ fsldma_clean_completed_descriptor(chan);
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_running, node) {
+ /* do not advance past the current descriptor loaded into the
+ * hardware channel, subsequent descriptors are either in
+ * process or have not been submitted
+ */
=20
Coding style.
=20
quoted
+ if (seen_current)
+ break;
+
+ /* stop the search if we reach the current descriptor and the
+ * channel is busy
+ */
=20
Coding style.
=20
quoted
+ if (desc->async_tx.phys =3D=3D curr_phys) {
+ seen_current =3D 1;
+ if (!idle)
+ break;
+ }
+
=20
This trick where you try to look at the hardware state to determine how
much to clean up has been a source of headaches in the past versions of
this driver.
I know a little about the history of this driver. Could you tell me what ki=
nd
headaches in the past versions, I can have a test and fix it in my patch. A=
nd
I also think use current phys addr should be more explicit.
Thanks.
=20
It is much easier to reason about the state of the hardware and avoid
race conditions if you complete entire blocks of descriptors after the
hardware interrupts you to tell you it is finished.
In current driver, it's ok, but there is a potential issue when enable
async_tx api. How can you determine these descriptors in ld_running whether
have been completed in fsl_tx_status()? (I mean in my patch.)
=20
This is the philosophy employed by the driver before your modifications:
ld_pending: a block of descriptors which is ready to run as soon as the
hardware becomes idle.
ld_running: a block of descriptors which is being executed by the
hardware.
These 2 lists are not enough, async_tx descriptors must be kept order as
expected of its submitter, we only can process the descriptor which has bee=
n
acked by async_tx api, but not free all descriptors in ld_running.
For example,
Step 1, in async_tx memcpy api,
tx2 =3D device->device_prep_dma_memcpy(...),
tx2->depend_tx =3D tx1;
step 2, in async_tx submit api,
async_tx_submit() will check tx2->depend_tx whether has been acked,
unfortunately, tx2->depend_tx is freed before step 2 (dma channels is flush=
ed
by other drivers), the contents of tx2->depend_tx is set to POOL_POISON_FRE=
ED
if DMAPOOL_DEBUG is enabled (illegal pointer will be used if disable this c=
onfig
option);
step 3, BUG_ON(async_tx_test_ack(depend_tx)) is triggered.
For resolve this potential risk, first, ack flag must be checked in dma dri=
ver,
second, ld_completed is added to restore all descriptors which have been ac=
ked
and completed.
In my following answer, most of all are around this idea.
=20
quoted
+ cookie =3D fsldma_run_tx_complete_actions(desc, chan, cookie);
+
+ if (fsldma_clean_running_descriptor(desc, chan))
+ break;
+
+ }
+
+ /*
+ * Start any pending transactions automatically
+ *
+ * In the ideal case, we keep the DMA controller busy while we go
+ * ahead and free the descriptors below.
+ */
+ fsl_chan_xfer_ld_queue(chan);
+
+ if (cookie > 0)
+ chan->common.completed_cookie =3D cookie; }
+
static dma_cookie_t fsl_dma_tx_submit(struct dma_async_tx_descriptor
*tx) {
struct fsldma_chan *chan =3D to_fsl_chan(tx->chan); @@ -534,8 +745,10
@@ -811,124 +1024,6 @@ static int fsl_dma_device_control(struct
dma_chan *dchan, }
/**
- * fsldma_cleanup_descriptor - cleanup and free a single link
descriptor
- * @chan: Freescale DMA channel
- * @desc: descriptor to cleanup and free
- *
- * This function is used on a descriptor which has been executed by
the DMA
- * controller. It will run any callbacks, submit any dependencies,
and then
- * free the descriptor.
- */
-static void fsldma_cleanup_descriptor(struct fsldma_chan *chan,
- struct fsl_desc_sw *desc)
-{
- struct dma_async_tx_descriptor *txd =3D &desc->async_tx;
- struct device *dev =3D chan->common.device->dev;
- dma_addr_t src =3D get_desc_src(chan, desc);
- dma_addr_t dst =3D get_desc_dst(chan, desc);
- u32 len =3D get_desc_cnt(chan, desc);
-
- /* Run the link descriptor callback function */
- if (txd->callback) {
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p callback\n", desc);
-#endif
- txd->callback(txd->callback_param);
- }
-
- /* Run any dependencies */
- dma_run_dependencies(txd);
-
- /* Unmap the dst buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
- if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
- dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
- else
- dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
- }
-
- /* Unmap the src buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
- if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
- dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
- else
- dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
- }
-
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p free\n", desc);
-#endif
- dma_pool_free(chan->desc_pool, desc, txd->phys);
-}
-
-/**
- * fsl_chan_xfer_ld_queue - transfer any pending transactions
- * @chan : Freescale DMA channel
- *
- * HARDWARE STATE: idle
- * LOCKING: must hold chan->desc_lock
- */
-static void fsl_chan_xfer_ld_queue(struct fsldma_chan *chan) -{
- struct fsl_desc_sw *desc;
-
- /*
- * If the list of pending descriptors is empty, then we
- * don't need to do any work at all
- */
- if (list_empty(&chan->ld_pending)) {
- chan_dbg(chan, "no pending LDs\n");
- return;
- }
-
- /*
- * The DMA controller is not idle, which means that the interrupt
- * handler will start any queued transactions when it runs after
- * this transaction finishes
- */
- if (!chan->idle) {
- chan_dbg(chan, "DMA controller still busy\n");
- return;
- }
-
- /*
- * If there are some link descriptors which have not been
- * transferred, we need to start the controller
- */
-
- /*
- * Move all elements from the queue of pending transactions
- * onto the list of running transactions
- */
- chan_dbg(chan, "idle, starting controller\n");
- desc =3D list_first_entry(&chan->ld_pending, struct fsl_desc_sw,
node);
quoted
- list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
-
- /*
- * The 85xx DMA controller doesn't clear the channel start bit
- * automatically at the end of a transfer. Therefore we must clear
- * it in software before starting the transfer.
- */
- if ((chan->feature & FSL_DMA_IP_MASK) =3D=3D FSL_DMA_IP_85XX) {
- u32 mode;
-
- mode =3D DMA_IN(chan, &chan->regs->mr, 32);
- mode &=3D ~FSL_DMA_MR_CS;
- DMA_OUT(chan, &chan->regs->mr, mode, 32);
- }
-
- /*
- * Program the descriptor's address into the DMA controller,
- * then start the DMA transaction
- */
- set_cdar(chan, desc->async_tx.phys);
- get_cdar(chan);
-
- dma_start(chan);
- chan->idle =3D false;
-}
-
-/**
* fsl_dma_memcpy_issue_pending - Issue the DMA start command
* @chan : Freescale DMA channel
*/
=20
You've made status from a very quick operation (compare two cookies) into
a potentially long running operation. It may now run callbacks, unmap
pages, etc.
Yes, that's right, callbacks and unmap pages will be invoked if DMA status
is not DMA_SUCCESS.
=20
I note that Documentation/crypto/async-tx-api.txt section 3.6
"Constraints" does say that async_*() functions cannot be called from IRQ
context. However, the DMAEngine API itself does not have anything to say
about IRQ context.
=20
I expect fsl_tx_status() to be quick, and not potentially call other
arbitrary code.
fsl_tx_status() is not in IRQ context. It's reasonable to unmap pages and
run dependency of descriptor as fsldma_run_tx_complete_actions() does.
=20
Is it possible to leave this function unchanged?
According to my knowledge, it is unlikely to be left unchanged, or it will =
violate
the design of this interface. If DMA status is not DMA_SUCCESS, that means =
there
are new descriptors completed, we should move them to ld_completed, and do =
actions
to its async_tx descriptors, then dma descriptor will be freed at another t=
ime.
Most of my idea is from iop-adma.c, the original interface is not align wit=
h it.
Async_tx flags (expecially ack_test) is not considered when dma descriptor =
is freed,
so some random errors happened, I think you must familiar with this history=
.
As an important "synchronization flag", async_tx api must control the order=
of tx
descriptor. Dma driver also should make sure keeping order when free the de=
scriptor.
That's the reason why I add ld_completed list.
=20
Also note that if you leave this function unchanged, the locking error
pointed out above (fsldma_clean_completed_descriptor() is not called with
the lock held) goes away.
I know. Thanks.
=20
quoted
spin_unlock_irqrestore(&chan->desc_lock, flags);
- return ret;
+ return dma_cookie_status(dchan, cookie, txstate);
}
/*--------------------------------------------------------------------
--------*/ @@ -1035,53 +1136,21 @@ static irqreturn_t
fsldma_chan_irq(int irq, void *data) static void
dma_do_tasklet(unsigned long data) {
struct fsldma_chan *chan =3D (struct fsldma_chan *)data;
- struct fsl_desc_sw *desc, *_desc;
- LIST_HEAD(ld_cleanup);
unsigned long flags;
chan_dbg(chan, "tasklet entry\n");
spin_lock_irqsave(&chan->desc_lock, flags);
- /* update the cookie if we have some descriptors to cleanup */
- if (!list_empty(&chan->ld_running)) {
- dma_cookie_t cookie;
-
- desc =3D to_fsl_desc(chan->ld_running.prev);
- cookie =3D desc->async_tx.cookie;
- dma_cookie_complete(&desc->async_tx);
-
- chan_dbg(chan, "completed_cookie=3D%d\n", cookie);
- }
-
- /*
- * move the descriptors to a temporary list so we can drop the lock
- * during the entire cleanup operation
- */
- list_splice_tail_init(&chan->ld_running, &ld_cleanup);
+ /* Run all cleanup for this descriptor */
+ fsldma_cleanup_descriptor(chan);
/* the hardware is now idle and ready for more */
chan->idle =3D true;
- /*
- * Start any pending transactions automatically
- *
- * In the ideal case, we keep the DMA controller busy while we go
- * ahead and free the descriptors below.
- */
fsl_chan_xfer_ld_queue(chan);
spin_unlock_irqrestore(&chan->desc_lock, flags);
- /* Run the callback for each descriptor, in order */
- list_for_each_entry_safe(desc, _desc, &ld_cleanup, node) {
-
- /* Remove from the list of transactions */
- list_del(&desc->node);
-
- /* Run all cleanup for this descriptor */
- fsldma_cleanup_descriptor(chan, desc);
- }
-
chan_dbg(chan, "tasklet exit\n");
}
@@ -1262,6 +1331,7 @@ static int __devinit fsl_dma_chan_probe(struct
From: Ira W. Snyder <hidden> Date: 2012-07-17 16:17:00
On Tue, Jul 17, 2012 at 07:06:33AM +0000, Liu Qiang-B32616 wrote:
quoted
-----Original Message-----
From: Ira W. Snyder [mailto:iws@ovro.caltech.edu]
Sent: Tuesday, July 17, 2012 4:01 AM
To: Liu Qiang-B32616
Cc: linux-crypto@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Phillips
Kim-R1AAHA; herbert@gondor.hengli.com.au; davem@davemloft.net; Dan
Williams; Vinod Koul; Li Yang-R58472
Subject: Re: [PATCH v3 3/4] fsl-dma: change release process of dma
descriptor for supporting async_tx
On Mon, Jul 16, 2012 at 12:08:29PM +0800, Qiang Liu wrote:
quoted
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma
descriptor, all descriptors will be released whatever is acked or
no-acked by async_tx, so there is a potential race condition when dma
engine is uesd by others clients (e.g. when enable NET_DMA to offload
TCP).
quoted
In our case, a race condition which is raised when use both of talitos
and dmaengine to offload xor is because napi scheduler will sync all
pending requests in dma channels, it affects the process of raid
operations due to ack_tx is not checked in fsl dma. The no-acked
descriptor is freed which is submitted just now, as a dependent tx,
this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
---
drivers/dma/fsldma.c | 378 +++++++++++++++++++++++++++++-------------
+ list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
+
+ /*
+ * The 85xx DMA controller doesn't clear the channel start bit
+ * automatically at the end of a transfer. Therefore we must clear
+ * it in software before starting the transfer.
+ */
+ if ((chan->feature & FSL_DMA_IP_MASK) == FSL_DMA_IP_85XX) {
+ u32 mode;
+
+ mode = DMA_IN(chan, &chan->regs->mr, 32);
+ mode &= ~FSL_DMA_MR_CS;
+ DMA_OUT(chan, &chan->regs->mr, mode, 32);
+ }
+
+ /*
+ * Program the descriptor's address into the DMA controller,
+ * then start the DMA transaction
+ */
+ set_cdar(chan, desc->async_tx.phys);
+ get_cdar(chan);
+
+ dma_start(chan);
+ chan->idle = false;
+}
+
Please add a note about the locking requirements here, and for the other
new functions you've added.
You call this function from two places:
1) fsldma_cleanup_descriptor() - called with mod->desc_lock held
2) fsl_tx_status() - WITHOUT mod->desc_lock held
One of them is definitely wrong, and I'd bet that it is #2. You're
modifying ld_completed without a lock.
Yes, My bad, I will correct it.
quoted
quoted
+static int
+fsldma_clean_completed_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_completed, node) {
+
+ if (async_tx_test_ack(&desc->async_tx)) {
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p free\n", desc); #endif
+ dma_pool_free(chan->desc_pool, desc,
+ desc->async_tx.phys);
+ }
+ }
+
+ return 0;
+}
+
+/**
+ * fsldma_run_tx_complete_actions - cleanup and free a single link
+descriptor
+ * @chan: Freescale DMA channel
+ * @desc: descriptor to cleanup and free
+ * @cookie: Freescale DMA transaction identifier
+ *
+ * This function is used on a descriptor which has been executed by
+the DMA
+ * controller. It will run any callbacks, submit any dependencies,
+and then
+ * free the descriptor.
+ */
+static dma_cookie_t fsldma_run_tx_complete_actions(struct fsl_desc_sw
*desc,
quoted
+ struct fsldma_chan *chan, dma_cookie_t cookie) {
+ struct dma_async_tx_descriptor *txd = &desc->async_tx;
+ struct device *dev = chan->common.device->dev;
+ dma_addr_t src = get_desc_src(chan, desc);
+ dma_addr_t dst = get_desc_dst(chan, desc);
+ u32 len = get_desc_cnt(chan, desc);
+
+ BUG_ON(txd->cookie < 0);
+
+ if (txd->cookie > 0) {
+ cookie = txd->cookie;
+
+ /* Run the link descriptor callback function */
+ if (txd->callback) {
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p callback\n", desc); #endif
+ txd->callback(txd->callback_param);
+ }
+
+ /* Unmap the dst buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
+ if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
+ dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
+ else
+ dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
+ }
+
+ /* Unmap the src buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
+ if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
+ dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
+ else
+ dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
+ }
+ }
+
+ /* Run any dependencies */
+ dma_run_dependencies(txd);
+
+ return cookie;
+}
+
+static int
+fsldma_clean_running_descriptor(struct fsl_desc_sw *desc,
+ struct fsldma_chan *chan)
+{
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+ /* the client is allowed to attach dependent operations
+ * until 'ack' is set
+ */
This comment is does not follow the coding style. It should be:
/*
* the client is allowed to attech dependent operations
* until 'ack' is set
*/
Fine, I will correct it in v4. Include another 2 places related to coding style.
Thanks.
quoted
quoted
+ if (!async_tx_test_ack(&desc->async_tx)) {
+ /* move this slot to the completed */
Perhaps a better comment would be:
Move this descriptor to the list of descriptors which is complete, but
still awaiting the 'ack' bit to be set.
This should all be on one line. It is less than 80 characters wide.
Accept.
quoted
quoted
+ return 0;
+}
+
Locking notes please.
I will add it in v4, please check. Thanks.
quoted
quoted
+static void fsldma_cleanup_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+ dma_cookie_t cookie = 0;
+ dma_addr_t curr_phys = get_cdar(chan);
+ int idle = dma_is_idle(chan);
+ int seen_current = 0;
+
+ fsldma_clean_completed_descriptor(chan);
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_running, node) {
+ /* do not advance past the current descriptor loaded into the
+ * hardware channel, subsequent descriptors are either in
+ * process or have not been submitted
+ */
Coding style.
quoted
+ if (seen_current)
+ break;
+
+ /* stop the search if we reach the current descriptor and the
+ * channel is busy
+ */
Coding style.
quoted
+ if (desc->async_tx.phys == curr_phys) {
+ seen_current = 1;
+ if (!idle)
+ break;
+ }
+
This trick where you try to look at the hardware state to determine how
much to clean up has been a source of headaches in the past versions of
this driver.
I know a little about the history of this driver. Could you tell me what kind
headaches in the past versions, I can have a test and fix it in my patch. And
I also think use current phys addr should be more explicit.
Thanks.
It has been a very long time since I last worked on this code, but I
will try to remember.
I remember one problem where the currently running descriptor was free'd
while the hardware was still executing it.
There was another related problem where the DMA hardware would lock up,
and it is impossible to recover without a hard reset. The CB (channel
busy) bit gets stuck on, and the running transfer never completes. This
may have been due to a programming issue in a user of the DMAEngine API,
and not this driver itself. I don't remember for sure anymore.
Our current system here at work has 120 boards with this DMA controller.
Each one runs 100+ DMA operations per second, 24/7/365. They've been
online for more than two years. I know for sure that the current code
doesn't lock up the DMA controller. :)
I think your bug is real, and needs to be fixed. I'm just trying to make
sure I understand the change, so it won't break other users. I'm only
trying to help.
quoted
It is much easier to reason about the state of the hardware and avoid
race conditions if you complete entire blocks of descriptors after the
hardware interrupts you to tell you it is finished.
In current driver, it's ok, but there is a potential issue when enable
async_tx api. How can you determine these descriptors in ld_running whether
have been completed in fsl_tx_status()? (I mean in my patch.)
I think your idea using an ld_completed list for descriptors which have
been run by the hardware, but not yet 'ack'ed by software is fine.
Would something similar to the following work?
ld_pending: build a list of descriptors until issue_pending() is called.
This is exactly what it does now, no changes needed.
ld_running: this list of descriptors is currently executing. Mostly
unchanged from how it works now.
When you get an interrupt, you know the descriptors in ld_running are
finished. Update the cookie to the highest number from ld_running. Free
the descriptors which have been 'ack'ed immediately. Move the ones which
are not 'ack'ed onto ld_completed. As part of this process, you should
run dma_run_dependencies() and callbacks as needed.
I think that this solves the problem you are seeing, which is that
descriptors which have not been 'ack'ed are free'd.
If this is unclear, I can write some code to demonstrate. If you could
write a small test driver, similar to drivers/dma/dmatest.c, which tests
the async_tx API without any extra hardware needed, I can run it. I have
never used the async_tx API before.
quoted
This is the philosophy employed by the driver before your modifications:
ld_pending: a block of descriptors which is ready to run as soon as the
hardware becomes idle.
ld_running: a block of descriptors which is being executed by the
hardware.
These 2 lists are not enough, async_tx descriptors must be kept order as
expected of its submitter, we only can process the descriptor which has been
acked by async_tx api, but not free all descriptors in ld_running.
For example,
Step 1, in async_tx memcpy api,
tx2 = device->device_prep_dma_memcpy(...),
tx2->depend_tx = tx1;
step 2, in async_tx submit api,
async_tx_submit() will check tx2->depend_tx whether has been acked,
unfortunately, tx2->depend_tx is freed before step 2 (dma channels is flushed
by other drivers), the contents of tx2->depend_tx is set to POOL_POISON_FREED
if DMAPOOL_DEBUG is enabled (illegal pointer will be used if disable this config
option);
step 3, BUG_ON(async_tx_test_ack(depend_tx)) is triggered.
For resolve this potential risk, first, ack flag must be checked in dma driver,
second, ld_completed is added to restore all descriptors which have been acked
and completed.
In my following answer, most of all are around this idea.
quoted
quoted
+ cookie = fsldma_run_tx_complete_actions(desc, chan, cookie);
+
+ if (fsldma_clean_running_descriptor(desc, chan))
+ break;
+
+ }
+
+ /*
+ * Start any pending transactions automatically
+ *
+ * In the ideal case, we keep the DMA controller busy while we go
+ * ahead and free the descriptors below.
+ */
+ fsl_chan_xfer_ld_queue(chan);
+
+ if (cookie > 0)
+ chan->common.completed_cookie = cookie; }
+
static dma_cookie_t fsl_dma_tx_submit(struct dma_async_tx_descriptor
*tx) {
struct fsldma_chan *chan = to_fsl_chan(tx->chan); @@ -534,8 +745,10
@@ -811,124 +1024,6 @@ static int fsl_dma_device_control(struct
dma_chan *dchan, }
/**
- * fsldma_cleanup_descriptor - cleanup and free a single link
descriptor
- * @chan: Freescale DMA channel
- * @desc: descriptor to cleanup and free
- *
- * This function is used on a descriptor which has been executed by
the DMA
- * controller. It will run any callbacks, submit any dependencies,
and then
- * free the descriptor.
- */
-static void fsldma_cleanup_descriptor(struct fsldma_chan *chan,
- struct fsl_desc_sw *desc)
-{
- struct dma_async_tx_descriptor *txd = &desc->async_tx;
- struct device *dev = chan->common.device->dev;
- dma_addr_t src = get_desc_src(chan, desc);
- dma_addr_t dst = get_desc_dst(chan, desc);
- u32 len = get_desc_cnt(chan, desc);
-
- /* Run the link descriptor callback function */
- if (txd->callback) {
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p callback\n", desc);
-#endif
- txd->callback(txd->callback_param);
- }
-
- /* Run any dependencies */
- dma_run_dependencies(txd);
-
- /* Unmap the dst buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
- if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
- dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
- else
- dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
- }
-
- /* Unmap the src buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
- if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
- dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
- else
- dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
- }
-
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p free\n", desc);
-#endif
- dma_pool_free(chan->desc_pool, desc, txd->phys);
-}
-
-/**
- * fsl_chan_xfer_ld_queue - transfer any pending transactions
- * @chan : Freescale DMA channel
- *
- * HARDWARE STATE: idle
- * LOCKING: must hold chan->desc_lock
- */
-static void fsl_chan_xfer_ld_queue(struct fsldma_chan *chan) -{
- struct fsl_desc_sw *desc;
-
- /*
- * If the list of pending descriptors is empty, then we
- * don't need to do any work at all
- */
- if (list_empty(&chan->ld_pending)) {
- chan_dbg(chan, "no pending LDs\n");
- return;
- }
-
- /*
- * The DMA controller is not idle, which means that the interrupt
- * handler will start any queued transactions when it runs after
- * this transaction finishes
- */
- if (!chan->idle) {
- chan_dbg(chan, "DMA controller still busy\n");
- return;
- }
-
- /*
- * If there are some link descriptors which have not been
- * transferred, we need to start the controller
- */
-
- /*
- * Move all elements from the queue of pending transactions
- * onto the list of running transactions
- */
- chan_dbg(chan, "idle, starting controller\n");
- desc = list_first_entry(&chan->ld_pending, struct fsl_desc_sw,
node);
quoted
- list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
-
- /*
- * The 85xx DMA controller doesn't clear the channel start bit
- * automatically at the end of a transfer. Therefore we must clear
- * it in software before starting the transfer.
- */
- if ((chan->feature & FSL_DMA_IP_MASK) == FSL_DMA_IP_85XX) {
- u32 mode;
-
- mode = DMA_IN(chan, &chan->regs->mr, 32);
- mode &= ~FSL_DMA_MR_CS;
- DMA_OUT(chan, &chan->regs->mr, mode, 32);
- }
-
- /*
- * Program the descriptor's address into the DMA controller,
- * then start the DMA transaction
- */
- set_cdar(chan, desc->async_tx.phys);
- get_cdar(chan);
-
- dma_start(chan);
- chan->idle = false;
-}
-
-/**
* fsl_dma_memcpy_issue_pending - Issue the DMA start command
* @chan : Freescale DMA channel
*/
You've made status from a very quick operation (compare two cookies) into
a potentially long running operation. It may now run callbacks, unmap
pages, etc.
Yes, that's right, callbacks and unmap pages will be invoked if DMA status
is not DMA_SUCCESS.
quoted
I note that Documentation/crypto/async-tx-api.txt section 3.6
"Constraints" does say that async_*() functions cannot be called from IRQ
context. However, the DMAEngine API itself does not have anything to say
about IRQ context.
I expect fsl_tx_status() to be quick, and not potentially call other
arbitrary code.
fsl_tx_status() is not in IRQ context. It's reasonable to unmap pages and
run dependency of descriptor as fsldma_run_tx_complete_actions() does.
I looked at several other DMAEngine API drivers. Some of them do run
dependencies and callbacks from tx_status(). You are correct, this is
fine.
quoted
Is it possible to leave this function unchanged?
According to my knowledge, it is unlikely to be left unchanged, or it will violate
the design of this interface. If DMA status is not DMA_SUCCESS, that means there
are new descriptors completed, we should move them to ld_completed, and do actions
to its async_tx descriptors, then dma descriptor will be freed at another time.
Most of my idea is from iop-adma.c, the original interface is not align with it.
Async_tx flags (expecially ack_test) is not considered when dma descriptor is freed,
so some random errors happened, I think you must familiar with this history.
As an important "synchronization flag", async_tx api must control the order of tx
descriptor. Dma driver also should make sure keeping order when free the descriptor.
That's the reason why I add ld_completed list.
Is it possible to put the descriptors into three different states?
1) ld_pending: ready to run, but not yet executed on the hardware
Descriptors move to #2 through either dma_async_issue_pending() or by
the interrupt which happens when the hardware completes executing a set
of DMA descriptors.
2) ld_running: currently executing on the hardware
Descriptors move to #3 through the interrupt which happens when the
hardware completes executing a set of DMA descriptors.
Dependencies and callbacks are executed as the descriptors are moved
onto ld_completed.
3) ld_completed: finished executing on the hardware, but not yet 'ack'ed
When they have been 'ack'ed, the descriptors are free'd.
As noted above, I think I could code this up fairly quickly if this
explanation is unclear.
Also note that I may not understand your bug completely, and my idea may
be completely wrong!
Ira
quoted
Also note that if you leave this function unchanged, the locking error
pointed out above (fsldma_clean_completed_descriptor() is not called with
the lock held) goes away.
I know. Thanks.
quoted
quoted
spin_unlock_irqrestore(&chan->desc_lock, flags);
- return ret;
+ return dma_cookie_status(dchan, cookie, txstate);
}
/*--------------------------------------------------------------------
--------*/ @@ -1035,53 +1136,21 @@ static irqreturn_t
fsldma_chan_irq(int irq, void *data) static void
dma_do_tasklet(unsigned long data) {
struct fsldma_chan *chan = (struct fsldma_chan *)data;
- struct fsl_desc_sw *desc, *_desc;
- LIST_HEAD(ld_cleanup);
unsigned long flags;
chan_dbg(chan, "tasklet entry\n");
spin_lock_irqsave(&chan->desc_lock, flags);
- /* update the cookie if we have some descriptors to cleanup */
- if (!list_empty(&chan->ld_running)) {
- dma_cookie_t cookie;
-
- desc = to_fsl_desc(chan->ld_running.prev);
- cookie = desc->async_tx.cookie;
- dma_cookie_complete(&desc->async_tx);
-
- chan_dbg(chan, "completed_cookie=%d\n", cookie);
- }
-
- /*
- * move the descriptors to a temporary list so we can drop the lock
- * during the entire cleanup operation
- */
- list_splice_tail_init(&chan->ld_running, &ld_cleanup);
+ /* Run all cleanup for this descriptor */
+ fsldma_cleanup_descriptor(chan);
/* the hardware is now idle and ready for more */
chan->idle = true;
- /*
- * Start any pending transactions automatically
- *
- * In the ideal case, we keep the DMA controller busy while we go
- * ahead and free the descriptors below.
- */
fsl_chan_xfer_ld_queue(chan);
spin_unlock_irqrestore(&chan->desc_lock, flags);
- /* Run the callback for each descriptor, in order */
- list_for_each_entry_safe(desc, _desc, &ld_cleanup, node) {
-
- /* Remove from the list of transactions */
- list_del(&desc->node);
-
- /* Run all cleanup for this descriptor */
- fsldma_cleanup_descriptor(chan, desc);
- }
-
chan_dbg(chan, "tasklet exit\n");
}
@@ -1262,6 +1331,7 @@ static int __devinit fsl_dma_chan_probe(struct
From: Liu Qiang-B32616 <hidden> Date: 2012-07-18 03:31:49
Hi Ira,
My comments inline.
Hi Ira and Dan,
Here is a introduction about my scenario of this case.
My case is use async_tx API to offload raid5,
Use fsl-talitos to compute parity calculation, fsl-dma to process memcpy.
What bug occurred to me?
Exception is thrown by BUG_ON(async_tx_ack_test(depend_tx)) in async_tx_submit().
TASK = ee1a94a0[1390] 'md0_raid5' THREAD: ecf40000 CPU: 0
GPR00: 00000001 ecf41ca0 ee44/921a94a0 0000003f 00000001 c00593e4 00000000 00000001
GPR08: 00000000 a7a7a7a7 00000001 045/920000002 42028042 100a38d4 ed576d98 00000000
GPR16: ed5a11b0 00000000 2b162000 00000200 046/920000000 2d555000 ed3015e8 c15a7aa0
GPR24: 00000000 c155fc40 00000000 ecb63220 ecf41d28 e47/92f640bb0 ef640c30 ecf41ca0
NIP [c02b048c] async_tx_submit+0x6c/0x2b4
LR [c02b068c] async_tx_submit+0x26c/0x2b4
Call Trace:
[ecf41ca0] [c02b068c] async_tx_submit+0x26c/0x2b448/92 (unreliable)
[ecf41cd0] [c02b0a4c] async_memcpy+0x240/0x25c
[ecf41d20] [c0421064] async_copy_data+0xa0/0x17c
[ecf41d70] [c0421cf4] __raid_run_ops+0x874/0xe10
[ecf41df0] [c0426ee4] handle_stripe+0x820/0x25e8
[ecf41e90] [c0429080] raid5d+0x3d4/0x5b4
[ecf41f40] [c04329b8] md_thread+0x138/0x16c
[ecf41f90] [c008277c] kthread+0x8c/0x90
[ecf41ff0] [c0011630] kernel_thread+0x4c/0x68
What is the root cause of this bug?
The async_tx descriptor(depend_tx) is free'ed before async_tx_submit ack it.
That means async_tx descriptor should be acked before it's free'ed. In other
word, only ack'ed async_tx descriptor should be free'ed by dma engine.
How to fix it?
Add a queue ld_completed, move all completed descriptors in this queue, free
these descriptors at a proper time (these descriptors also should be acked).
Dan, do you think my understand about "ack" is right? Thanks.
- Qiang
-----Original Message-----
From: Ira W. Snyder [mailto:iws@ovro.caltech.edu]
Sent: Wednesday, July 18, 2012 12:17 AM
To: Liu Qiang-B32616
Cc: linux-crypto@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Phillips
Kim-R1AAHA; herbert@gondor.hengli.com.au; davem@davemloft.net; Dan
Williams; Vinod Koul; Li Yang-R58472
Subject: Re: [PATCH v3 3/4] fsl-dma: change release process of dma
descriptor for supporting async_tx
On Tue, Jul 17, 2012 at 07:06:33AM +0000, Liu Qiang-B32616 wrote:
quoted
quoted
-----Original Message-----
From: Ira W. Snyder [mailto:iws@ovro.caltech.edu]
Sent: Tuesday, July 17, 2012 4:01 AM
To: Liu Qiang-B32616
Cc: linux-crypto@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
Phillips
quoted
quoted
Kim-R1AAHA; herbert@gondor.hengli.com.au; davem@davemloft.net; Dan
Williams; Vinod Koul; Li Yang-R58472
Subject: Re: [PATCH v3 3/4] fsl-dma: change release process of dma
descriptor for supporting async_tx
On Mon, Jul 16, 2012 at 12:08:29PM +0800, Qiang Liu wrote:
quoted
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma
descriptor, all descriptors will be released whatever is acked or
no-acked by async_tx, so there is a potential race condition when
dma
quoted
quoted
quoted
engine is uesd by others clients (e.g. when enable NET_DMA to
offload
quoted
quoted
TCP).
quoted
In our case, a race condition which is raised when use both of
talitos
quoted
quoted
quoted
and dmaengine to offload xor is because napi scheduler will sync
all
quoted
quoted
quoted
pending requests in dma channels, it affects the process of raid
operations due to ack_tx is not checked in fsl dma. The no-acked
descriptor is freed which is submitted just now, as a dependent tx,
this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
---
drivers/dma/fsldma.c | 378 +++++++++++++++++++++++++++++---------
+ * handler will start any queued transactions when it runs
after
quoted
quoted
quoted
+ * this transaction finishes
+ */
+ if (!chan->idle) {
+ chan_dbg(chan, "DMA controller still busy\n");
+ return;
+ }
+
+ /*
+ * If there are some link descriptors which have not been
+ * transferred, we need to start the controller
+ */
+
+ /*
+ * Move all elements from the queue of pending transactions
+ * onto the list of running transactions
+ */
+ chan_dbg(chan, "idle, starting controller\n");
+ desc = list_first_entry(&chan->ld_pending, struct fsl_desc_sw,
node);
quoted
+ list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
+
+ /*
+ * The 85xx DMA controller doesn't clear the channel start
bit
quoted
quoted
quoted
+ * automatically at the end of a transfer. Therefore we must
clear
quoted
quoted
quoted
+ * it in software before starting the transfer.
+ */
+ if ((chan->feature & FSL_DMA_IP_MASK) == FSL_DMA_IP_85XX) {
+ u32 mode;
+
+ mode = DMA_IN(chan, &chan->regs->mr, 32);
+ mode &= ~FSL_DMA_MR_CS;
+ DMA_OUT(chan, &chan->regs->mr, mode, 32);
+ }
+
+ /*
+ * Program the descriptor's address into the DMA controller,
+ * then start the DMA transaction
+ */
+ set_cdar(chan, desc->async_tx.phys);
+ get_cdar(chan);
+
+ dma_start(chan);
+ chan->idle = false;
+}
+
Please add a note about the locking requirements here, and for the
other
quoted
quoted
new functions you've added.
You call this function from two places:
1) fsldma_cleanup_descriptor() - called with mod->desc_lock held
2) fsl_tx_status() - WITHOUT mod->desc_lock held
One of them is definitely wrong, and I'd bet that it is #2. You're
modifying ld_completed without a lock.
Yes, My bad, I will correct it.
quoted
quoted
+static int
+fsldma_clean_completed_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_completed,
node) {
quoted
quoted
quoted
+
+ if (async_tx_test_ack(&desc->async_tx)) {
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p free\n", desc); #endif
+ dma_pool_free(chan->desc_pool, desc,
+ desc->async_tx.phys);
+ }
+ }
+
+ return 0;
+}
+
+/**
+ * fsldma_run_tx_complete_actions - cleanup and free a single link
+descriptor
+ * @chan: Freescale DMA channel
+ * @desc: descriptor to cleanup and free
+ * @cookie: Freescale DMA transaction identifier
+ *
+ * This function is used on a descriptor which has been executed
by
quoted
quoted
quoted
+the DMA
+ * controller. It will run any callbacks, submit any dependencies,
+and then
+ * free the descriptor.
+ */
+static dma_cookie_t fsldma_run_tx_complete_actions(struct
fsl_desc_sw
quoted
quoted
*desc,
quoted
+ struct fsldma_chan *chan, dma_cookie_t cookie) {
+ struct dma_async_tx_descriptor *txd = &desc->async_tx;
+ struct device *dev = chan->common.device->dev;
+ dma_addr_t src = get_desc_src(chan, desc);
+ dma_addr_t dst = get_desc_dst(chan, desc);
+ u32 len = get_desc_cnt(chan, desc);
+
+ BUG_ON(txd->cookie < 0);
+
+ if (txd->cookie > 0) {
+ cookie = txd->cookie;
+
+ /* Run the link descriptor callback function */
+ if (txd->callback) {
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p callback\n", desc); #endif
+ txd->callback(txd->callback_param);
+ }
+
+ /* Unmap the dst buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
+ if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
+ dma_unmap_single(dev, dst, len,
DMA_FROM_DEVICE);
quoted
quoted
quoted
+ else
+ dma_unmap_page(dev, dst, len,
DMA_FROM_DEVICE);
quoted
quoted
quoted
+ }
+
+ /* Unmap the src buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
+ if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
+ dma_unmap_single(dev, src, len,
DMA_TO_DEVICE);
quoted
quoted
quoted
+ else
+ dma_unmap_page(dev, src, len,
DMA_TO_DEVICE);
quoted
quoted
quoted
+ }
+ }
+
+ /* Run any dependencies */
+ dma_run_dependencies(txd);
+
+ return cookie;
+}
+
+static int
+fsldma_clean_running_descriptor(struct fsl_desc_sw *desc,
+ struct fsldma_chan *chan)
+{
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+ /* the client is allowed to attach dependent operations
+ * until 'ack' is set
+ */
This comment is does not follow the coding style. It should be:
/*
* the client is allowed to attech dependent operations
* until 'ack' is set
*/
Fine, I will correct it in v4. Include another 2 places related to
coding style.
quoted
Thanks.
quoted
quoted
+ if (!async_tx_test_ack(&desc->async_tx)) {
+ /* move this slot to the completed */
Perhaps a better comment would be:
Move this descriptor to the list of descriptors which is complete,
This should all be on one line. It is less than 80 characters wide.
Accept.
quoted
quoted
+ return 0;
+}
+
Locking notes please.
I will add it in v4, please check. Thanks.
quoted
quoted
+static void fsldma_cleanup_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+ dma_cookie_t cookie = 0;
+ dma_addr_t curr_phys = get_cdar(chan);
+ int idle = dma_is_idle(chan);
+ int seen_current = 0;
+
+ fsldma_clean_completed_descriptor(chan);
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_running, node)
{
quoted
quoted
quoted
+ /* do not advance past the current descriptor loaded
into the
quoted
quoted
quoted
+ * hardware channel, subsequent descriptors are either
in
quoted
quoted
quoted
+ * process or have not been submitted
+ */
Coding style.
quoted
+ if (seen_current)
+ break;
+
+ /* stop the search if we reach the current descriptor
and the
quoted
quoted
quoted
+ * channel is busy
+ */
Coding style.
quoted
+ if (desc->async_tx.phys == curr_phys) {
+ seen_current = 1;
+ if (!idle)
+ break;
+ }
+
This trick where you try to look at the hardware state to determine
how
quoted
quoted
much to clean up has been a source of headaches in the past versions
of
quoted
quoted
this driver.
I know a little about the history of this driver. Could you tell me
what kind
quoted
headaches in the past versions, I can have a test and fix it in my
patch. And
quoted
I also think use current phys addr should be more explicit.
Thanks.
It has been a very long time since I last worked on this code, but I
will try to remember.
I remember one problem where the currently running descriptor was free'd
while the hardware was still executing it.
There was another related problem where the DMA hardware would lock up,
and it is impossible to recover without a hard reset. The CB (channel
busy) bit gets stuck on, and the running transfer never completes. This
may have been due to a programming issue in a user of the DMAEngine API,
and not this driver itself. I don't remember for sure anymore.
Our current system here at work has 120 boards with this DMA controller.
Each one runs 100+ DMA operations per second, 24/7/365. They've been
online for more than two years. I know for sure that the current code
doesn't lock up the DMA controller. :)
I think your bug is real, and needs to be fixed. I'm just trying to make
sure I understand the change, so it won't break other users. I'm only
trying to help.
Thanks for your information. I will do more explanation of my idea in the
following answer.
Could you provide some sample code for reproduce bug, I don't know dmatest.c
whether is enough. I will add dma self test in fsldma.c.
quoted
quoted
It is much easier to reason about the state of the hardware and avoid
race conditions if you complete entire blocks of descriptors after
the
quoted
quoted
hardware interrupts you to tell you it is finished.
In current driver, it's ok, but there is a potential issue when enable
async_tx api. How can you determine these descriptors in ld_running
whether
quoted
have been completed in fsl_tx_status()? (I mean in my patch.)
I think your idea using an ld_completed list for descriptors which have
been run by the hardware, but not yet 'ack'ed by software is fine.
Would something similar to the following work?
ld_pending: build a list of descriptors until issue_pending() is called.
This is exactly what it does now, no changes needed.
Yes, no changes.
ld_running: this list of descriptors is currently executing. Mostly
unchanged from how it works now.
Yes, no changes.
I will add descriptions about all new interfaces.
When you get an interrupt, you know the descriptors in ld_running are
finished. Update the cookie to the highest number from ld_running. Free
the descriptors which have been 'ack'ed immediately. Move the ones which
are not 'ack'ed onto ld_completed. As part of this process, you should
run dma_run_dependencies() and callbacks as needed.
Right, below is new implement of dma_do_tasklet();
First, dma_do_tasklet()
-> fsldma_cleanup_descriptor()
-> fsldma_clean_completed_descriptor(), free the descriptors which has been ack'ed (I mean in queue ld_completed, not include other queues);
Second, transverse the queue ld_running
-> fsldma_run_tx_complete_actions(), find the last descriptor which is completed, update the cookie to the highest number, run callback, unmap dma pages, and run dma_run_dependencies();
-> fsldma_clean_running_descriptor(), move this descriptor from ld_running to ld_completed.
Last,
-> fsl_chan_xfer_ld_queue(), submit much more descriptors from ld_pending to ld_running.
I hope my description is clear enough.
I think that this solves the problem you are seeing, which is that
descriptors which have not been 'ack'ed are free'd.
If this is unclear, I can write some code to demonstrate. If you could
write a small test driver, similar to drivers/dma/dmatest.c, which tests
the async_tx API without any extra hardware needed, I can run it. I have
never used the async_tx API before.
Your description is clear, I agree with you, I will add fsldma self test in
the file.
quoted
quoted
This is the philosophy employed by the driver before your
modifications:
quoted
quoted
ld_pending: a block of descriptors which is ready to run as soon as
the
quoted
quoted
hardware becomes idle.
ld_running: a block of descriptors which is being executed by the
hardware.
These 2 lists are not enough, async_tx descriptors must be kept order
as
quoted
expected of its submitter, we only can process the descriptor which has
been
quoted
acked by async_tx api, but not free all descriptors in ld_running.
For example,
Step 1, in async_tx memcpy api,
tx2 = device->device_prep_dma_memcpy(...),
tx2->depend_tx = tx1;
step 2, in async_tx submit api,
async_tx_submit() will check tx2->depend_tx whether has been acked,
unfortunately, tx2->depend_tx is freed before step 2 (dma channels is
flushed
quoted
by other drivers), the contents of tx2->depend_tx is set to
POOL_POISON_FREED
quoted
if DMAPOOL_DEBUG is enabled (illegal pointer will be used if disable
this config
quoted
option);
step 3, BUG_ON(async_tx_test_ack(depend_tx)) is triggered.
For resolve this potential risk, first, ack flag must be checked in dma
driver,
quoted
second, ld_completed is added to restore all descriptors which have
been acked
quoted
and completed.
In my following answer, most of all are around this idea.
+
+ if (fsldma_clean_running_descriptor(desc, chan))
+ break;
+
+ }
+
+ /*
+ * Start any pending transactions automatically
+ *
+ * In the ideal case, we keep the DMA controller busy while
we go
quoted
quoted
quoted
+ * ahead and free the descriptors below.
+ */
+ fsl_chan_xfer_ld_queue(chan);
+
+ if (cookie > 0)
+ chan->common.completed_cookie = cookie; }
+
static dma_cookie_t fsl_dma_tx_submit(struct
@@ -811,124 +1024,6 @@ static int fsl_dma_device_control(struct
dma_chan *dchan, }
/**
- * fsldma_cleanup_descriptor - cleanup and free a single link
descriptor
- * @chan: Freescale DMA channel
- * @desc: descriptor to cleanup and free
- *
- * This function is used on a descriptor which has been executed
by
quoted
quoted
quoted
the DMA
- * controller. It will run any callbacks, submit any dependencies,
and then
- * free the descriptor.
- */
-static void fsldma_cleanup_descriptor(struct fsldma_chan *chan,
- struct fsl_desc_sw *desc)
-{
- struct dma_async_tx_descriptor *txd = &desc->async_tx;
- struct device *dev = chan->common.device->dev;
- dma_addr_t src = get_desc_src(chan, desc);
- dma_addr_t dst = get_desc_dst(chan, desc);
- u32 len = get_desc_cnt(chan, desc);
-
- /* Run the link descriptor callback function */
- if (txd->callback) {
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p callback\n", desc);
-#endif
- txd->callback(txd->callback_param);
- }
-
- /* Run any dependencies */
- dma_run_dependencies(txd);
-
- /* Unmap the dst buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
- if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
- dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
- else
- dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
- }
-
- /* Unmap the src buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
- if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
- dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
- else
- dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
- }
-
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p free\n", desc);
-#endif
- dma_pool_free(chan->desc_pool, desc, txd->phys);
-}
-
-/**
- * fsl_chan_xfer_ld_queue - transfer any pending transactions
- * @chan : Freescale DMA channel
- *
- * HARDWARE STATE: idle
- * LOCKING: must hold chan->desc_lock
- */
-static void fsl_chan_xfer_ld_queue(struct fsldma_chan *chan) -{
- struct fsl_desc_sw *desc;
-
- /*
- * If the list of pending descriptors is empty, then we
- * don't need to do any work at all
- */
- if (list_empty(&chan->ld_pending)) {
- chan_dbg(chan, "no pending LDs\n");
- return;
- }
-
- /*
- * The DMA controller is not idle, which means that the
interrupt
quoted
quoted
quoted
- * handler will start any queued transactions when it runs
after
quoted
quoted
quoted
- * this transaction finishes
- */
- if (!chan->idle) {
- chan_dbg(chan, "DMA controller still busy\n");
- return;
- }
-
- /*
- * If there are some link descriptors which have not been
- * transferred, we need to start the controller
- */
-
- /*
- * Move all elements from the queue of pending transactions
- * onto the list of running transactions
- */
- chan_dbg(chan, "idle, starting controller\n");
- desc = list_first_entry(&chan->ld_pending, struct fsl_desc_sw,
node);
quoted
- list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
-
- /*
- * The 85xx DMA controller doesn't clear the channel start
bit
quoted
quoted
quoted
- * automatically at the end of a transfer. Therefore we must
clear
quoted
quoted
quoted
- * it in software before starting the transfer.
- */
- if ((chan->feature & FSL_DMA_IP_MASK) == FSL_DMA_IP_85XX) {
- u32 mode;
-
- mode = DMA_IN(chan, &chan->regs->mr, 32);
- mode &= ~FSL_DMA_MR_CS;
- DMA_OUT(chan, &chan->regs->mr, mode, 32);
- }
-
- /*
- * Program the descriptor's address into the DMA controller,
- * then start the DMA transaction
- */
- set_cdar(chan, desc->async_tx.phys);
- get_cdar(chan);
-
- dma_start(chan);
- chan->idle = false;
-}
-
-/**
* fsl_dma_memcpy_issue_pending - Issue the DMA start command
* @chan : Freescale DMA channel
*/
You've made status from a very quick operation (compare two cookies)
into
quoted
quoted
a potentially long running operation. It may now run callbacks, unmap
pages, etc.
Yes, that's right, callbacks and unmap pages will be invoked if DMA
status
quoted
is not DMA_SUCCESS.
quoted
I note that Documentation/crypto/async-tx-api.txt section 3.6
"Constraints" does say that async_*() functions cannot be called from
IRQ
quoted
quoted
context. However, the DMAEngine API itself does not have anything to
say
quoted
quoted
about IRQ context.
I expect fsl_tx_status() to be quick, and not potentially call other
arbitrary code.
fsl_tx_status() is not in IRQ context. It's reasonable to unmap pages
and
quoted
run dependency of descriptor as fsldma_run_tx_complete_actions() does.
I looked at several other DMAEngine API drivers. Some of them do run
dependencies and callbacks from tx_status(). You are correct, this is
fine.
quoted
quoted
Is it possible to leave this function unchanged?
According to my knowledge, it is unlikely to be left unchanged, or it
will violate
quoted
the design of this interface. If DMA status is not DMA_SUCCESS, that
means there
quoted
are new descriptors completed, we should move them to ld_completed, and
do actions
quoted
to its async_tx descriptors, then dma descriptor will be freed at
another time.
quoted
Most of my idea is from iop-adma.c, the original interface is not align
with it.
quoted
Async_tx flags (expecially ack_test) is not considered when dma
descriptor is freed,
quoted
so some random errors happened, I think you must familiar with this
history.
quoted
As an important "synchronization flag", async_tx api must control the
order of tx
quoted
descriptor. Dma driver also should make sure keeping order when free
the descriptor.
quoted
That's the reason why I add ld_completed list.
Is it possible to put the descriptors into three different states?
1) ld_pending: ready to run, but not yet executed on the hardware
Descriptors move to #2 through either dma_async_issue_pending() or by
the interrupt which happens when the hardware completes executing a set
of DMA descriptors.
2) ld_running: currently executing on the hardware
Descriptors move to #3 through the interrupt which happens when the
hardware completes executing a set of DMA descriptors.
Dependencies and callbacks are executed as the descriptors are moved
onto ld_completed.
3) ld_completed: finished executing on the hardware, but not yet 'ack'ed
When they have been 'ack'ed, the descriptors are free'd.
As noted above, I think I could code this up fairly quickly if this
explanation is unclear.
Totally right. I think you understand my idea.
Also note that I may not understand your bug completely, and my idea may
be completely wrong!
I hope you've already understand my issue:)
Thanks.
Ira
quoted
quoted
Also note that if you leave this function unchanged, the locking
error
quoted
quoted
pointed out above (fsldma_clean_completed_descriptor() is not called
--------*/ @@ -1035,53 +1136,21 @@ static irqreturn_t
fsldma_chan_irq(int irq, void *data) static void
dma_do_tasklet(unsigned long data) {
struct fsldma_chan *chan = (struct fsldma_chan *)data;
- struct fsl_desc_sw *desc, *_desc;
- LIST_HEAD(ld_cleanup);
unsigned long flags;
chan_dbg(chan, "tasklet entry\n");
spin_lock_irqsave(&chan->desc_lock, flags);
- /* update the cookie if we have some descriptors to cleanup
*/
quoted
quoted
quoted
- if (!list_empty(&chan->ld_running)) {
- dma_cookie_t cookie;
-
- desc = to_fsl_desc(chan->ld_running.prev);
- cookie = desc->async_tx.cookie;
- dma_cookie_complete(&desc->async_tx);
-
- chan_dbg(chan, "completed_cookie=%d\n", cookie);
- }
-
- /*
- * move the descriptors to a temporary list so we can drop
the lock
quoted
quoted
quoted
- * during the entire cleanup operation
- */
- list_splice_tail_init(&chan->ld_running, &ld_cleanup);
+ /* Run all cleanup for this descriptor */
+ fsldma_cleanup_descriptor(chan);
/* the hardware is now idle and ready for more */
chan->idle = true;
- /*
- * Start any pending transactions automatically
- *
- * In the ideal case, we keep the DMA controller busy while
we go
quoted
quoted
quoted
- * ahead and free the descriptors below.
- */
fsl_chan_xfer_ld_queue(chan);
spin_unlock_irqrestore(&chan->desc_lock, flags);
- /* Run the callback for each descriptor, in order */
- list_for_each_entry_safe(desc, _desc, &ld_cleanup, node) {
-
- /* Remove from the list of transactions */
- list_del(&desc->node);
-
- /* Run all cleanup for this descriptor */
- fsldma_cleanup_descriptor(chan, desc);
- }
-
chan_dbg(chan, "tasklet exit\n");
}
From: Liu Qiang-B32616 <hidden> Date: 2012-07-18 03:44:16
Hi Ira,
My comments inline.
Hi Ira and Dan,
Here is a introduction about my scenario of this case.
My case is use async_tx API to offload raid5,
Use fsl-talitos to compute parity calculation, fsl-dma to process memcpy.
What bug occurred to me?
Exception is thrown by BUG_ON(async_tx_ack_test(depend_tx)) in async_tx_sub=
mit().
TASK =3D ee1a94a0[1390] 'md0_raid5' THREAD: ecf40000 CPU: 0
GPR00: 00000001 ecf41ca0 ee44/921a94a0 0000003f 00000001 c00593e4 00000000 =
00000001=20
GPR08: 00000000 a7a7a7a7 00000001 045/920000002 42028042 100a38d4 ed576d98 =
00000000=20
GPR16: ed5a11b0 00000000 2b162000 00000200 046/920000000 2d555000 ed3015e8 =
c15a7aa0=20
GPR24: 00000000 c155fc40 00000000 ecb63220 ecf41d28 e47/92f640bb0 ef640c30 =
ecf41ca0=20
NIP [c02b048c] async_tx_submit+0x6c/0x2b4
LR [c02b068c] async_tx_submit+0x26c/0x2b4
Call Trace:
[ecf41ca0] [c02b068c] async_tx_submit+0x26c/0x2b448/92 (unreliable)
[ecf41cd0] [c02b0a4c] async_memcpy+0x240/0x25c
[ecf41d20] [c0421064] async_copy_data+0xa0/0x17c
[ecf41d70] [c0421cf4] __raid_run_ops+0x874/0xe10
[ecf41df0] [c0426ee4] handle_stripe+0x820/0x25e8
[ecf41e90] [c0429080] raid5d+0x3d4/0x5b4
[ecf41f40] [c04329b8] md_thread+0x138/0x16c
[ecf41f90] [c008277c] kthread+0x8c/0x90
[ecf41ff0] [c0011630] kernel_thread+0x4c/0x68
What is the root cause of this bug?
The async_tx descriptor(depend_tx) is free'ed before async_tx_submit ack it=
.
That means async_tx descriptor should be acked before it's free'ed. In othe=
r
word, only ack'ed async_tx descriptor should be free'ed by dma engine.
How to fix it?
Add a queue ld_completed, move all completed descriptors in this queue, fre=
e
these descriptors at a proper time (these descriptors also should be acked)=
.
Dan, do you think my understand about "ack" is right? Thanks.=20
- Qiang
-----Original Message-----
From: Ira W. Snyder [mailto:iws@ovro.caltech.edu]
Sent: Wednesday, July 18, 2012 12:17 AM
To: Liu Qiang-B32616
Cc: linux-crypto@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; Phillips
Kim-R1AAHA; herbert@gondor.hengli.com.au; davem@davemloft.net; Dan
Williams; Vinod Koul; Li Yang-R58472
Subject: Re: [PATCH v3 3/4] fsl-dma: change release process of dma
descriptor for supporting async_tx
=20
On Tue, Jul 17, 2012 at 07:06:33AM +0000, Liu Qiang-B32616 wrote:
quoted
quoted
-----Original Message-----
From: Ira W. Snyder [mailto:iws@ovro.caltech.edu]
Sent: Tuesday, July 17, 2012 4:01 AM
To: Liu Qiang-B32616
Cc: linux-crypto@vger.kernel.org; linuxppc-dev@lists.ozlabs.org;
Phillips
quoted
quoted
Kim-R1AAHA; herbert@gondor.hengli.com.au; davem@davemloft.net; Dan
Williams; Vinod Koul; Li Yang-R58472
Subject: Re: [PATCH v3 3/4] fsl-dma: change release process of dma
descriptor for supporting async_tx
On Mon, Jul 16, 2012 at 12:08:29PM +0800, Qiang Liu wrote:
quoted
Fix the potential risk when enable config NET_DMA and ASYNC_TX.
Async_tx is lack of support in current release process of dma
descriptor, all descriptors will be released whatever is acked or
no-acked by async_tx, so there is a potential race condition when
dma
quoted
quoted
quoted
engine is uesd by others clients (e.g. when enable NET_DMA to
offload
quoted
quoted
TCP).
quoted
In our case, a race condition which is raised when use both of
talitos
quoted
quoted
quoted
and dmaengine to offload xor is because napi scheduler will sync
all
quoted
quoted
quoted
pending requests in dma channels, it affects the process of raid
operations due to ack_tx is not checked in fsl dma. The no-acked
descriptor is freed which is submitted just now, as a dependent tx,
this freed descriptor trigger
BUG_ON(async_tx_test_ack(depend_tx)) in async_tx_submit().
Cc: Dan Williams <redacted>
Cc: Vinod Koul <redacted>
Cc: Li Yang <redacted>
Cc: Ira W. Snyder <redacted>
Signed-off-by: Qiang Liu <redacted>
---
drivers/dma/fsldma.c | 378 +++++++++++++++++++++++++++++---------
+ * handler will start any queued transactions when it runs
after
quoted
quoted
quoted
+ * this transaction finishes
+ */
+ if (!chan->idle) {
+ chan_dbg(chan, "DMA controller still busy\n");
+ return;
+ }
+
+ /*
+ * If there are some link descriptors which have not been
+ * transferred, we need to start the controller
+ */
+
+ /*
+ * Move all elements from the queue of pending transactions
+ * onto the list of running transactions
+ */
+ chan_dbg(chan, "idle, starting controller\n");
+ desc =3D list_first_entry(&chan->ld_pending, struct fsl_desc_sw,
node);
quoted
+ list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
+
+ /*
+ * The 85xx DMA controller doesn't clear the channel start
bit
quoted
quoted
quoted
+ * automatically at the end of a transfer. Therefore we must
clear
quoted
quoted
quoted
+ * it in software before starting the transfer.
+ */
+ if ((chan->feature & FSL_DMA_IP_MASK) =3D=3D FSL_DMA_IP_85XX) {
+ u32 mode;
+
+ mode =3D DMA_IN(chan, &chan->regs->mr, 32);
+ mode &=3D ~FSL_DMA_MR_CS;
+ DMA_OUT(chan, &chan->regs->mr, mode, 32);
+ }
+
+ /*
+ * Program the descriptor's address into the DMA controller,
+ * then start the DMA transaction
+ */
+ set_cdar(chan, desc->async_tx.phys);
+ get_cdar(chan);
+
+ dma_start(chan);
+ chan->idle =3D false;
+}
+
Please add a note about the locking requirements here, and for the
other
quoted
quoted
new functions you've added.
You call this function from two places:
1) fsldma_cleanup_descriptor() - called with mod->desc_lock held
2) fsl_tx_status() - WITHOUT mod->desc_lock held
One of them is definitely wrong, and I'd bet that it is #2. You're
modifying ld_completed without a lock.
Yes, My bad, I will correct it.
quoted
quoted
+static int
+fsldma_clean_completed_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_completed,
node) {
quoted
quoted
quoted
+
+ if (async_tx_test_ack(&desc->async_tx)) {
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p free\n", desc); #endif
+ dma_pool_free(chan->desc_pool, desc,
+ desc->async_tx.phys);
+ }
+ }
+
+ return 0;
+}
+
+/**
+ * fsldma_run_tx_complete_actions - cleanup and free a single link
+descriptor
+ * @chan: Freescale DMA channel
+ * @desc: descriptor to cleanup and free
+ * @cookie: Freescale DMA transaction identifier
+ *
+ * This function is used on a descriptor which has been executed
by
quoted
quoted
quoted
+the DMA
+ * controller. It will run any callbacks, submit any dependencies,
+and then
+ * free the descriptor.
+ */
+static dma_cookie_t fsldma_run_tx_complete_actions(struct
fsl_desc_sw
quoted
quoted
*desc,
quoted
+ struct fsldma_chan *chan, dma_cookie_t cookie) {
+ struct dma_async_tx_descriptor *txd =3D &desc->async_tx;
+ struct device *dev =3D chan->common.device->dev;
+ dma_addr_t src =3D get_desc_src(chan, desc);
+ dma_addr_t dst =3D get_desc_dst(chan, desc);
+ u32 len =3D get_desc_cnt(chan, desc);
+
+ BUG_ON(txd->cookie < 0);
+
+ if (txd->cookie > 0) {
+ cookie =3D txd->cookie;
+
+ /* Run the link descriptor callback function */
+ if (txd->callback) {
+#ifdef FSL_DMA_LD_DEBUG
+ chan_dbg(chan, "LD %p callback\n", desc); #endif
+ txd->callback(txd->callback_param);
+ }
+
+ /* Unmap the dst buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
+ if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
+ dma_unmap_single(dev, dst, len,
DMA_FROM_DEVICE);
quoted
quoted
quoted
+ else
+ dma_unmap_page(dev, dst, len,
DMA_FROM_DEVICE);
quoted
quoted
quoted
+ }
+
+ /* Unmap the src buffer, if requested */
+ if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
+ if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
+ dma_unmap_single(dev, src, len,
DMA_TO_DEVICE);
quoted
quoted
quoted
+ else
+ dma_unmap_page(dev, src, len,
DMA_TO_DEVICE);
quoted
quoted
quoted
+ }
+ }
+
+ /* Run any dependencies */
+ dma_run_dependencies(txd);
+
+ return cookie;
+}
+
+static int
+fsldma_clean_running_descriptor(struct fsl_desc_sw *desc,
+ struct fsldma_chan *chan)
+{
+ /* Remove from the list of transactions */
+ list_del(&desc->node);
+ /* the client is allowed to attach dependent operations
+ * until 'ack' is set
+ */
This comment is does not follow the coding style. It should be:
/*
* the client is allowed to attech dependent operations
* until 'ack' is set
*/
Fine, I will correct it in v4. Include another 2 places related to
coding style.
quoted
Thanks.
quoted
quoted
+ if (!async_tx_test_ack(&desc->async_tx)) {
+ /* move this slot to the completed */
Perhaps a better comment would be:
Move this descriptor to the list of descriptors which is complete,
This should all be on one line. It is less than 80 characters wide.
Accept.
quoted
quoted
+ return 0;
+}
+
Locking notes please.
I will add it in v4, please check. Thanks.
quoted
quoted
+static void fsldma_cleanup_descriptor(struct fsldma_chan *chan) {
+ struct fsl_desc_sw *desc, *_desc;
+ dma_cookie_t cookie =3D 0;
+ dma_addr_t curr_phys =3D get_cdar(chan);
+ int idle =3D dma_is_idle(chan);
+ int seen_current =3D 0;
+
+ fsldma_clean_completed_descriptor(chan);
+
+ /* Run the callback for each descriptor, in order */
+ list_for_each_entry_safe(desc, _desc, &chan->ld_running, node)
{
quoted
quoted
quoted
+ /* do not advance past the current descriptor loaded
into the
quoted
quoted
quoted
+ * hardware channel, subsequent descriptors are either
in
quoted
quoted
quoted
+ * process or have not been submitted
+ */
Coding style.
quoted
+ if (seen_current)
+ break;
+
+ /* stop the search if we reach the current descriptor
and the
quoted
quoted
quoted
+ * channel is busy
+ */
Coding style.
quoted
+ if (desc->async_tx.phys =3D=3D curr_phys) {
+ seen_current =3D 1;
+ if (!idle)
+ break;
+ }
+
This trick where you try to look at the hardware state to determine
how
quoted
quoted
much to clean up has been a source of headaches in the past versions
of
quoted
quoted
this driver.
I know a little about the history of this driver. Could you tell me
what kind
quoted
headaches in the past versions, I can have a test and fix it in my
patch. And
quoted
I also think use current phys addr should be more explicit.
Thanks.
=20
It has been a very long time since I last worked on this code, but I
will try to remember.
=20
I remember one problem where the currently running descriptor was free'd
while the hardware was still executing it.
=20
There was another related problem where the DMA hardware would lock up,
and it is impossible to recover without a hard reset. The CB (channel
busy) bit gets stuck on, and the running transfer never completes. This
may have been due to a programming issue in a user of the DMAEngine API,
and not this driver itself. I don't remember for sure anymore.
=20
Our current system here at work has 120 boards with this DMA controller.
Each one runs 100+ DMA operations per second, 24/7/365. They've been
online for more than two years. I know for sure that the current code
doesn't lock up the DMA controller. :)
=20
I think your bug is real, and needs to be fixed. I'm just trying to make
sure I understand the change, so it won't break other users. I'm only
trying to help.
Thanks for your information. I will do more explanation of my idea in the
following answer.
Could you provide some sample code for reproduce bug, I don't know dmatest.=
c
whether is enough. I will add dma self test in fsldma.c.
=20
quoted
quoted
It is much easier to reason about the state of the hardware and avoid
race conditions if you complete entire blocks of descriptors after
the
quoted
quoted
hardware interrupts you to tell you it is finished.
In current driver, it's ok, but there is a potential issue when enable
async_tx api. How can you determine these descriptors in ld_running
whether
quoted
have been completed in fsl_tx_status()? (I mean in my patch.)
=20
I think your idea using an ld_completed list for descriptors which have
been run by the hardware, but not yet 'ack'ed by software is fine.
=20
Would something similar to the following work?
=20
ld_pending: build a list of descriptors until issue_pending() is called.
This is exactly what it does now, no changes needed.
Yes, no changes.
=20
ld_running: this list of descriptors is currently executing. Mostly
unchanged from how it works now.
Yes, no changes.
I will add descriptions about all new interfaces.
=20
When you get an interrupt, you know the descriptors in ld_running are
finished. Update the cookie to the highest number from ld_running. Free
the descriptors which have been 'ack'ed immediately. Move the ones which
are not 'ack'ed onto ld_completed. As part of this process, you should
run dma_run_dependencies() and callbacks as needed.
Right, below is new implement of dma_do_tasklet();
First, dma_do_tasklet()
-> fsldma_cleanup_descriptor()
-> fsldma_clean_completed_descriptor(), free the descriptors which has be=
en ack'ed (I mean in queue ld_completed, not include other queues);
Second, transverse the queue ld_running
-> fsldma_run_tx_complete_actions(), find the last descriptor which is com=
pleted, update the cookie to the highest number, run callback, unmap dma pa=
ges, and run dma_run_dependencies();
-> fsldma_clean_running_descriptor(), move this descriptor from ld_running=
to ld_completed.
Last,
-> fsl_chan_xfer_ld_queue(), submit much more descriptors from ld_pending =
to ld_running.
I hope my description is clear enough.
=20
I think that this solves the problem you are seeing, which is that
descriptors which have not been 'ack'ed are free'd.
=20
If this is unclear, I can write some code to demonstrate. If you could
write a small test driver, similar to drivers/dma/dmatest.c, which tests
the async_tx API without any extra hardware needed, I can run it. I have
never used the async_tx API before.
Your description is clear, I agree with you, I will add fsldma self test in
the file.
=20
quoted
quoted
This is the philosophy employed by the driver before your
modifications:
quoted
quoted
ld_pending: a block of descriptors which is ready to run as soon as
the
quoted
quoted
hardware becomes idle.
ld_running: a block of descriptors which is being executed by the
hardware.
These 2 lists are not enough, async_tx descriptors must be kept order
as
quoted
expected of its submitter, we only can process the descriptor which has
been
quoted
acked by async_tx api, but not free all descriptors in ld_running.
For example,
Step 1, in async_tx memcpy api,
tx2 =3D device->device_prep_dma_memcpy(...),
tx2->depend_tx =3D tx1;
step 2, in async_tx submit api,
async_tx_submit() will check tx2->depend_tx whether has been acked,
unfortunately, tx2->depend_tx is freed before step 2 (dma channels is
flushed
quoted
by other drivers), the contents of tx2->depend_tx is set to
POOL_POISON_FREED
quoted
if DMAPOOL_DEBUG is enabled (illegal pointer will be used if disable
this config
quoted
option);
step 3, BUG_ON(async_tx_test_ack(depend_tx)) is triggered.
For resolve this potential risk, first, ack flag must be checked in dma
driver,
quoted
second, ld_completed is added to restore all descriptors which have
been acked
quoted
and completed.
In my following answer, most of all are around this idea.
+
+ if (fsldma_clean_running_descriptor(desc, chan))
+ break;
+
+ }
+
+ /*
+ * Start any pending transactions automatically
+ *
+ * In the ideal case, we keep the DMA controller busy while
we go
quoted
quoted
quoted
+ * ahead and free the descriptors below.
+ */
+ fsl_chan_xfer_ld_queue(chan);
+
+ if (cookie > 0)
+ chan->common.completed_cookie =3D cookie; }
+
static dma_cookie_t fsl_dma_tx_submit(struct
@@ -811,124 +1024,6 @@ static int fsl_dma_device_control(struct
dma_chan *dchan, }
/**
- * fsldma_cleanup_descriptor - cleanup and free a single link
descriptor
- * @chan: Freescale DMA channel
- * @desc: descriptor to cleanup and free
- *
- * This function is used on a descriptor which has been executed
by
quoted
quoted
quoted
the DMA
- * controller. It will run any callbacks, submit any dependencies,
and then
- * free the descriptor.
- */
-static void fsldma_cleanup_descriptor(struct fsldma_chan *chan,
- struct fsl_desc_sw *desc)
-{
- struct dma_async_tx_descriptor *txd =3D &desc->async_tx;
- struct device *dev =3D chan->common.device->dev;
- dma_addr_t src =3D get_desc_src(chan, desc);
- dma_addr_t dst =3D get_desc_dst(chan, desc);
- u32 len =3D get_desc_cnt(chan, desc);
-
- /* Run the link descriptor callback function */
- if (txd->callback) {
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p callback\n", desc);
-#endif
- txd->callback(txd->callback_param);
- }
-
- /* Run any dependencies */
- dma_run_dependencies(txd);
-
- /* Unmap the dst buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_DEST_UNMAP)) {
- if (txd->flags & DMA_COMPL_DEST_UNMAP_SINGLE)
- dma_unmap_single(dev, dst, len, DMA_FROM_DEVICE);
- else
- dma_unmap_page(dev, dst, len, DMA_FROM_DEVICE);
- }
-
- /* Unmap the src buffer, if requested */
- if (!(txd->flags & DMA_COMPL_SKIP_SRC_UNMAP)) {
- if (txd->flags & DMA_COMPL_SRC_UNMAP_SINGLE)
- dma_unmap_single(dev, src, len, DMA_TO_DEVICE);
- else
- dma_unmap_page(dev, src, len, DMA_TO_DEVICE);
- }
-
-#ifdef FSL_DMA_LD_DEBUG
- chan_dbg(chan, "LD %p free\n", desc);
-#endif
- dma_pool_free(chan->desc_pool, desc, txd->phys);
-}
-
-/**
- * fsl_chan_xfer_ld_queue - transfer any pending transactions
- * @chan : Freescale DMA channel
- *
- * HARDWARE STATE: idle
- * LOCKING: must hold chan->desc_lock
- */
-static void fsl_chan_xfer_ld_queue(struct fsldma_chan *chan) -{
- struct fsl_desc_sw *desc;
-
- /*
- * If the list of pending descriptors is empty, then we
- * don't need to do any work at all
- */
- if (list_empty(&chan->ld_pending)) {
- chan_dbg(chan, "no pending LDs\n");
- return;
- }
-
- /*
- * The DMA controller is not idle, which means that the
interrupt
quoted
quoted
quoted
- * handler will start any queued transactions when it runs
after
quoted
quoted
quoted
- * this transaction finishes
- */
- if (!chan->idle) {
- chan_dbg(chan, "DMA controller still busy\n");
- return;
- }
-
- /*
- * If there are some link descriptors which have not been
- * transferred, we need to start the controller
- */
-
- /*
- * Move all elements from the queue of pending transactions
- * onto the list of running transactions
- */
- chan_dbg(chan, "idle, starting controller\n");
- desc =3D list_first_entry(&chan->ld_pending, struct fsl_desc_sw,
node);
quoted
- list_splice_tail_init(&chan->ld_pending, &chan->ld_running);
-
- /*
- * The 85xx DMA controller doesn't clear the channel start
bit
quoted
quoted
quoted
- * automatically at the end of a transfer. Therefore we must
clear
quoted
quoted
quoted
- * it in software before starting the transfer.
- */
- if ((chan->feature & FSL_DMA_IP_MASK) =3D=3D FSL_DMA_IP_85XX) {
- u32 mode;
-
- mode =3D DMA_IN(chan, &chan->regs->mr, 32);
- mode &=3D ~FSL_DMA_MR_CS;
- DMA_OUT(chan, &chan->regs->mr, mode, 32);
- }
-
- /*
- * Program the descriptor's address into the DMA controller,
- * then start the DMA transaction
- */
- set_cdar(chan, desc->async_tx.phys);
- get_cdar(chan);
-
- dma_start(chan);
- chan->idle =3D false;
-}
-
-/**
* fsl_dma_memcpy_issue_pending - Issue the DMA start command
* @chan : Freescale DMA channel
*/
You've made status from a very quick operation (compare two cookies)
into
quoted
quoted
a potentially long running operation. It may now run callbacks, unmap
pages, etc.
Yes, that's right, callbacks and unmap pages will be invoked if DMA
status
quoted
is not DMA_SUCCESS.
quoted
I note that Documentation/crypto/async-tx-api.txt section 3.6
"Constraints" does say that async_*() functions cannot be called from
IRQ
quoted
quoted
context. However, the DMAEngine API itself does not have anything to
say
quoted
quoted
about IRQ context.
I expect fsl_tx_status() to be quick, and not potentially call other
arbitrary code.
fsl_tx_status() is not in IRQ context. It's reasonable to unmap pages
and
quoted
run dependency of descriptor as fsldma_run_tx_complete_actions() does.
=20
I looked at several other DMAEngine API drivers. Some of them do run
dependencies and callbacks from tx_status(). You are correct, this is
fine.
=20
quoted
quoted
Is it possible to leave this function unchanged?
According to my knowledge, it is unlikely to be left unchanged, or it
will violate
quoted
the design of this interface. If DMA status is not DMA_SUCCESS, that
means there
quoted
are new descriptors completed, we should move them to ld_completed, and
do actions
quoted
to its async_tx descriptors, then dma descriptor will be freed at
another time.
quoted
Most of my idea is from iop-adma.c, the original interface is not align
with it.
quoted
Async_tx flags (expecially ack_test) is not considered when dma
descriptor is freed,
quoted
so some random errors happened, I think you must familiar with this
history.
quoted
As an important "synchronization flag", async_tx api must control the
order of tx
quoted
descriptor. Dma driver also should make sure keeping order when free
the descriptor.
quoted
That's the reason why I add ld_completed list.
=20
Is it possible to put the descriptors into three different states?
=20
1) ld_pending: ready to run, but not yet executed on the hardware
=20
Descriptors move to #2 through either dma_async_issue_pending() or by
the interrupt which happens when the hardware completes executing a set
of DMA descriptors.
=20
2) ld_running: currently executing on the hardware
=20
Descriptors move to #3 through the interrupt which happens when the
hardware completes executing a set of DMA descriptors.
=20
Dependencies and callbacks are executed as the descriptors are moved
onto ld_completed.
=20
3) ld_completed: finished executing on the hardware, but not yet 'ack'ed
=20
When they have been 'ack'ed, the descriptors are free'd.
=20
=20
As noted above, I think I could code this up fairly quickly if this
explanation is unclear.
Totally right. I think you understand my idea.
=20
Also note that I may not understand your bug completely, and my idea may
be completely wrong!
I hope you've already understand my issue:)
Thanks.
=20
Ira
=20
quoted
quoted
Also note that if you leave this function unchanged, the locking
error
quoted
quoted
pointed out above (fsldma_clean_completed_descriptor() is not called
--------*/ @@ -1035,53 +1136,21 @@ static irqreturn_t
fsldma_chan_irq(int irq, void *data) static void
dma_do_tasklet(unsigned long data) {
struct fsldma_chan *chan =3D (struct fsldma_chan *)data;
- struct fsl_desc_sw *desc, *_desc;
- LIST_HEAD(ld_cleanup);
unsigned long flags;
chan_dbg(chan, "tasklet entry\n");
spin_lock_irqsave(&chan->desc_lock, flags);
- /* update the cookie if we have some descriptors to cleanup
*/
quoted
quoted
quoted
- if (!list_empty(&chan->ld_running)) {
- dma_cookie_t cookie;
-
- desc =3D to_fsl_desc(chan->ld_running.prev);
- cookie =3D desc->async_tx.cookie;
- dma_cookie_complete(&desc->async_tx);
-
- chan_dbg(chan, "completed_cookie=3D%d\n", cookie);
- }
-
- /*
- * move the descriptors to a temporary list so we can drop
the lock
quoted
quoted
quoted
- * during the entire cleanup operation
- */
- list_splice_tail_init(&chan->ld_running, &ld_cleanup);
+ /* Run all cleanup for this descriptor */
+ fsldma_cleanup_descriptor(chan);
/* the hardware is now idle and ready for more */
chan->idle =3D true;
- /*
- * Start any pending transactions automatically
- *
- * In the ideal case, we keep the DMA controller busy while
we go
quoted
quoted
quoted
- * ahead and free the descriptors below.
- */
fsl_chan_xfer_ld_queue(chan);
spin_unlock_irqrestore(&chan->desc_lock, flags);
- /* Run the callback for each descriptor, in order */
- list_for_each_entry_safe(desc, _desc, &ld_cleanup, node) {
-
- /* Remove from the list of transactions */
- list_del(&desc->node);
-
- /* Run all cleanup for this descriptor */
- fsldma_cleanup_descriptor(chan, desc);
- }
-
chan_dbg(chan, "tasklet exit\n");
}