Le 16/11/2019 à 21:45, Dan Williams a écrit :

quoted

My feeling is that any existing users of access0 are definitely not going
to be expecting generic initiators, so we might want to do this the other
way around. access0 is only CPUs and memory, access1 is including
generic initiators.  If there are no GIs don't expose access1 at all?

There are no consumers of the information that I know of, so I do not
see the risk of regression.

hwloc already reads access0/initiators/ node symlinks (mostly useful for
finding which CPUs are local to kmem dax devices). If I understand
correctly the changes you propose, we would get an empty list of CPUs in
the access0/initiators/ nodes? If it only occurs on platforms with GI
(when are those coming to market?), I'd say it's not a big deal for us,
we'll manage to have users upgrade their hwloc.

Brice



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel