From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Anup Patel" <anup@brainfault.org>
Cc: <opensbi@lists.infradead.org>
Subject: Re: [PATCH 1/8] lib: sbi: add 64 bit csr macros
Date: Mon, 28 Apr 2025 15:48:20 +0200 [thread overview]
Message-ID: <D9IBI128G7PQ.10FJADCTGTA4T@ventanamicro.com> (raw)
In-Reply-To: <CAAhSdy3L1_FFuy-UzViRdCWSQeZc6v_fBhwbHb9oT7Ei4FA0KQ@mail.gmail.com>
2025-04-28T17:58:31+05:30, Anup Patel <anup@brainfault.org>:
> On Tue, Apr 15, 2025 at 8:13 PM Radim Krčmář <rkrcmar@ventanamicro.com> wrote:
>>
>> 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.
>>
>> Signed-off-by: Radim Krčmář <rkrcmar@ventanamicro.com>
>> ---
>> diff --git a/include/sbi/riscv_asm.h b/include/sbi/riscv_asm.h
>> @@ -156,6 +156,27 @@
>> : "memory"); \
>> })
>>
>> +
>
> Redundant newline.
Oops, it will be gone in v2, thanks.
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next prev parent reply other threads:[~2025-04-28 13:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 13:19 [PATCH 0/8] Reset more security-related CSRs Radim Krčmář
2025-04-15 13:19 ` [PATCH 1/8] lib: sbi: add 64 bit csr macros Radim Krčmář
2025-04-28 12:28 ` Anup Patel
2025-04-28 13:48 ` Radim Krčmář [this message]
2025-04-15 13:19 ` [PATCH 2/8] lib: sbi: use " Radim Krčmář
2025-04-28 12:29 ` Anup Patel
2025-04-15 13:19 ` [PATCH 3/8] lib: sbi_hart: reset hstatus Radim Krčmář
2025-04-28 12:27 ` Anup Patel
2025-04-15 13:19 ` [PATCH 4/8] lib: sbi_hart: reset sstateen and hstateen Radim Krčmář
2025-04-28 12:29 ` Anup Patel
2025-04-15 13:19 ` [PATCH 5/8] lib: sbi_hart: fix sstateen emulation Radim Krčmář
2025-04-28 12:34 ` Anup Patel
2025-04-15 13:19 ` [PATCH 6/8] lib: sbi_hart: reset mstateen0 Radim Krčmář
2025-04-28 12:35 ` Anup Patel
2025-04-15 13:19 ` [PATCH 7/8] lib: sbi_hart: add Ssstateen extension Radim Krčmář
2025-04-28 12:38 ` Anup Patel
2025-04-28 13:47 ` Radim Krčmář
2025-04-29 5:30 ` Anup Patel
2025-04-15 13:19 ` [PATCH 8/8] lib: sbi_hart: properly reset Ssstateen Radim Krčmář
2025-04-28 12:39 ` Anup Patel
2025-04-28 13:44 ` Radim Krčmář
2025-04-28 12:41 ` [PATCH 0/8] Reset more security-related CSRs Anup Patel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9IBI128G7PQ.10FJADCTGTA4T@ventanamicro.com \
--to=rkrcmar@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=opensbi@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox