UVM config for driver, monitor

In reply to verif_learner:

In reply to verif_learner:
I am hesitant to agent configuration class directly to driver/monitor as it contains more info than what they would need. I am also hesitant to create separate configuration classes for driver/monitor as I am ending with way too many classes in the environment. Probably, I will just create additional driver/monitor config classes or just pass virtual interfaces.
Thanks for the input.

I#d not recommedn to have seperate configuration objects for driver/monitor/sequencer. It is sufficient to have such an object for the agent. From the agent you can make the direct assignments to the variables in driver/monitor.