From: Clément Léger <cleger@rivosinc.com>
To: opensbi@lists.infradead.org
Subject: [PATCH 3/6] lib: sbi: sse: Return SBI_EDENIED for read only parameters.
Date: Mon, 24 Mar 2025 18:02:57 +0100 [thread overview]
Message-ID: <66fe7daf-e934-4135-b07a-89d403cf12c7@rivosinc.com> (raw)
In-Reply-To: <20250324-38c2a7772fb7bbe8a15e2d6a@orel>
On 24/03/2025 18:01, Andrew Jones wrote:
> On Mon, Mar 17, 2025 at 11:54:21AM +0100, Cl?ment L?ger wrote:
>> The SSE specification did specified that read only parameters should
>> return SBI_EBADRANGE but was modified recently to return SBI_EDENIED.
>>
>> Signed-off-by: Cl?ment L?ger <cleger@rivosinc.com>
>> ---
>> lib/sbi/sbi_sse.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/lib/sbi/sbi_sse.c b/lib/sbi/sbi_sse.c
>> index a30fad54..ac714b8a 100644
>> --- a/lib/sbi/sbi_sse.c
>> +++ b/lib/sbi/sbi_sse.c
>> @@ -388,7 +388,7 @@ static int sse_event_set_hart_id_check(struct sbi_sse_event *e,
>> struct sbi_domain *hd = sbi_domain_thishart_ptr();
>>
>> if (!sse_event_is_global(e))
>> - return SBI_EBAD_RANGE;
>> + return SBI_EDENIED;
>>
>> if (!sbi_domain_is_assigned_hart(hd, sbi_hartid_to_hartindex(hartid)))
>> return SBI_EINVAL;
>> @@ -444,7 +444,7 @@ static int sse_event_set_attr_check(struct sbi_sse_event *e, uint32_t attr_id,
>>
>> return SBI_OK;
>> default:
>> - return SBI_EBAD_RANGE;
>> + return SBI_EDENIED;
>
> This confused me at first. Maybe a comment pointing out that
> sbi_sse_attr_check() already confirmed we're in range and
> this switch default just catches read-only attributes would
> be helpful.
Yes sure, I'll do that in the next version.
Thanks,
Cl?ment
>
> Otherwise,
>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
>
> Thanks,
> drew
>
>> }
>> }
>>
>> --
>> 2.47.2
>>
next prev parent reply other threads:[~2025-03-24 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 10:54 [PATCH 0/6] lib: sbi: sse: spec update and fixes Clément Léger
2025-03-17 10:54 ` [PATCH 1/6] lib: sbi: sse: Update SSE event ids Clément Léger
2025-03-24 16:15 ` Andrew Jones
2025-03-17 10:54 ` [PATCH 2/6] lib: sbi: sse: Fix format string for event invalid state Clément Léger
2025-03-24 16:39 ` Andrew Jones
2025-03-24 16:41 ` Clément Léger
2025-03-17 10:54 ` [PATCH 3/6] lib: sbi: sse: Return SBI_EDENIED for read only parameters Clément Léger
2025-03-24 17:01 ` Andrew Jones
2025-03-24 17:02 ` Clément Léger [this message]
2025-03-17 10:54 ` [PATCH 4/6] lib: sbi: sse: Rename STATUS* interrupted flags to SSTATUS* Clément Léger
2025-03-24 17:03 ` Andrew Jones
2025-03-17 10:54 ` [PATCH 5/6] lib: sbi: sse: Add support for SSTATUS.SPELP Clément Léger
2025-03-24 17:08 ` Andrew Jones
2025-03-17 10:54 ` [PATCH 6/6] lib: sbi: sse: Add support for SSTATUS.SDT Clément Léger
2025-03-24 17:46 ` Andrew Jones
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=66fe7daf-e934-4135-b07a-89d403cf12c7@rivosinc.com \
--to=cleger@rivosinc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.