On 2015-12-13 at 09:43 "'Davide Libenzi' via Akaros" <[email protected]> wrote: > There is a way, and Linux perf has an ID for every trace, ID which > you can bind to any event string you can push into the perf file. > But, in order to do that, I will need to add libpfm4 dependency to > kprof2perf, which is not worth it. > Instead I will go ahead to move the akaros to linux perf conversion, > to the akaros perf tool (which already has the libpfm4 dependency), > and drop the kprof2perf tool altogether.
sounds great. > In order to do that though, I will need to know, on the Akaros side, > the full path within the build directory, of the akaros kernel ELF > file. A couple of solutions which come to my mind: > > 1) Build system create a magic build info file into KFS > 2) Build info are stuck in a kernel ELF section, retrievable via > system call or #some-dev-file just to be clear, you want a way for a program running on Akaros to know the path to the kernel when it was built, e.g. /full/path/to/obj/kern/akaros-kernel (or perhaps akaros-kernel-64b)? -- 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.
