> The get_cpubind function is already in.
> There are several ways I can see
> - Add a configuration flag to limit the discovery to the current binding
> of the process
> - Add a configuration function to limit the discovery to a given cpuset.
> To get the current binding of the process, one has to run a first
> discovery, then use get_cpubind, then run a second one with the
> configuration. This is tedious, the API works this way.
> - Add a function to restrict a discovered topology to a given cpuset. This
> looks like within the scope of the functions we are thinking about for
> network use (extract part of a topology, merge topologies).
> Do we still want this for 1.0?
I think Ashley wanted the first item when he requested lstopo --pid
<pid> but I may be wrong.