From: Christoph Hellwig <hch@lst.de>
To: Will Deacon <will@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-arch@vger.kernel.org, catalin.marinas@arm.com,
maz@kernel.org, mark.rutland@arm.com, robin.murphy@arm.com,
vgupta@kernel.org, linux@armlinux.org.uk, arnd@arndb.de,
bcain@quicinc.com, geert@linux-m68k.org, monstr@monstr.eu,
dinguyen@kernel.org, shorne@gmail.com, mpe@ellerman.id.au,
dalias@libc.org
Subject: Re: Cache maintenance for non-coherent DMA in arch_sync_dma_for_device()
Date: Thu, 9 Jun 2022 16:18:38 +0200 [thread overview]
Message-ID: <20220609141838.GA1829@lst.de> (raw)
In-Reply-To: <20220609135954.GC3064@willie-the-truck>
On Thu, Jun 09, 2022 at 02:59:54PM +0100, Will Deacon wrote:
> That makes sense to me (assuming an opt-out for archs that want it), but
> I'd like to make sure that these low-level helpers aren't generally
> available for e.g. driver modules to dip into directly; it's pretty common
> for folks to request that we EXPORT our cache maintenance routines because
> they're violating the DMA API someplace and so far we've been pretty good
> at asking them to fix their code instead.
Yes, they have absolutely no business being available to drivers
directly.
prev parent reply other threads:[~2022-06-09 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:21 Cache maintenance for non-coherent DMA in arch_sync_dma_for_device() Will Deacon
2022-06-06 15:35 ` Russell King (Oracle)
2022-06-06 16:02 ` Robin Murphy
2022-06-06 16:16 ` Russell King (Oracle)
2022-06-08 8:49 ` Christoph Hellwig
2022-06-06 16:13 ` Catalin Marinas
2022-06-06 16:15 ` Ard Biesheuvel
2022-06-08 16:51 ` Catalin Marinas
2022-06-08 8:48 ` Christoph Hellwig
2022-06-08 12:02 ` Russell King (Oracle)
2022-06-08 15:14 ` Christoph Hellwig
2022-06-09 13:59 ` Will Deacon
2022-06-09 14:18 ` Christoph Hellwig [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=20220609141838.GA1829@lst.de \
--to=hch@lst.de \
--cc=arnd@arndb.de \
--cc=bcain@quicinc.com \
--cc=catalin.marinas@arm.com \
--cc=dalias@libc.org \
--cc=dinguyen@kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=monstr@monstr.eu \
--cc=mpe@ellerman.id.au \
--cc=robin.murphy@arm.com \
--cc=shorne@gmail.com \
--cc=vgupta@kernel.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.