Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
In-Reply-To: <20230803042738.5937-1-parri.andrea@gmail.com>
References: <20230803042738.5937-1-parri.andrea@gmail.com>
Subject: Re: [PATCH v2] riscv,mmio: Fix readX()-to-delay() ordering
Message-Id: <169169664358.3729.13203537465035049812.b4-ty@rivosinc.com>
Date:   Thu, 10 Aug 2023 12:44:03 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Cc:     linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     Paul Walmsley <paul.walmsley@sifive.com>,
        Palmer Dabbelt <palmer@dabbelt.com>, aou@eecs.berkeley.edu,
        Andrea Parri <parri.andrea@gmail.com>
Precedence: bulk


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@rivosinc.com>