Lines Matching full:feature
904 <title>Extended Feature Interface</title>
910 The Extended Feature Interface is a standard callback interface
912 Each feature defines a set of callback handlers which can be enabled or
921 <title>Feature Name and Handlers</title>
924 Each extended feature has an entry in the <varname>ext_feature_table</varname>
925 in <filename>opd_extended.cpp</filename>. Each entry contains a feature name,
926 and a corresponding set of handlers. Feature name is a unique string, which is
927 used to identify a feature in the table. Each feature provides a set
929 locations to perform certain tasks. At runtime, the OProfile daemon calls a feature
931 an extended feature is enabled, and whether a particular handler exists.
932 Only the handlers of the enabled feature will be executed.
941 Each feature is enabled using the OProfile daemon (oprofiled) command-line
942 option "--ext-feature=<extended-feature-name>:[args]". The
943 "extended-feature-name" is used to determine the feature to be enabled.
944 The optional "args" is passed into the feature-specific initialization handler
945 (<function>ext_init</function>). Currently, only one extended feature can be
955 Each feature is responsible for providing its own set of handlers.
963 "ext_init" handles initialization of an extended feature. It takes
964 "args" parameter which is passed in through the "oprofiled --ext-feature=<
965 extended-feature-name>:[args]". This handler is executed in the function
982 "ext_print_stats" handles the extended feature statistics report. It adds
997 sample files (sample files for events related to extended feature).
1013 <title>Extended Feature Reference Implementation</title>
1019 An example of extended feature implementation can be seen by
1051 --ext-feature=ibs:\
1057 Here, the OProfile daemon parses the <varname>--ext-feature</varname>
1058 option and checks the feature name ("ibs") before calling the
