Lines Matching refs:to

27 Some tools may have already a way to resolve the kernel functions. These APIs
28 allow them to keep using it instead of duplicating all the entries inside.
31 functions resolver. This function receives a pointer to its custom context
33 function, which has to be resolved. In case of success, it should return
40 _tep_find_function_address()_, and _tep_print_func_field()_ to resolve
41 a function address to a function name.
44 resolver to the default function.  The _tep_ argument is trace event parser
48 These APIs can be used to find function name and start address, by given
49 address. The given address does not have to be exact, it will select
56 by given address _addr_. The _addr_ does not have to be exact, it will select
60 The _tep_register_function()_ function registers a function name mapped to an
62 or events have "%pS" parameter in its format string. It is common to pass in
70 it was stored in the kernel. Some strings internal to the kernel with static
71 address are passed to certain events. The "%s" in the event's format field
72 which has an address needs to know what string would be at that address. The
75 context. The _fmt_ is the string to register, it is copied internally.
91 an error -1 is returned, and errno is set to the appropriate error number.
94 of an error -1 is returned, and errno is set to the appropriate error number.
124 		/* failed to register my_resolve_kernel_addr */
127 	/* These APIs use my_resolve_kernel_addr() to resolve the addr */
142 		/* Failed to register kvm_exit address mapping */
147 		/* Failed to register "print string" address mapping */
157 	Header file to include in order to have access to the library APIs.
159 	Linker switch to add when building a program that uses the library.
175 Report bugs to  <linux-trace-devel@vger.kernel.org>