On Fri, Dec 11, 2015 at 12:09 PM, Davide Libenzi <[email protected]>
wrote:
> > +void perfmon_interrupt(struct hw_trapframe *hw_tf, void *data)
>> > +{
>> > + int i;
>> > + struct perfmon_cpu_context *cctx = PERCPU_VARPTR(counters_env);
>> > + uint64_t gctrl, status;
>> > +
>> > + profiler_add_hw_sample(hw_tf);
>>
>> So it looks like we generate a trace whenever any of the counters
>> overflow, but
>> we lose track of which one overflowed. I guess that's what userland perf
>> expects?
>>
>
> I need to add an "ID", and figure out how to pass that to userland perf.
> Will do in follow up CL.
>
Actually, doing it in this stream, as tail commits.
I already added an "info" field containing the event coordinates.
Need to figure out how to translate it for Linux perf now ...
--
You received this message because you are subscribed to the Google Groups
"Akaros" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
