Re: [PATCH v3 0/3] RISC-V: Ensure Zicbom has a valid block size - patchwork-bot+linux-riscv

From: patchwork-bot+linux-riscv@kernel.org
To: Andrew Jones <ajones@ventanamicro.com>
Cc: linux-riscv@lists.infradead.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	conor.dooley@microchip.com, heiko@sntech.de,
	apatel@ventanamicro.com, atishp@rivosinc.com
Subject: Re: [PATCH v3 0/3] RISC-V: Ensure Zicbom has a valid block size
Date: Fri, 09 Dec 2022 22:30:17 +0000	[thread overview]
Message-ID: <167062501746.3088.13063280790225807236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221129143447.49714-1-ajones@ventanamicro.com>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Tue, 29 Nov 2022 15:34:44 +0100 you wrote:
> When a DT puts zicbom in the isa string, but does not provide a block
> size, ALT_CMO_OP() will attempt to do cache operations on address
> zero since the start address will be ANDed with zero. We can't simply
> BUG() in riscv_init_cbom_blocksize() when we fail to find a block
> size because the failure will happen before logging works, leaving
> users to scratch their heads as to why the boot hung. Instead, ensure
> Zicbom is disabled and output an error which will hopefully alert
> people that the DT needs to be fixed. While at it, add a check that
> the block size is a power-of-2 too.
> 
> [...]

Here is the summary with links:
  - [v3,1/3] RISC-V: Improve use of isa2hwcap[]
    https://git.kernel.org/riscv/c/78eda777d2f1
  - [v3,2/3] RISC-V: Introduce riscv_isa_extension_check
    https://git.kernel.org/riscv/c/132cfeb2b7fd
  - [v3,3/3] RISC-V: Ensure Zicbom has a valid block size
    https://git.kernel.org/riscv/c/68dc0718407d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv