TempleOSCD_140715.ISO
This commit is contained in:
1 parent
7ef616a20e
commit
64f679eeb9
1095 files changed
+24814
-221011
No files matched your search
+3
-5
@@ -1,9 +1,7 @@
|
||||
$WW,1$The TempleOS profiler records statistics on what code location was executing when a task was preempted. You can learn where most time is wasted. There are two modes, $LK,"ProfBin",A="MN:ProfBin"$() which monitors a range of buckets and $LK,"ProfAll",A="MN:ProfAll"$() which records a hit location as well as count. I recommend $LK,"ProfAll",A="MN:ProfAll"$().
|
||||
$WW,1$The profiler records where the CPU was executing when the $TX,"1000 Hz",D="DD_JIFFY_HZ"$ timer interrupt occured, so you can learn where time is spent.
|
||||
|
||||
You can pass a subroutine depth level argument which records a hit in not only the routine executing, but the routines which called it, as well.
|
||||
Use the $LK,"Prof",A="MN:Prof"$() depth argument to record a hit in the N routines which called the current routine, as well.
|
||||
|
||||
When done collecting statistics, use $LK,"ProfRep",A="MN:ProfRep"$() for a report. You might need a $LK,"DocMax",A="MN:DocMax"$() to expand the command line window buffer to fit it all.
|
||||
|
||||
You can set the CPU to monitor with $LK,"ProfCPUSet",A="MN:ProfCPUSet"$().
|
||||
|
||||
Study the code. The profiler is very simple and you might want to enhance it or modify it to debug something in particular.
|
||||
Study the code. The profiler is very simple. You might want to enhance it or modify it to debug something in particular.
|
||||
Reference in new issue
Block a user