From: Chen Yu <yu.c.chen@intel.com>
To: Libing Lei <libing.lei@jaguarmicro.com>
Cc: <Eugeniy.Paltsev@synopsys.com>, <vkoul@kernel.org>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3] dmaengine: dw-axi-dmac: add spinlock for multi-channel DMA
Date: Fri, 7 Apr 2023 14:48:56 +0800 [thread overview]
Message-ID: <ZC+82NwoumBLYnml@chenyu5-mobl1> (raw)
In-Reply-To: <20230404153945.916-1-libing.lei@jaguarmicro.com>
On 2023-04-04 at 23:39:45 +0800, Libing Lei wrote:
> When multiple channels operate simultaneously, the common register shared
> by all channels could be set to an unexpected value due to race conditions
Does the channel mean the "chip" in the following patch? I mean, each channel
has 1 chip plugged in? I asked this question because I'm trying to figure out
the protection scope of the introduced spinlock.
> on SMP machines, resulting in a disaster that DMAC cannot work from then
> on:
>
> cpu0 cpu1
> dw_axi_dma_interrupt()
> axi_dma_irq_disable(chip)
> ...
> axi_chan_block_xfer_start()
> axi_dma_enable()
> val = axi_dma_ioread32(chip, DMAC_CFG)
> axi_dma_irq_enable(chip)
> axi_dma_iowrite32(chip, DMAC_CFG, val)
>
> As a result, the global interrupt enable bit INT_EN in the DMAC_CFG
> register is eventually cleared and the DMAC will no longer generates
> interrupts.
>
> The error scenario is as follows:
>
> [ 63.483688] dmatest: dma0chan1-copy: result #18: 'test timed out' with
> src_off=0xc2 dst_off=0x27b len=0x3a54 (0)
> [ 63.483693] dmatest: dma0chan2-copy: result #18: 'test timed out' with
> src_off=0x239 dst_off=0xfc9 len=0x213a (0)
> [ 63.483696] dmatest: dma0chan0-copy: result #19: 'test timed out' with
> src_off=0x5d1 dst_off=0x231 len=0x395e (0)
>
> a spinlock is added to fix it up.
>
Although it is unlikely to introduce ABBA lock, maybe enabling the
CONFIG_LOCKDEP to have a double check on this.
> Signed-off-by: Libing Lei <libing.lei@jaguarmicro.com>
The patch looks good to me.
thanks,
Chenyu
next prev parent reply other threads:[~2023-04-07 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 15:39 [PATCH V3] dmaengine: dw-axi-dmac: add spinlock for multi-channel DMA Libing Lei
2023-04-07 6:48 ` Chen Yu [this message]
2023-04-09 15:47 ` Libing Lei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZC+82NwoumBLYnml@chenyu5-mobl1 \
--to=yu.c.chen@intel.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=dmaengine@vger.kernel.org \
--cc=libing.lei@jaguarmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox