From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] arm64: dma: Drop cache invalidation from arch_dma_prep_coherent()
Date: Wed, 24 Aug 2022 23:00:02 +0100 [thread overview]
Message-ID: <YwafYihD+Fnuuzaj@arm.com> (raw)
In-Reply-To: <20220823122111.17439-1-will@kernel.org>
On Tue, Aug 23, 2022 at 01:21:11PM +0100, Will Deacon wrote:
> arch_dma_prep_coherent() is called when preparing a non-cacheable region
> for a consistent DMA buffer allocation. Since the buffer pages may
> previously have been written via a cacheable mapping and consequently
> allocated as dirty cachelines, the purpose of this function is to remove
> these dirty lines from the cache, writing them back so that the
> non-coherent device is able to see them.
>
> On arm64, this operation can be achieved with a clean to the point of
> coherency; a subsequent invalidation is not required and serves little
> purpose in the presence of a cacheable alias (e.g. the linear map),
> since clean lines can be speculatively fetched back into the cache after
> the invalidation operation has completed.
>
> Relax the cache maintenance in arch_dma_prep_coherent() so that only a
> clean, and not a clean-and-invalidate operation is performed.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Signed-off-by: Will Deacon <will@kernel.org>
> ---
>
> I'm slightly wary about this change as other architectures seem to do
> clean+invalidate here, but I'd like to hear what others think in any
> case.
Given that we still have the cacheable alias around, I don't see much
point in the invalidation. So:
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
(I was wondering why not just invalidate without clean but it could be
that the allocated memory was zeroed and we want that to make it to the
PoC)
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-24 22:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 12:21 [PATCH] arm64: dma: Drop cache invalidation from arch_dma_prep_coherent() Will Deacon
2022-08-24 9:58 ` Ard Biesheuvel
2022-08-24 11:23 ` Will Deacon
2022-08-24 11:49 ` Ard Biesheuvel
2022-08-24 22:00 ` Catalin Marinas [this message]
2022-09-07 9:04 ` Christoph Hellwig
2022-09-07 14:10 ` Russell King (Oracle)
2022-09-07 14:14 ` Christoph Hellwig
2022-09-07 14:15 ` Russell King (Oracle)
2022-09-07 9:03 ` Christoph Hellwig
2022-09-07 9:27 ` Robin Murphy
2022-09-07 16:25 ` Will Deacon
2022-09-07 17:50 ` Robin Murphy
2022-09-08 10:32 ` Catalin Marinas
2022-09-08 11:32 ` Robin Murphy
2022-09-08 13:02 ` Catalin Marinas
2022-09-08 13:27 ` Catalin Marinas
2022-09-08 13:32 ` Will Deacon
2022-09-08 15:49 ` Catalin Marinas
2022-09-07 16:28 ` Will Deacon
2022-09-22 20:02 ` Catalin Marinas
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=YwafYihD+Fnuuzaj@arm.com \
--to=catalin.marinas@arm.com \
--cc=ardb@kernel.org \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).