I am currently hacking my way through it using the NodeID (e.g, (A).version on
python side) as a parameter of controller (B) so that I can basically write in
(B)'s state machine :
MachineID proxiedController :=
createMachineID(MachineType:<A_MACHINE_TYPE>, proxiedNodeID);
It seems to work for now but I would like at least not to have
MachineType:<A_MACHINE_TYPE> hardcoded in (B).
Ideally, I would like to be able to get (A)'s MachineID dynamically when
initializing (B) and use it as a constant for the rest of the simulation.
I understand that it goes against the component-hierarchy-based implementation
that instantiates components bottom up, relying on the absence of dependencies
between a component and its parents.
But, is there a way to perform some post-instanciation setup operations like
with the [before_]end_of_elaboration() SystemC callbacks?
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
