From: <job...@ao...> - 2009-11-18 00:44:33
|
On Nov 17, 2009, at 9:23 AM, job...@ao... wrote: > By looking at EIP values, I can see that samples are being collected > for my test module. In the function get_file in daemon/opd_sfile.c > which is called after issuing the opcontrol --shutdown command, I > can see trans->pc values that correspond to the EIP values of > samples collected for my test module but no new sample file is > created for these samples. > > Since I can see the samples are there for my test module, why isn't > a sample file created for the test module samples? When get_file is called for the samples for my test module, the file it gets is /var/lib/oprofile/samples//current/{kern}/no-vmlinux/{dep}/ {kern}/no-vmlinux/TIMER.0.0.all.all.all, which has a nonzero count. Thus, no sample file is created for my test module. Why would samples for my test module result in getting the sample file for no-vmlinux? > > > On Nov 12, 2009, at 3:42 PM, job...@ao... wrote: > >> Could the fact that I am following the instructions below be an >> issue as far as sampling inserted kernel modules? Of course, >> samples for other than the kernel modules seem to be stored just >> fine. >> If running from an image in the internal jffs2 file system, you >> will need to mount another file system to store the samples. Below >> are examples of the commands to set that up. You will need to >> modify for local conditions. >> mkdir /var/lib/oprofile >> mount -t ramfs none /var/lib/oprofile >> >> = > = |