public inbox for opensbi@lists.infradead.org
 help / color / mirror / Atom feed
From: Yu-Chien Peter Lin <peter.lin@sifive.com>
To: opensbi@lists.infradead.org
Cc: zong.li@sifive.com, greentime.hu@sifive.com,
	alvinga@andestech.com, Yu-Chien Peter Lin <peter.lin@sifive.com>
Subject: [PATCH 3/8] lib: sbi_domain: print unsupported SmePMP permissions
Date: Thu, 14 Aug 2025 19:05:17 +0800	[thread overview]
Message-ID: <20250814110522.18809-4-peter.lin@sifive.com> (raw)
In-Reply-To: <20250814110522.18809-1-peter.lin@sifive.com>

The reg->flag is encoded with 6 bits to specify RWX
permissions for M-mode and S-/U-mode. However, only 16
of the possible encodings are valid on SmePMP.

Previously, specifying an unsupported encoding could fail
silently. Add a warning log when an unsupported permission
encoding is detected, improving visibility for debugging.

Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
---
 lib/sbi/sbi_domain.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/lib/sbi/sbi_domain.c b/lib/sbi/sbi_domain.c
index e8adf66f..d6566b12 100644
--- a/lib/sbi/sbi_domain.c
+++ b/lib/sbi/sbi_domain.c
@@ -125,6 +125,7 @@ void sbi_domain_memregion_init(unsigned long addr,
 unsigned int sbi_domain_get_smepmp_flags(struct sbi_domain_memregion *reg)
 {
 	unsigned int pmp_flags = 0;
+	unsigned long rstart, rend;
 
 	if ((reg->flags & SBI_DOMAIN_MEMREGION_ACCESS_MASK) == 0) {
 		/*
@@ -186,6 +187,13 @@ unsigned int sbi_domain_get_smepmp_flags(struct sbi_domain_memregion *reg)
 			pmp_flags |= PMP_W;
 		if (reg->flags & SBI_DOMAIN_MEMREGION_SU_EXECUTABLE)
 			pmp_flags |= PMP_X;
+	} else {
+		rstart = reg->base;
+		rend = (reg->order < __riscv_xlen) ?
+			rstart + ((1UL << reg->order) - 1) : -1UL;
+		sbi_printf("%s: Unsupported Smepmp permissions "
+			   "on region 0x%" PRILX "-0x%" PRILX "\n",
+			   __func__, rstart, rend);
 	}
 
 	return pmp_flags;
-- 
2.39.3


-- 
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi

  parent reply	other threads:[~2025-08-14 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-14 11:05 [PATCH 0/8] SmePMP bugfixes and improvement Yu-Chien Peter Lin
2025-08-14 11:05 ` [PATCH 1/8] lib: sbi_hart: move sbi_hart_get_smepmp_flags() to sbi_domain Yu-Chien Peter Lin
2025-08-14 11:05 ` [PATCH 2/8] lib: sbi_domain: allow specifying inaccessible region Yu-Chien Peter Lin
2025-08-14 11:05 ` Yu-Chien Peter Lin [this message]
2025-08-14 11:05 ` [PATCH 4/8] lib: sbi_hart: add error message for insufficient PMP entries Yu-Chien Peter Lin
2025-08-14 11:05 ` [PATCH 5/8] lib: sbi_domain_context: skip the reserved entry during domain context switch Yu-Chien Peter Lin
2025-08-15  5:54   ` Alvin Che-Chia Chang(張哲嘉)
2025-08-14 11:05 ` [PATCH 6/8] lib: sbi_domain: add SBI_DOMAIN_MEMREGION_FW memregion flag Yu-Chien Peter Lin
2025-08-14 15:39   ` Alvin Che-Chia Chang(張哲嘉)
2025-08-21  8:32   ` Xiang W
2025-08-14 11:05 ` [PATCH 7/8] lib: sbi_domain: ensure consistent firmware PMP entries Yu-Chien Peter Lin
2025-08-14 11:05 ` [PATCH 8/8] lib: sbi_domain_context: preserve firmware PMP entries during domain context switch Yu-Chien Peter Lin
2025-10-06  5:21 ` [PATCH 0/8] SmePMP bugfixes and improvement Anup Patel
2025-10-08  1:30   ` Peter Lin

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=20250814110522.18809-4-peter.lin@sifive.com \
    --to=peter.lin@sifive.com \
    --cc=alvinga@andestech.com \
    --cc=greentime.hu@sifive.com \
    --cc=opensbi@lists.infradead.org \
    --cc=zong.li@sifive.com \
    /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