From: Yu-Chien Peter Lin <peter.lin@sifive.com>
To: Radim Krcmar <rkrcmar@qti.qualcomm.com>
Cc: "opensbi@lists.infradead.org" <opensbi@lists.infradead.org>,
"zong.li@sifive.com" <zong.li@sifive.com>,
"greentime.hu@sifive.com" <greentime.hu@sifive.com>,
"anup@brainfault.org" <anup@brainfault.org>,
"scott@riscstar.com" <scott@riscstar.com>,
"conor@kernel.org" <conor@kernel.org>,
"dave.patel@riscstar.com" <dave.patel@riscstar.com>,
"raymond.mao@riscstar.com" <raymond.mao@riscstar.com>,
"robin.randhawa@sifive.com" <robin.randhawa@sifive.com>,
"samuel.holland@sifive.com" <samuel.holland@sifive.com>,
"pawandeep.oza@oss.qualcomm.com" <pawandeep.oza@oss.qualcomm.com>,
"krzk@kernel.org" <krzk@kernel.org>,
opensbi <opensbi-bounces@lists.infradead.org>
Subject: Re: [PATCH v2 5/9] lib: sbi_hart: add WID protection mechanism
Date: Fri, 23 Oct 2026 16:05:38 +0800 [thread overview]
Message-ID: <atsVUlAh0LSjUkAW@plin-1878> (raw)
In-Reply-To: <DM6FR879EC0N.1XXM04LPUG5F0@qti.qualcomm.com>
Hi Radim,
On Fri, Oct 16, 2026 at 05:24:07PM +0000, Radim Krcmar wrote:
> 2026-08-17T17:04:59+08:00, Yu-Chien Peter Lin <peter.lin@sifive.com>:
> > Register a WID-based hart protection mechanism that
> > configures mlwid and mwiddeleg CSRs on domain entry.
> > This enables the protection framework reconfigure WID
> > isolation whenever domains are switched.
> >
> > Signed-off-by: Yu-Chien Peter Lin <peter.lin@sifive.com>
> > ---
> > Changes v1 -> v2:
> > - Validate WID against pmlwidlist before writing mlwid CSR (Oza)
> > ---
> > diff --git a/lib/sbi/sbi_hart_worlds.c b/lib/sbi/sbi_hart_worlds.c
> > +++ b/lib/sbi/sbi_hart_worlds.c
> > @@ -0,0 +1,72 @@
> > +/*
> > + * SPDX-License-Identifier: BSD-2-Clause
> > + *
> > + * Copyright (c) 2026 SiFive Inc.
> > + */
> > +
> > +#include <sbi/riscv_encoding.h>
> > +#include <sbi/sbi_console.h>
> > +#include <sbi/sbi_domain.h>
> > +#include <sbi/sbi_error.h>
> > +#include <sbi/sbi_hart.h>
> > +#include <sbi/sbi_hart_protection.h>
> > +#include <sbi/sbi_hart_worlds.h>
> > +#include <sbi/sbi_scratch.h>
> > +
> > +static int sbi_hart_worlds_configure(struct sbi_scratch *scratch,
> > + struct sbi_domain *dom)
> > +{
> > + struct sbi_hart_features *hf = sbi_hart_features_ptr(scratch);
> > + bool wid_found = true;
> > + u32 wid_val = 0;
> > +
> > + if (!sbi_hart_has_extension(scratch, SBI_HART_EXT_SMLWID))
> > + return 0;
> > + if (dom->has_wid) {
> > + wid_val = dom->wid;
>
> I would prefer to fail domain creation if we have mlwid and the domain
> doesn't specify its wid.
>
> The rest are security issues waiting to happen.
Agreed. I’ll make WID mandatory whenever MLWID is present, rather than
falling back to other sources.
>
> > + } else if (sbi_hart_has_extension(scratch, SBI_HART_EXT_SMWID)) {
> > + wid_val = csr_read(CSR_MWID) & ~MWID_LOCK;
> > + } else if (hf->has_pmwid) {
> > + wid_val = hf->pmwid;
> > + } else {
> > + /*
> > + * Smlwid present but no WID source. Without writing
> > + * mlwid, the hardware reset value is used which may
> > + * cause a software-check exception on lower-privilege
> > + * mode entry.
> > + */
> > + wid_found = false;
> > + }
>
> mlwid CSR is a WID source by itself -- the domain will use the current
> value... Failing initialization seems better than reusing whatever the
> last domain left there.
Agreed.
>
> > +
> > + if (wid_found) {
> > + if (hf->has_pmlwidlist &&
> > + !(hf->pmlwidlist & BIT_ULL(wid_val))) {
> > + sbi_printf("%s: domain wid %u not in pmlwidlist\n",
> > + __func__, wid_val);
> > + return SBI_EINVAL;
> > + }
> > + csr_write(CSR_MLWID, wid_val);
> > + }
> > +
> > + if (sbi_hart_has_extension(scratch, SBI_HART_EXT_SMWIDDELEG))
> > + csr_write(CSR_MWIDDELEG, dom->widdeleg);
>
> I would be a happier if we added a little bit of widdeleg verification,
> so DT mistakes wouldn't shoot us in the head.
Sure.
Regards,
Peter Lin
--
opensbi mailing list
opensbi@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/opensbi
next prev parent reply other threads:[~2026-10-23 8:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 9:04 [PATCH v2 0/9] Add RISC-V Worlds ISA support to OpenSBI Yu-Chien Peter Lin
2026-08-17 9:04 ` [PATCH v2 1/9] lib: sbi_hart: detect RISC-V Worlds ISA extensions Yu-Chien Peter Lin
2026-09-03 16:50 ` Pawandeep Oza
2026-08-17 9:04 ` [PATCH v2 2/9] lib: utils: fdt_helper: parse RISC-V Worlds per-hart WID properties Yu-Chien Peter Lin
2026-09-03 21:15 ` Pawandeep Oza
2026-09-24 7:33 ` Yu-Chien Peter Lin
2026-09-25 18:26 ` Pawandeep Oza
2026-08-17 9:04 ` [PATCH v2 3/9] lib: fdt_domain: parse domain " Yu-Chien Peter Lin
2026-09-03 21:18 ` Pawandeep Oza
2026-09-24 7:55 ` Yu-Chien Peter Lin
2026-08-17 9:04 ` [PATCH v2 4/9] lib: sbi_hart: lock mwid CSR for RoT immutability Yu-Chien Peter Lin
2026-09-03 21:20 ` Pawandeep Oza
2026-08-17 9:04 ` [PATCH v2 5/9] lib: sbi_hart: add WID protection mechanism Yu-Chien Peter Lin
2026-08-18 2:39 ` Yu-Chien Peter Lin
2026-09-03 21:52 ` Pawandeep Oza
2026-09-24 8:24 ` Yu-Chien Peter Lin
2026-10-16 17:24 ` Radim Krcmar
2026-10-16 18:33 ` Radim Krcmar
2026-10-23 8:11 ` Yu-Chien Peter Lin
2026-10-23 8:05 ` Yu-Chien Peter Lin [this message]
2026-08-17 9:05 ` [PATCH v2 6/9] lib: sbi_domain_context: add slwid to per-domain S-mode context Yu-Chien Peter Lin
2026-09-03 21:59 ` Pawandeep Oza
2026-10-16 17:08 ` Radim Krcmar
2026-10-23 8:10 ` Yu-Chien Peter Lin
2026-08-17 9:05 ` [PATCH v2 7/9] include: sbi_types: add PRIx64 format macro Yu-Chien Peter Lin
2026-09-03 21:59 ` Pawandeep Oza
2026-08-17 9:05 ` [PATCH v2 8/9] lib: sbi: display World ID configuration at boot Yu-Chien Peter Lin
2026-09-03 22:00 ` Pawandeep Oza
2026-08-17 9:05 ` [PATCH v2 9/9] docs: document WID DT properties Yu-Chien Peter Lin
2026-09-03 22:01 ` Pawandeep Oza
2026-09-28 8:35 ` Anup Patel
2026-09-29 13:33 ` Yu-Chien Peter Lin
2026-09-28 11:30 ` Krzysztof Kozlowski
2026-09-29 14:19 ` Yu-Chien Peter Lin
2026-09-28 11:33 ` [PATCH v2 0/9] Add RISC-V Worlds ISA support to OpenSBI Krzysztof Kozlowski
2026-09-29 14:29 ` Yu-Chien 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=atsVUlAh0LSjUkAW@plin-1878 \
--to=peter.lin@sifive.com \
--cc=anup@brainfault.org \
--cc=conor@kernel.org \
--cc=dave.patel@riscstar.com \
--cc=greentime.hu@sifive.com \
--cc=krzk@kernel.org \
--cc=opensbi-bounces@lists.infradead.org \
--cc=opensbi@lists.infradead.org \
--cc=pawandeep.oza@oss.qualcomm.com \
--cc=raymond.mao@riscstar.com \
--cc=rkrcmar@qti.qualcomm.com \
--cc=robin.randhawa@sifive.com \
--cc=samuel.holland@sifive.com \
--cc=scott@riscstar.com \
--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