Edd Barrett

Without going too deep into the details: we are compiling traces (straight-line paths through our own IR). However, our code still has control flow, as we need to jump to...

That'd be good, yeah! On Thu, 5 Nov 2020, 18:03 Benoit de Chezelles, wrote: > You can actually create your own command for this. This is what you could >...

It might be good if the current line diagnostic was automatically displayed also.

It turned out Tom's recent changes did not require "free-form" instrumentation data, so this has become somewhat lower priority. The PyPy idea is still valid.

Ideally, Krun would support "plugins", where each plugin would consist of: * An iterations runner. * Optionally, an instrumentation parser. As it stands both of these are hard-coded into Krun,...

Most of the stuff we are interested in already goes into the log (bad amperf ratios and dmesg changes) thanks to `log_and_mail()`. Not sure if you had something more grand...

We just need to make the regex more general to match any driver name.

Relevant: #359

Maybe that's it, I think I'll experiment when I get a moment.

Hi Stefan, This all sounds good. About `cset` -- in Krun this is used only when pinning is enabled. By default it is not. The original plan was to pin...