The agent_manager class is used by Matic to support communication with Simics Agents, which run on target systems. The manager creates and controls Agent Handles for those agents. There may only exist one agent manager in the simulation.
Matic requires the simulation to run, allowing Simics Agents on the target systems to run and respond. However, if the simulation is not running, any commands will be queued on the agent_handle objects and run eventually.
The start-agent-manager command will load the required module and create and start an agent manager.
See also: Simics User's Guide as well as the agent_handle class.
conf_object, log_object
- cell-change
- Notifier that is triggered after the object's cell was changed.
- object-delete
- Notifier that is triggered just before Simics object is deleted.
- queue-change
- Notifier that is triggered after the object's clock was changed. New clock can be obtained with the SIM_object_clock function.
-
connect-to-agent
– create a handle for a Simics Agent
-
disable
– disable the manager and delete handles
-
enable
– enable the agent_manager
-
info
– print information about the object
-
list-agents
– list all known Simics Agents
-
status
– print status of the object
-
infos
-
Optional attribute;
read/write access; type:
[s*]
Information about each Simics Agent.
-
pipe
-
Pseudo attribute;
read-only access; type:
o|n
The connected magic pipe object.
matic