In reply to uvmsd:
Monitor already has so much of logic with fork-join constructs.
Monitors shouldn’t rely on anything from the driver. By making the monitor dependent on the driver, you eliminate the possibility of using this as a passive agent. This sounds like an external interface, so it’s more likely that you can live with that limitation. But consider if you wanted to replace your driver with a model from a vendor, or to create a multi-chip simulation, then you’d still want to be able to put this agent into passive mode.
Best of luck.