From: Catalin Marinas <catalin.marinas@arm.com>
To: Barry Song <21cnbao@gmail.com>
Cc: Tangquan Zheng <zhengtangquan@oppo.com>,
Barry Song <baohua@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Leon Romanovsky <leon@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
robin.murphy@arm.com, Xueyuan Chen <xueyuan.chen21@gmail.com>,
linux-kernel@vger.kernel.org,
Suren Baghdasaryan <surenb@google.com>,
iommu@lists.linux.dev, Marc Zyngier <maz@kernel.org>,
will@kernel.org, Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org, m.szyprowski@samsung.com
Subject: Re: [PATCH v3 1/5] arm64: Provide dcache_by_myline_op_nosync helper
Date: Fri, 13 Mar 2026 19:35:08 +0000 [thread overview]
Message-ID: <abRm7DPWntjBB7Ji@arm.com> (raw)
In-Reply-To: <20260228221216.59886-1-21cnbao@gmail.com>
On Sun, Mar 01, 2026 at 06:12:16AM +0800, Barry Song wrote:
> From: Barry Song <baohua@kernel.org>
>
> dcache_by_myline_op ensures completion of the data cache operations for a
> region, while dcache_by_myline_op_nosync only issues them without waiting.
> This enables deferred synchronization so completion for multiple regions
> can be handled together later.
>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Anshuman Khandual <anshuman.khandual@arm.com>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: Suren Baghdasaryan <surenb@google.com>
> Cc: Tangquan Zheng <zhengtangquan@oppo.com>
> Tested-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
> Signed-off-by: Barry Song <baohua@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Barry Song <21cnbao@gmail.com>
Cc: m.szyprowski@samsung.com, robin.murphy@arm.com, will@kernel.org,
iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Barry Song <baohua@kernel.org>,
Leon Romanovsky <leon@kernel.org>,
Ada Couprie Diaz <ada.coupriediaz@arm.com>,
Ard Biesheuvel <ardb@kernel.org>, Marc Zyngier <maz@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Suren Baghdasaryan <surenb@google.com>,
Tangquan Zheng <zhengtangquan@oppo.com>,
Xueyuan Chen <xueyuan.chen21@gmail.com>
Subject: Re: [PATCH v3 1/5] arm64: Provide dcache_by_myline_op_nosync helper
Date: Fri, 13 Mar 2026 19:35:08 +0000 [thread overview]
Message-ID: <abRm7DPWntjBB7Ji@arm.com> (raw)
In-Reply-To: <20260228221216.59886-1-21cnbao@gmail.com>
On Sun, Mar 01, 2026 at 06:12:16AM +0800, Barry Song wrote:
> From: Barry Song <baohua@kernel.org>
>
> dcache_by_myline_op ensures completion of the data cache operations for a
> region, while dcache_by_myline_op_nosync only issues them without waiting.
> This enables deferred synchronization so completion for multiple regions
> can be handled together later.
>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Marek Szyprowski <m.szyprowski@samsung.com>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Ada Couprie Diaz <ada.coupriediaz@arm.com>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Anshuman Khandual <anshuman.khandual@arm.com>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: Suren Baghdasaryan <surenb@google.com>
> Cc: Tangquan Zheng <zhengtangquan@oppo.com>
> Tested-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
> Signed-off-by: Barry Song <baohua@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2026-03-13 19:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260228221143eucas1p12a276d4216b6ce0f3c374b093f73acd5@eucas1p1.samsung.com>
2026-02-28 22:11 ` [PATCH v3 0/5] dma-mapping: arm64: support batched cache sync Barry Song
2026-02-28 22:11 ` Barry Song
2026-02-28 22:12 ` [PATCH v3 1/5] arm64: Provide dcache_by_myline_op_nosync helper Barry Song
2026-02-28 22:12 ` Barry Song
2026-03-13 19:35 ` Catalin Marinas [this message]
2026-03-13 19:35 ` Catalin Marinas
2026-02-28 22:12 ` [PATCH v3 2/5] arm64: Provide dcache_clean_poc_nosync helper Barry Song
2026-02-28 22:12 ` Barry Song
2026-03-13 19:35 ` Catalin Marinas
2026-03-13 19:35 ` Catalin Marinas
2026-02-28 22:12 ` [PATCH v3 3/5] arm64: Provide dcache_inval_poc_nosync helper Barry Song
2026-02-28 22:12 ` Barry Song
2026-03-13 19:35 ` Catalin Marinas
2026-03-13 19:35 ` Catalin Marinas
2026-03-03 16:33 ` [PATCH v3 0/5] dma-mapping: arm64: support batched cache sync Marek Szyprowski
2026-03-03 16:33 ` Marek Szyprowski
2026-03-13 19:36 ` Catalin Marinas
2026-03-13 19:36 ` Catalin Marinas
2026-03-16 7:24 ` Marek Szyprowski
2026-03-16 7:24 ` Marek Szyprowski
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=abRm7DPWntjBB7Ji@arm.com \
--to=catalin.marinas@arm.com \
--cc=21cnbao@gmail.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=baohua@kernel.org \
--cc=iommu@lists.linux.dev \
--cc=leon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=will@kernel.org \
--cc=xueyuan.chen21@gmail.com \
--cc=zhengtangquan@oppo.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 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.