This can be very expensive in the nested virtualization case, so I
wouldn't like this to be in normal paths. I think detailed profiling
like that can be left to 'perf kvm', which only has overhead if enabled
at runtime.
For example you can put the code to note the cpl in a tracepoint which
is enabled dynamically.
--
error compiling committee.c: too many arguments to function
--