On Wed, Jul 27, 2022 at 07:11:30PM +0200, Daniel Bristot de Oliveira wrote: > A runtime monitor can cause a reaction to the detection of an > exception on the model's execution. By default, the monitors have > tracing reactions, printing the monitor output via tracepoints. > But other reactions can be added (on-demand) via this interface. > > The user interface resembles the kernel tracing interface and > presents these files: > > "available_reactors" > - Reading shows the available reactors, one per line. > > For example: > # cat available_reactors > nop > panic > printk > > "reacting_on" > - It is an on/off general switch for reactors, disabling s/switch/switcher/ s/disabling/enabling\/disabling/ [...] > + * "available_reactors" > + * - List the available reactors, one per line. > + * > + * For example: > + * # cat available_reactors > + * nop > + * panic > + * printk > + * > + * "reacting_on" > + * - It is an on/off general switch for reactors, disabling s/switch/switcher/ s/disabling/enabling\/disabling/ [...] > +/** > + * rv_register_reactor - register a rv reactor. > + * @reactor: The rv_reactor to be registered. > + * > + * Returns 0 if successful, error otherwise. > + */ > +int rv_register_reactor(struct rv_reactor *reactor) > +{ > + int retval = 0; > + > + if (strlen(reactor->name) >= MAX_RV_REACTOR_NAME_SIZE) { s/>=/>/