From: Vinod Koul <vkoul@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: dmaengine@vger.kernel.org,
Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
Dave Jiang <dave.jiang@intel.com>, Frank Li <Frank.Li@kernel.org>,
Kelvin Cao <kelvin.cao@microchip.com>,
Logan Gunthorpe <logang@deltatee.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>
Subject: Re: [PATCH 0/8] dmaengine: unmap descriptor before completing cookie
Date: Sat, 17 Oct 2026 10:57:27 +0100 [thread overview]
Message-ID: <atNGh7mCjGJ9rgPt@parshuram> (raw)
In-Reply-To: <asy5hLkzZARvkKyD@shikoro>
On 12-10-26, 12:42, Wolfram Sang wrote:
>
> > We found out that we need to unmap descriptors before completing a
> > cookie [1]. Fix the drivers for which this is a no-brainer and just
> > switches those two function calls.
>
> Okay, according to Sashiko, patches 1+5+6+7 are no no-brainers but need
> a deeper analysis which I am not able to provide.
>
> So, we could drop this series entirely because it seems more trustworthy
> to let people with actual hardware fix these issues. Maybe a FIXME could
> be added instead to these drivers.
>
> Or, we can apply at least patches 2+3+4+8 where Sashiko found no issues.
>
> I tend to use the first option but am open to whatever maintainers think
> about it.
yeah lets get some testing into these. I would hope people who care
about these would test this out... FIXME is fine too
Thanks
--
~Vinod
prev parent reply other threads:[~2026-10-17 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 12:43 [PATCH 0/8] dmaengine: unmap descriptor before completing cookie Wolfram Sang
2026-10-10 12:43 ` [PATCH 1/8] dmaengine: ptdma: " Wolfram Sang
2026-10-10 12:57 ` sashiko-bot
2026-10-12 14:51 ` Frank Li
2026-10-10 12:43 ` [PATCH 2/8] dmaengine: fsl_raid: " Wolfram Sang
2026-10-10 12:43 ` [PATCH 3/8] dmaengine: idxd: " Wolfram Sang
2026-10-13 22:54 ` Vinicius Costa Gomes
2026-10-10 12:43 ` [PATCH 4/8] dmaengine: ioat: " Wolfram Sang
2026-10-10 12:43 ` [PATCH 5/8] dmaengine: mv_xor_v2: " Wolfram Sang
2026-10-10 12:54 ` sashiko-bot
2026-10-10 12:43 ` [PATCH 6/8] dmaengine: plx_dma: " Wolfram Sang
2026-10-10 12:56 ` sashiko-bot
2026-10-13 20:06 ` Logan Gunthorpe
2026-10-10 12:43 ` [PATCH 7/8] dmaengine: switchtec-dma: " Wolfram Sang
2026-10-10 12:54 ` sashiko-bot
2026-10-13 20:06 ` Logan Gunthorpe
2026-10-10 12:43 ` [PATCH 8/8] dmaengine: xgene-dma: " Wolfram Sang
2026-10-12 10:42 ` [PATCH 0/8] dmaengine: " Wolfram Sang
2026-10-17 9:57 ` Vinod Koul [this message]
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=atNGh7mCjGJ9rgPt@parshuram \
--to=vkoul@kernel.org \
--cc=Basavaraj.Natikar@amd.com \
--cc=Frank.Li@kernel.org \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kelvin.cao@microchip.com \
--cc=logang@deltatee.com \
--cc=vinicius.gomes@intel.com \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox