From: John L. <mov...@us...> - 2003-06-14 23:29:29
|
Update of /cvsroot/oprofile/oprofile/doc In directory sc8-pr-cvs1:/tmp/cvs-serv13222/doc Modified Files: oprofile.xml Log Message: s/RTC/RTC_INTERRUPTS/ Index: oprofile.xml =================================================================== RCS file: /cvsroot/oprofile/oprofile/doc/oprofile.xml,v retrieving revision 1.78 retrieving revision 1.79 diff -u -p -d -r1.78 -r1.79 --- oprofile.xml 14 Jun 2003 23:27:04 -0000 1.78 +++ oprofile.xml 14 Jun 2003 23:29:26 -0000 1.79 @@ -615,7 +615,7 @@ Here, we have an Intel laptop without su <screen> # op_help -r CPU with RTC device -# opcontrol --vmlinux=/boot/2.5.66/vmlinux --event=RTC:1024:0:1:1 +# opcontrol --vmlinux=/boot/2.5.66/vmlinux --event=RTC_INTERRUPTS:1024:0:1:1 # opcontrol --start </screen> </sect3> @@ -701,7 +701,7 @@ of the form <option><emphasis>name</emph </informaltable> <para> If OProfile is using RTC mode, and you want to alter the default counter value, -you can use something like <option>--event=RTC:2048:0:1:1</option>. Note the last +you can use something like <option>--event=RTC_INTERRUPTS:2048:0:1:1</option>. Note the last three values here are ignored. If OProfile is using timer-interrupt mode, there is no configuration possible. </para> @@ -820,7 +820,7 @@ two. Setting the value from the GUI should be straightforward. On the command line, you need to specify the event to <command>opcontrol</command>, e.g. : </para> -<para><command>opcontrol --event=RTC:256:0:1:1</command></para> +<para><command>opcontrol --event=RTC_INTERRUPTS:256:0:1:1</command></para> </sect2> <sect2 id="timer"> |