From: Christoph Hellwig <hch@lst.de>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
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, 7 Sep 2022 11:04:34 +0200 [thread overview]
Message-ID: <20220907090434.GB30704@lst.de> (raw)
In-Reply-To: <YwafYihD+Fnuuzaj@arm.com>
On Wed, Aug 24, 2022 at 11:00:02PM +0100, Catalin Marinas wrote:
> (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)
The memory is zerod after arch_dma_prep_coherent. So a pure invalidate
seems like the right thing to do here.
_______________________________________________
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-09-07 9:14 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
2022-09-07 9:04 ` Christoph Hellwig [this message]
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=20220907090434.GB30704@lst.de \
--to=hch@lst.de \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--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).