[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169169664358.3729.13203537465035049812.b4-ty@rivosinc.com>
Date: Thu, 10 Aug 2023 12:44:03 -0700
From: Palmer Dabbelt <palmer@...osinc.com>
To: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>, aou@...s.berkeley.edu,
Andrea Parri <parri.andrea@...il.com>
Cc: linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] riscv,mmio: Fix readX()-to-delay() ordering
On Thu, 03 Aug 2023 06:27:38 +0200, Andrea Parri wrote:
> Section 2.1 of the Platform Specification [1] states:
>
> Unless otherwise specified by a given I/O device, I/O devices are on
> ordering channel 0 (i.e., they are point-to-point strongly ordered).
>
> which is not sufficient to guarantee that a readX() by a hart completes
> before a subsequent delay() on the same hart (cf. memory-barriers.txt,
> "Kernel I/O barrier effects").
>
> [...]
Applied, thanks!
[1/1] riscv,mmio: Fix readX()-to-delay() ordering
https://git.kernel.org/palmer/c/4eb2eb1b4c0e
Best regards,
--
Palmer Dabbelt <palmer@...osinc.com>
Powered by blists - more mailing lists