Gabriele Monaco <[email protected]> writes: > RV deterministic and hybrid automata currently only support global, > per-cpu and per-task monitors. It isn't possible to write a model that > would follow some different type of object, like a deadline entity or a > lock. > > Define the generic per-object monitor implementation which shares part > of the implementation with the per-task monitors. > The user needs to provide an id for the object (e.g. pid for tasks) and > define the data type for the monitor_target (e.g. struct task_struct * > for tasks). Both are supplied to the event handlers, as the id may not > be easily available in the target. > > The monitor storage (e.g. the rv monitor, pointer to the target, etc.) > is stored in a hash table indexed by id. Monitor storage objects are > automatically allocated unless specified otherwise (e.g. if the creation > context is unsafe for allocation). > > Signed-off-by: Gabriele Monaco <[email protected]>
Reviewed-by: Nam Cao <[email protected]>
