Re: [PATCH v2 0/3] OpenSBI domain initialization order

Pawandeep Oza <[email protected]>
Newsgroups org.infradead.lists.opensbi
Message-ID <CAAVgOk+Oj8xS=cvOpQk5M-HedxgpPT8+z=Aa+NGfoHhtpnup=Q@mail.gmail.com>
On Mon, Aug 17, 2026 at 7:32 AM Anup Patel <[email protected]> wrote:
>
> Currently, we rely on the "opensbi-domain" DT property of CPU DT nodes
> to select the domain assigned to each HART at boot-time but unfortunately
> this is only suitable if we have two non-ROOT domains (aka trused and
> non-trusted. For more than two non-ROOT domains, the domain initialization
> order should be much more predictable where users should define the exact
> order via some DT property under domain DT nodes.
>
> These patches can also be found in sbi_domain_init_order_v2 branch
> at: https://github.com/avpatel/opensbi.git
>
> Changes since v1:
> - Removed unwanted "break" from the loop in sbi_domain_context_exit()
> - Use root values when "next-arg1", "next-addr" and "next-mode" DT
>   properties are absent in the domain DT node.
>
> Anup Patel (3):
>   lib: sbi_domain: Check possible harts in
>     sbi_domain_context_enter/exit()
>   lib: sbi_domain: Re-work boot-time assignment of HARTs to non-ROOT
>     domains
>   lib: sbi_domain: Introduce domain intialization order
>
>  docs/domain_support.md             |  25 ++++---
>  include/sbi/sbi_domain.h           |   6 +-
>  include/sbi_utils/fdt/fdt_domain.h |   3 +-
>  lib/sbi/sbi_domain.c               |  45 ++++++++-----
>  lib/sbi/sbi_domain_context.c       |  31 ++++++---
>  lib/utils/fdt/fdt_domain.c         | 103 +++++------------------------
>  6 files changed, 79 insertions(+), 134 deletions(-)
>
> --
> 2.43.0
>
>
> --
> opensbi mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/opensbi

LGTM

Reviewed-by: Pawandeep Oza <[email protected]>
Tested-by: Pawandeep Oza <[email protected]>

-- 
opensbi mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/opensbi
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.