[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNMnA0VtExcvpV=Sr57RQ3xxVkHxhrTkvEKeHZ27bhud+w@mail.gmail.com>
Date: Fri, 17 Jun 2022 12:18:41 +0200
From: Marco Elver <elver@...gle.com>
To: paulmck@...nel.org
Cc: Kefeng Wang <wangkefeng.wang@...wei.com>, catalin.marinas@....com,
will@...nel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, mark.rutland@....com,
Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
arnd@...db.de, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v4 1/2] asm-generic: Add memory barrier dma_mb()
On Fri, 17 Jun 2022 at 01:13, Paul E. McKenney <paulmck@...nel.org> wrote:
>
> On Mon, May 23, 2022 at 01:35:27PM +0200, Marco Elver wrote:
> > On Mon, 23 May 2022 at 13:21, Kefeng Wang <wangkefeng.wang@...wei.com> wrote:
> > >
> > > The memory barrier dma_mb() is introduced by commit a76a37777f2c
> > > ("iommu/arm-smmu-v3: Ensure queue is read after updating prod pointer"),
> > > which is used to ensure that prior (both reads and writes) accesses
> > > to memory by a CPU are ordered w.r.t. a subsequent MMIO write.
> > >
> > > Reviewed-by: Arnd Bergmann <arnd@...db.de> # for asm-generic
> > > Signed-off-by: Kefeng Wang <wangkefeng.wang@...wei.com>
> >
> > Reviewed-by: Marco Elver <elver@...gle.com>
>
> Just checking... Did these ever get picked up? It was suggested
> that they go up via the arm64 tree, if I remember correctly.
I don't see them in -next, and as far as I can tell, they're not in
the arm64 tree.
Thanks,
-- Marco
Powered by blists - more mailing lists