Index: sid/bsp/configrun-sid.in =================================================================== RCS file: /cvs/src/src/sid/bsp/configrun-sid.in,v retrieving revision 1.37 diff -c -p -r1.37 configrun-sid.in *** sid/bsp/configrun-sid.in 16 Dec 2005 10:23:12 -0000 1.37 --- sid/bsp/configrun-sid.in 26 Jun 2006 21:57:15 -0000 *************** if ($opt_cpu eq "mt") *** 499,510 **** if ($opt_gprof) { $second_section .= "# gprof connections - connect-pin target-sched 0-event -> gprof sample connect-pin deinit-sequence output-7 -> gprof store ! relate gprof target-component cpu connect-pin cpu cg-caller -> gprof cg-caller connect-pin cpu cg-callee -> gprof cg-callee ! set gprof value-attribute pc set gprof bucket-size 4 # bytes per bucket "; } --- 499,511 ---- if ($opt_gprof) { $second_section .= "# gprof connections connect-pin deinit-sequence output-7 -> gprof store ! connect-pin cpu sample-gprof -> gprof sample ! connect-pin cpu gprof-pc -> gprof pc ! connect-pin cpu gprof-pc-hi -> gprof pc-hi connect-pin cpu cg-caller -> gprof cg-caller connect-pin cpu cg-callee -> gprof cg-callee ! relate gprof target-component cpu set gprof bucket-size 4 # bytes per bucket "; } Index: sid/component/profiling/sw-profile-gprof.xml =================================================================== RCS file: /cvs/src/src/sid/component/profiling/sw-profile-gprof.xml,v retrieving revision 1.4 diff -c -p -r1.4 sw-profile-gprof.xml *** sid/component/profiling/sw-profile-gprof.xml 11 May 2006 16:04:38 -0000 1.4 --- sid/component/profiling/sw-profile-gprof.xml 26 Jun 2006 21:57:16 -0000 *************** *** 6,11 **** --- 6,13 ---- + + *************** *** 21,27 **** - --- 23,28 ---- *************** *** 55,62 ****

This component needs to be configured with the target-component relation. The first element in the relation will be used as the ! target of profiling. The value-attribute setting contains the ! name of the target component's attribute that will be collected. If pc-size is 64, then the target component should also have an attribute with the same name suffixed by "-hi"

--- 56,62 ----

This component needs to be configured with the target-component relation. The first element in the relation will be used as the ! target of profiling. If pc-size is 64, then the target component should also have an attribute with the same name suffixed by "-hi"

*************** *** 78,90 ****

Whenever the sample pin is driven, this component ! takes a single sample of the configured target component's value ! attribute. The attribute is interpreted as a numeric string, ! and the resulting number is accumulated in a big histogram, in ! the appropriate bucket. The bucket is chosen by masking the ! number into bucket-size-wide buckets. ! If the target component is unset, or its target attribute does ! not result in a valid numeric string, no sample is accumulated.

Alternately, if the cg-caller and perhaps the cg-caller-hi and then the cg-callee and perhaps the cg-callee-hi --- 78,89 ----

Whenever the sample pin is driven, this component ! takes a single sample using the number drive on the pin. ! The resulting number is accumulated in a big histogram, in ! the appropriate bucket. The bucket is chosen by combining the two 32 bit values ! last driven on the pc and the pc-hi pins to form one 64 bit index. ! This index is then masked into bucket-size-wide buckets. ! If the target component is unset then no sample is accumulated.

Alternately, if the cg-caller and perhaps the cg-caller-hi and then the cg-callee and perhaps the cg-callee-hi *************** *** 144,161 **** be driven by any activity in SID, such as bus traffic (see hw-probe-bus), or host or target schedulers (see sid-sched-*). ! Perhaps the simplest way is to take a CPU PC sample every time ! the CPU has completed a batch of instructions.

new sw-profile-gprof gprof new SOME_KIND_OF_CPU cpu relate gprof target-component cpu connect-pin shutdown-manager output-5 -> gprof store ! connect-pin foo output -> cpu step! ! connect-pin foo output -> gprof sample ! # Set sampling interval by number of CPU instructions. ! set cpu step-insn-count 127 Host system --- 143,157 ---- be driven by any activity in SID, such as bus traffic (see <tt>hw-probe-bus</tt>), or host or target schedulers (see <tt>sid-sched-*</tt>). ! </p> <code> new sw-profile-gprof gprof new SOME_KIND_OF_CPU cpu relate gprof target-component cpu connect-pin shutdown-manager output-5 -> gprof store ! connect-pin cpu sample-gprof -> gprof sample ! connect-pin cpu gprof-pc -> gprof pc </code> <title> Host system