3 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Radim KrčmářandAnup Patel	009f77a9f0	lib: sbi_hart: reset hstatus ... hstatus.HU must be cleared, because U-mode could otherwise use the HLS/HSV instructions. This would allow U-mode to read physical memory directly if vgatp and vsatp was 0. The remaining fields don't seem like a security vulnerability now, but clearing the whole CSR is not an issue, so do that be safe. Reviewed-by: Anup Patel <anup@brainfault.org> Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com> Link: https://lore.kernel.org/r/20250429142549.3673976-5-rkrcmar@ventanamicro.com Signed-off-by: Anup Patel <anup@brainfault.org>	2025-04-30 10:14:26 +05:30
Radim KrčmářandAnup Patel	65e8be4fe8	lib: sbi: use 64 bit csr macros ... Switch the most obvious cases to new macros. Reviewed-by: Anup Patel <anup@brainfault.org> Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com> Link: https://lore.kernel.org/r/20250429142549.3673976-4-rkrcmar@ventanamicro.com Signed-off-by: Anup Patel <anup@brainfault.org>	2025-04-30 10:14:25 +05:30
Radim KrčmářandAnup Patel	f82c4bdf8c	lib: sbi: add 64 bit csr macros ... Most CSRs are XLEN bits wide, but some are 64 bit, so rv32 needs two accesses, plaguing the code with ifdefs. Add new helpers that split 64 bit operation into two operations on rv32. The helpers don't use "csr + 0x10", but append "H" at the end of the csr name to get a compile-time error when accessing a non 64 bit register. This has the downside that you have to use the name when accessing them. e.g. csr_read64(0x1234) or csr_read64(CSR_SATP) won't compile and the error messages you get for these bugs are not straightforward. Reviewed-by: Anup Patel <anup@brainfault.org> Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com> Link: https://lore.kernel.org/r/20250429142549.3673976-3-rkrcmar@ventanamicro.com Signed-off-by: Anup Patel <anup@brainfault.org>	2025-04-30 10:14:25 +05:30