On 2015-12-14 at 11:08 "'Davide Libenzi' via Akaros" > > I'm a little unclear on why you need to know the full path from > > within Akaros. I'd imagine at some point a tool wants to know the > > original binary for symbol lookups, but that seems a little > > different. > > > > Once you prepare the Linux perf file, Linux perf needs to find the > binary in order to fetch symbols from it.
That makes sense. So then on Linux, is a given 'perf' binary built to go along with a specific kernel (the kernel that it runs on)? Something like /usr/src/linux-4.2/boot/x86/bzimage? Or is the binary path part of a trace record, and perf expects to find it in the stream? Since the full path to the kernel binary is unusable from within Akaros (since that file system doesn't exist), it seemed a little weird to have the kernel export that info, esp when the analysis happens on the Linux side on the developer's workstation, where the knowledge of the binary might exist. That being said, I'm not opposed to exporting that info. I'd just like to understand why it's needed. Barret -- 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.
