이 콘텐츠는 선택한 언어로 제공되지 않습니다.
29.5.3. Getting more detailed output on the modules
				OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could have come from the 
initrd file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result, when OProfile records sample for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the executable.
			
				To get a more detailed view of the actions of the module, you will need to either have the module "unstripped" (that is installed from a custom build) or have the debuginfo package installed for the kernel.
			
				Find out which kernel is running with the 
uname -a command, obtain the appropriate debuginfo package and install it on the machine.
			
				Then proceed with clearing out the samples from previous runs with the following command:
			
opcontrol --reset
~]# opcontrol --reset
				To start the monitoring process, for example, on a machine with Westmere processor, run the following command:
			
opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux --event=CPU_CLK_UNHALTED:500000
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux --event=CPU_CLK_UNHALTED:500000
				Then the detailed information, for instance, for the ext4 module can be obtained with: