> , uvm_history seems closest by functionality but too tied to uvm and
> somewhat too heavy for .S codes.

The latter is true but former is not.  I'm curious why do you think
uvmhist is tied to uvm (except the name.  Actually, I'd like to rename
it to, e.g., khist).

Anyway, if they can coexist, it will be ok... (but the marconame
CTRn() sounds too terse for me).

enami.