Lines Matching full:varname
405 (<varname>last_task</varname> and <varname>last_is_kernel</varname>) are
468 <varname>mmap_sem</varname> for the task is then taken, to allow safe
477 <varname>last_task</varname> and <varname>last_is_kernel</varname>, as
550 for the buffer processing. The <varname>struct transient</varname>
563 various handlers (see the <varname>handlers</varname> array), which
600 <varname>struct transient</varname>, and we must locate an
691 <varname>profile_spec</varname>.
740 <varname>filename_spec</varname>. Finally, we can check whether to
742 <varname>filename_spec</varname> against the
743 <varname>profile_spec</varname> the user specified (for the interested,
835 <varname>op_bfd</varname> class provides an abstracted interface to
846 The class <varname>profile_container</varname> is a hold-all that
848 <varname>profile_t</varname> objects. The
851 key/value types to the <varname>profile_t</varname>. Once this has been
853 <varname>profile_t</varname> plus the <varname>op_bfd</varname> for
858 collected in the <varname>op_bfd</varname>.
861 then we interrogate the <varname>profile_t</varname> for the relevant samples
862 for that offset range. We create a <varname>symbol_entry</varname>
864 debug information from the <varname>op_bfd</varname>, and possibly
867 Finally the <varname>symbol_entry</varname> is added to
868 a private container of <varname>profile_container</varname> - this
869 <varname>symbol_container</varname> holds all such processed symbols.
881 <varname>profile_container</varname> on a symbol-by-symbol basis. To
886 <varname>profile_container</varname> for a
887 <varname>symbol_collection</varname> (this is also where thresholding
890 <varname>opreport_formatter</varname> is initialised.
893 iterates through the (sorted) <varname>symbol_collection</varname>;
895 <varname>format_flags</varname> options) are output by calling the
896 field formatters, with the <varname>symbol_entry</varname> passed in.
924 Each extended feature has an entry in the <varname>ext_feature_table</varname>
1002 An additional field, <varname>odb_t * ext_file</varname>, is added to the
1003 <varname>struct sfile</varname> for storing extended sample files
1043 checks for the <varname>ext:ibs_fetch</varname> or <varname>ext:ibs_op</varname>
1057 Here, the OProfile daemon parses the <varname>--ext-feature</varname>
1062 (<varname>struct opd_event ibs_vc[OP_MAX_IBS_COUNTERS]</varname>) and
1064 (<varname>ibs_vci_map[OP_MAX_IBS_COUNTERS]</varname>) with IBS event value
1074 event buffer using the <varname>"IBS_FETCH_CODE"</varname> or
1075 <varname>"IBS_OP_CODE"</varname>. These codes trigger the handlers
1078 <varname>handler_t handlers[]</varname> vector in
1099 Traditionally, sample file information <varname>(odb_t)</varname> is stored
1100 in the <varname>struct sfile::odb_t file[OP_MAX_COUNTER]</varname>.
1101 Currently, <varname>OP_MAX_COUNTER</varname> is 8 on non-alpha, and 20 on
1107 <varname>OP_MAX_COUNTER</varname> (currently upto 13 IBS-fetch and 46 IBS-op
1109 handlers (<varname>struct opd_ext_sfile_handlers</varname>) for managing
1112 be accessed through <varname>struct sfile::odb_t * ext_files</varname>.
