I'm currently working on a derivative of oprofile for remote targets. I would like to have the ability to manipulate the oprofile driver/daemon without a launch so that oprofile can be used on a deeply embedded target and to profile a kernel. I was looking for a mechanism to control the daemon/driver by poking memory, and to read the trace buffer remotely using something like a JTAG device. I'm not that familiar with the oprofile daemon code, but doesn't this mean splitting the daemon functions between the host and the target?
BG _______________________________________________ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
