On 10/17/2009 06:35 AM, Daniel Schwager wrote:
I'm not that familiar with oprofile ...
so, setup with
opcontrol --deinit; modprobe oprofile timer=1; opcontrol --start
gave me the following result:
kvm03:~# opreport
Use 'opreport -l'. Make sure your qemu isn't stripped.
Try to start without timer=1 hung up my physical machine after daemon is
started:
kvm03:/opt/kvm-86-vnc-patch# opcontrol --deinit; modprobe oprofile ;
opcontrol --start
Stopping profiling.
Killing daemon.
Unloading oprofile module
Using default event: CPU_CLK_UNHALTED:100000:0:1:1
Using 2.6+ OProfile kernel interface.
Using log file /var/lib/oprofile/samples/oprofiled.log
Daemon started.
Could I give you more information ? Should I setup oprofile in another
way ?
Is there an oops in dmesg, or is the machine dead? What's the host
kernel version?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
