On Tue 21 Jan 13:18 PST 2020, Rob Herring via System-dt wrote:
[..]
> To flip all this around, what if domains become the top-level structure:
>
> domain@0 {
> chosen {};
> cpus {};
> memory@0 {};
> reserved-memory {};
> };
>
> domain@1 {
> chosen {};
> cpus {};
> memory@800000 {};
> reserved-memory {};
> };
>
I like this suggestion, as this both creates a natural grouping and
could allow for describing domain-specific hardware as subtrees in each
domain.
There seem to be a need of hierarchy of domains :
- clocks domains that allow cpu clusters to be reset without impacting other clusters.
- Memory domains with physically isolated address spaces within a cluster or memory with very different access costs when using GenZ memory
Regards,
Bjorn
> The content of all the currently top-level nodes don't need to change.
> The OS's would be modified to treat a domain node as the root node
> which shouldn't be very invasive. Then everything else just works as
> is.
>
> This could still have other nodes at the (real) root or links from one
> domain to another. I haven't thought thru that part, but I think this
> structure can only help because it removes the notion that the root
> has a specific cpu view.
>
> Rob
> --
> System-dt mailing list
> System-dt@lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/system-dt
--
System-dt mailing list
System-dt@lists.openampproject.org
https://lists.openampproject.org/mailman/listinfo/system-dt