€•_ŸŒsphinx.addnodes”Œdocument”“”)”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)”}”(hhh]”(hŒ pending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ%/translations/zh_CN/trace/kprobetrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ%/translations/zh_TW/trace/kprobetrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ%/translations/it_IT/trace/kprobetrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ%/translations/ja_JP/trace/kprobetrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ%/translations/ko_KR/trace/kprobetrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ%/translations/sp_SP/trace/kprobetrace”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒKprobe-based Event Tracing”h]”hŒKprobe-based Event Tracing”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒ?/var/lib/git/docbuild/linux/Documentation/trace/kprobetrace.rst”h KubhŒ field_list”“”)”}”(hhh]”hŒfield”“”)”}”(hhh]”(hŒ field_name”“”)”}”(hŒAuthor”h]”hŒAuthor”…””}”(hhÃhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÁhh¾hŸh¶h KubhŒ field_body”“”)”}”(hŒMasami Hiramatsu ”h]”hŒ paragraph”“”)”}”(hŒMasami Hiramatsu”h]”hŒMasami Hiramatsu”…””}”(hhÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KhhÓubah}”(h]”h ]”h"]”h$]”h&]”uh1hÑhh¾ubeh}”(h]”h ]”h"]”h$]”h&]”uh1h¼hŸh¶h Khh¹hžhubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒOverview”h]”hŒOverview”…””}”(hhühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hhùhžhhŸh¶h KubhØ)”}”(hXwThese events are similar to tracepoint-based events. Instead of tracepoints, this is based on kprobes (kprobe and kretprobe). So it can probe wherever kprobes can probe (this means, all functions except those with __kprobes/nokprobe_inline annotation and those marked NOKPROBE_SYMBOL). Unlike the tracepoint-based event, this can be added and removed dynamically, on the fly.”h]”hXwThese events are similar to tracepoint-based events. Instead of tracepoints, this is based on kprobes (kprobe and kretprobe). So it can probe wherever kprobes can probe (this means, all functions except those with __kprobes/nokprobe_inline annotation and those marked NOKPROBE_SYMBOL). Unlike the tracepoint-based event, this can be added and removed dynamically, on the fly.”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K hhùhžhubhØ)”}”(hŒFTo enable this feature, build your kernel with CONFIG_KPROBE_EVENTS=y.”h]”hŒFTo enable this feature, build your kernel with CONFIG_KPROBE_EVENTS=y.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KhhùhžhubhØ)”}”(hŒàSimilar to the event tracer, this doesn't need to be activated via current_tracer. Instead of that, add probe points via /sys/kernel/tracing/kprobe_events, and enable it via /sys/kernel/tracing/events/kprobes//enable.”h]”hŒâSimilar to the event tracer, this doesn’t need to be activated via current_tracer. Instead of that, add probe points via /sys/kernel/tracing/kprobe_events, and enable it via /sys/kernel/tracing/events/kprobes//enable.”…””}”(hj&hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KhhùhžhubhØ)”}”(hŒ•You can also use /sys/kernel/tracing/dynamic_events instead of kprobe_events. That interface will provide unified access to other dynamic events too.”h]”hŒ•You can also use /sys/kernel/tracing/dynamic_events instead of kprobe_events. That interface will provide unified access to other dynamic events too.”…””}”(hj4hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Khhùhžhubeh}”(h]”Œoverview”ah ]”h"]”Œoverview”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒSynopsis of kprobe_events”h]”hŒSynopsis of kprobe_events”…””}”(hjMhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjJhžhhŸh¶h KubhŒ literal_block”“”)”}”(hX¾ p[:[GRP/][EVENT]] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe r[MAXACTIVE][:[GRP/][EVENT]] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe p[:[GRP/][EVENT]] [MOD:]SYM[+0]%return [FETCHARGS] : Set a return probe -:[GRP/][EVENT] : Clear a probe GRP : Group name. If omitted, use "kprobes" for it. EVENT : Event name. If omitted, the event name is generated based on SYM+offs or MEMADDR. MOD : Module name which has given SYM. SYM[+offs] : Symbol+offset where the probe is inserted. SYM%return : Return address of the symbol MEMADDR : Address where the probe is inserted. MAXACTIVE : Maximum number of instances of the specified function that can be probed simultaneously, or 0 for the default value as defined in Documentation/trace/kprobes.rst section 1.3.1. FETCHARGS : Arguments. Each probe can have up to 128 args. %REG : Fetch register REG @ADDR : Fetch memory at ADDR (ADDR should be in kernel) @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) $stackN : Fetch Nth entry of stack (N >= 0) $stack : Fetch stack address. $argN : Fetch the Nth function argument. (N >= 1) (\*1) $retval : Fetch return value.(\*2) $comm : Fetch current task comm. +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*3)(\*4) \IMM : Store an immediate value to the argument. NAME=FETCHARG : Set NAME as the argument name of FETCHARG. FETCHARG:TYPE : Set TYPE as the type of FETCHARG. Currently, basic types (u8/u16/u32/u64/s8/s16/s32/s64), hexadecimal types (x8/x16/x32/x64), VFS layer common type(%pd/%pD), "char", "string", "ustring", "symbol", "symstr" and bitfield are supported. (\*1) only for the probe on function entry (offs == 0). Note, this argument access is best effort, because depending on the argument type, it may be passed on the stack. But this only support the arguments via registers. (\*2) only for return probe. Note that this is also best effort. Depending on the return value type, it might be passed via a pair of registers. But this only accesses one register. (\*3) this is useful for fetching a field of data structures. (\*4) "u" means user-space dereference. See :ref:`user_mem_access`.”h]”hX¾ p[:[GRP/][EVENT]] [MOD:]SYM[+offs]|MEMADDR [FETCHARGS] : Set a probe r[MAXACTIVE][:[GRP/][EVENT]] [MOD:]SYM[+0] [FETCHARGS] : Set a return probe p[:[GRP/][EVENT]] [MOD:]SYM[+0]%return [FETCHARGS] : Set a return probe -:[GRP/][EVENT] : Clear a probe GRP : Group name. If omitted, use "kprobes" for it. EVENT : Event name. If omitted, the event name is generated based on SYM+offs or MEMADDR. MOD : Module name which has given SYM. SYM[+offs] : Symbol+offset where the probe is inserted. SYM%return : Return address of the symbol MEMADDR : Address where the probe is inserted. MAXACTIVE : Maximum number of instances of the specified function that can be probed simultaneously, or 0 for the default value as defined in Documentation/trace/kprobes.rst section 1.3.1. FETCHARGS : Arguments. Each probe can have up to 128 args. %REG : Fetch register REG @ADDR : Fetch memory at ADDR (ADDR should be in kernel) @SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol) $stackN : Fetch Nth entry of stack (N >= 0) $stack : Fetch stack address. $argN : Fetch the Nth function argument. (N >= 1) (\*1) $retval : Fetch return value.(\*2) $comm : Fetch current task comm. +|-[u]OFFS(FETCHARG) : Fetch memory at FETCHARG +|- OFFS address.(\*3)(\*4) \IMM : Store an immediate value to the argument. NAME=FETCHARG : Set NAME as the argument name of FETCHARG. FETCHARG:TYPE : Set TYPE as the type of FETCHARG. Currently, basic types (u8/u16/u32/u64/s8/s16/s32/s64), hexadecimal types (x8/x16/x32/x64), VFS layer common type(%pd/%pD), "char", "string", "ustring", "symbol", "symstr" and bitfield are supported. (\*1) only for the probe on function entry (offs == 0). Note, this argument access is best effort, because depending on the argument type, it may be passed on the stack. But this only support the arguments via registers. (\*2) only for return probe. Note that this is also best effort. Depending on the return value type, it might be passed via a pair of registers. But this only accesses one register. (\*3) this is useful for fetching a field of data structures. (\*4) "u" means user-space dereference. See :ref:`user_mem_access`.”…””}”hj]sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1j[hŸh¶h KhjJhžhubeh}”(h]”Œsynopsis-of-kprobe-events”ah ]”h"]”Œsynopsis of kprobe_events”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒFunction arguments at kretprobe”h]”hŒFunction arguments at kretprobe”…””}”(hjxhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjuhžhhŸh¶h KKubhØ)”}”(hXmFunction arguments can be accessed at kretprobe using $arg fetcharg. This is useful to record the function parameter and return value at once, and trace the difference of structure fields (for debugging a function whether it correctly updates the given data structure or not). See the :ref:`sample` in fprobe event for how it works.”h]”(hX Function arguments can be accessed at kretprobe using $arg fetcharg. This is useful to record the function parameter and return value at once, and trace the difference of structure fields (for debugging a function whether it correctly updates the given data structure or not). See the ”…””}”(hj†hžhhŸNh Nubh)”}”(hŒ+:ref:`sample`”h]”hŒinline”“”)”}”(hjh]”hŒsample”…””}”(hj”hžhhŸNh Nubah}”(h]”h ]”(Œxref”Œstd”Œstd-ref”eh"]”h$]”h&]”uh1j’hjŽubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”Œtrace/kprobetrace”Œ refdomain”jŸŒreftype”Œref”Œ refexplicit”ˆŒrefwarn”ˆŒ reftarget”Œfprobetrace_exit_args_sample”uh1hhŸh¶h KLhj†ubhŒ" in fprobe event for how it works.”…””}”(hj†hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KLhjuhžhubhŒtarget”“”)”}”(hŒ.. _kprobetrace_types:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œkprobetrace-types”uh1j½h KShjuhžhhŸh¶ubeh}”(h]”Œfunction-arguments-at-kretprobe”ah ]”h"]”Œfunction arguments at kretprobe”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KKubh¢)”}”(hhh]”(h§)”}”(hŒTypes”h]”hŒTypes”…””}”(hjÖhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÓhžhhŸh¶h KVubhØ)”}”(hXˆSeveral types are supported for fetchargs. Kprobe tracer will access memory by given type. Prefix 's' and 'u' means those types are signed and unsigned respectively. 'x' prefix implies it is unsigned. Traced arguments are shown in decimal ('s' and 'u') or hexadecimal ('x'). Without type casting, 'x32' or 'x64' is used depends on the architecture (e.g. x86-32 uses x32, and x86-64 uses x64).”h]”hX¨Several types are supported for fetchargs. Kprobe tracer will access memory by given type. Prefix ‘s’ and ‘u’ means those types are signed and unsigned respectively. ‘x’ prefix implies it is unsigned. Traced arguments are shown in decimal (‘s’ and ‘u’) or hexadecimal (‘x’). Without type casting, ‘x32’ or ‘x64’ is used depends on the architecture (e.g. x86-32 uses x32, and x86-64 uses x64).”…””}”(hjähžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KWhjÓhžhubhØ)”}”(hXThese value types can be an array. To record array data, you can add '[N]' (where N is a fixed number, less than 64) to the base type. E.g. 'x16[4]' means an array of x16 (2-byte hex) with 4 elements. Note that the array can be applied to memory type fetchargs, you can not apply it to registers/stack-entries etc. (for example, '$stack1:x8[8]' is wrong, but '+8($stack):x8[8]' is OK.)”h]”hX‘These value types can be an array. To record array data, you can add ‘[N]’ (where N is a fixed number, less than 64) to the base type. E.g. ‘x16[4]’ means an array of x16 (2-byte hex) with 4 elements. Note that the array can be applied to memory type fetchargs, you can not apply it to registers/stack-entries etc. (for example, ‘$stack1:x8[8]’ is wrong, but ‘+8($stack):x8[8]’ is OK.)”…””}”(hjòhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K^hjÓhžhubhØ)”}”(hŒFChar type can be used to show the character value of traced arguments.”h]”hŒFChar type can be used to show the character value of traced arguments.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KehjÓhžhubhØ)”}”(hXString type is a special type, which fetches a "null-terminated" string from kernel space. This means it will fail and store NULL if the string container has been paged out. "ustring" type is an alternative of string for user-space. See :ref:`user_mem_access` for more info.”h]”(hŒõString type is a special type, which fetches a “null-terminated†string from kernel space. This means it will fail and store NULL if the string container has been paged out. “ustring†type is an alternative of string for user-space. See ”…””}”(hjhžhhŸNh Nubh)”}”(hŒ:ref:`user_mem_access`”h]”j“)”}”(hjh]”hŒuser_mem_access”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”(jžŒstd”Œstd-ref”eh"]”h$]”h&]”uh1j’hjubah}”(h]”h ]”h"]”h$]”h&]”Œrefdoc”j«Œ refdomain”j$Œreftype”Œref”Œ refexplicit”‰Œrefwarn”ˆj±Œuser_mem_access”uh1hhŸh¶h KghjubhŒ for more info.”…””}”(hjhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KghjÓhžhubhØ)”}”(hXôThe string array type is a bit different from other types. For other base types, [1] is equal to (e.g. +0(%di):x32[1] is same as +0(%di):x32.) But string[1] is not equal to string. The string type itself represents "char array", but string array type represents "char * array". So, for example, +0(%di):string[1] is equal to +0(+0(%di)):string. Bitfield is another special type, which takes 3 parameters, bit-width, bit- offset, and container-size (usually 32). The syntax is::”h]”hXûThe string array type is a bit different from other types. For other base types, [1] is equal to (e.g. +0(%di):x32[1] is same as +0(%di):x32.) But string[1] is not equal to string. The string type itself represents “char arrayâ€, but string array type represents “char * arrayâ€. So, for example, +0(%di):string[1] is equal to +0(+0(%di)):string. Bitfield is another special type, which takes 3 parameters, bit-width, bit- offset, and container-size (usually 32). The syntax is:”…””}”(hj@hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KlhjÓhžhubj\)”}”(hŒ*b@/”h]”hŒ*b@/”…””}”hjNsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KthjÓhžhubhØ)”}”(hXêSymbol type('symbol') is an alias of u32 or u64 type (depends on BITS_PER_LONG) which shows given pointer in "symbol+offset" style. On the other hand, symbol-string type ('symstr') converts the given address to "symbol+offset/symbolsize" style and stores it as a null-terminated string. With 'symstr' type, you can filter the event with wildcard pattern of the symbols, and you don't need to solve symbol name by yourself. For $comm, the default type is "string"; any other type is invalid.”h]”hXSymbol type(‘symbol’) is an alias of u32 or u64 type (depends on BITS_PER_LONG) which shows given pointer in “symbol+offset†style. On the other hand, symbol-string type (‘symstr’) converts the given address to “symbol+offset/symbolsize†style and stores it as a null-terminated string. With ‘symstr’ type, you can filter the event with wildcard pattern of the symbols, and you don’t need to solve symbol name by yourself. For $comm, the default type is “stringâ€; any other type is invalid.”…””}”(hj\hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KvhjÓhžhubhØ)”}”(hŒŽVFS layer common type(%pd/%pD) is a special type, which fetches dentry's or file's name from struct dentry's address or struct file's address.”h]”hŒ–VFS layer common type(%pd/%pD) is a special type, which fetches dentry’s or file’s name from struct dentry’s address or struct file’s address.”…””}”(hjjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K~hjÓhžhubj¾)”}”(hŒ.. _user_mem_access:”h]”h}”(h]”h ]”h"]”h$]”h&]”jÉŒuser-mem-access”uh1j½h KhjÓhžhhŸh¶ubeh}”(h]”(Œtypes”jÊeh ]”h"]”(Œtypes”Œkprobetrace_types”eh$]”h&]”uh1h¡hh£hžhhŸh¶h KVŒexpect_referenced_by_name”}”j‰j¿sŒexpect_referenced_by_id”}”jÊj¿subh¢)”}”(hhh]”(h§)”}”(hŒUser Memory Access”h]”hŒUser Memory Access”…””}”(hj“hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjhžhhŸh¶h K„ubhØ)”}”(hŒ†Kprobe events supports user-space memory access. For that purpose, you can use either user-space dereference syntax or 'ustring' type.”h]”hŒŠKprobe events supports user-space memory access. For that purpose, you can use either user-space dereference syntax or ‘ustring’ type.”…””}”(hj¡hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K…hjhžhubhØ)”}”(hX>The user-space dereference syntax allows you to access a field of a data structure in user-space. This is done by adding the "u" prefix to the dereference syntax. For example, +u4(%si) means it will read memory from the address in the register %si offset by 4, and the memory is expected to be in user-space. You can use this for strings too, e.g. +u0(%si):string will read a string from the address in the register %si that is expected to be in user- space. 'ustring' is a shortcut way of performing the same task. That is, +0(%si):ustring is equivalent to +u0(%si):string.”h]”hXFThe user-space dereference syntax allows you to access a field of a data structure in user-space. This is done by adding the “u†prefix to the dereference syntax. For example, +u4(%si) means it will read memory from the address in the register %si offset by 4, and the memory is expected to be in user-space. You can use this for strings too, e.g. +u0(%si):string will read a string from the address in the register %si that is expected to be in user- space. ‘ustring’ is a shortcut way of performing the same task. That is, +0(%si):ustring is equivalent to +u0(%si):string.”…””}”(hj¯hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KˆhjhžhubhØ)”}”(hX4Note that kprobe-event provides the user-memory access syntax but it doesn't use it transparently. This means if you use normal dereference or string type for user memory, it might fail, and may always fail on some architectures. The user has to carefully check if the target data is in kernel or user space.”h]”hX6Note that kprobe-event provides the user-memory access syntax but it doesn’t use it transparently. This means if you use normal dereference or string type for user memory, it might fail, and may always fail on some architectures. The user has to carefully check if the target data is in kernel or user space.”…””}”(hj½hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K‘hjhžhubeh}”(h]”(Œuser-memory-access”j‚eh ]”h"]”(Œuser memory access”Œuser_mem_access”eh$]”h&]”uh1h¡hh£hžhhŸh¶h K„jŒ}”jÑjxsjŽ}”j‚jxsubh¢)”}”(hhh]”(h§)”}”(hŒPer-Probe Event Filtering”h]”hŒPer-Probe Event Filtering”…””}”(hjÙhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÖhžhhŸh¶h K—ubhØ)”}”(hX]Per-probe event filtering feature allows you to set different filter on each probe and gives you what arguments will be shown in trace buffer. If an event name is specified right after 'p:' or 'r:' in kprobe_events, it adds an event under tracing/events/kprobes/, at the directory you can see 'id', 'enable', 'format', 'filter' and 'trigger'.”h]”hXyPer-probe event filtering feature allows you to set different filter on each probe and gives you what arguments will be shown in trace buffer. If an event name is specified right after ‘p:’ or ‘r:’ in kprobe_events, it adds an event under tracing/events/kprobes/, at the directory you can see ‘id’, ‘enable’, ‘format’, ‘filter’ and ‘trigger’.”…””}”(hjçhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K˜hjÖhžhubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒBenable: You can enable/disable the probe by writing 1 or 0 on it. ”h]”(hŒterm”“”)”}”(hŒenable:”h]”hŒenable:”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhŸh¶h KŸhjüubhŒ definition”“”)”}”(hhh]”hØ)”}”(hŒ9You can enable/disable the probe by writing 1 or 0 on it.”h]”hŒ9You can enable/disable the probe by writing 1 or 0 on it.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KŸhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjüubeh}”(h]”h ]”h"]”h$]”h&]”uh1júhŸh¶h KŸhj÷ubjû)”}”(hŒ3format: This shows the format of this probe event. ”h]”(j)”}”(hŒformat:”h]”hŒformat:”…””}”(hj3hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhŸh¶h K¢hj/ubj)”}”(hhh]”hØ)”}”(hŒ*This shows the format of this probe event.”h]”hŒ*This shows the format of this probe event.”…””}”(hjDhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K¢hjAubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj/ubeh}”(h]”h ]”h"]”h$]”h&]”uh1júhŸh¶h K¢hj÷hžhubjû)”}”(hŒ5filter: You can write filtering rules of this event. ”h]”(j)”}”(hŒfilter:”h]”hŒfilter:”…””}”(hjbhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhŸh¶h K¥hj^ubj)”}”(hhh]”hØ)”}”(hŒ,You can write filtering rules of this event.”h]”hŒ,You can write filtering rules of this event.”…””}”(hjshžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K¥hjpubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj^ubeh}”(h]”h ]”h"]”h$]”h&]”uh1júhŸh¶h K¥hj÷hžhubjû)”}”(hŒ+id: This shows the id of this probe event. ”h]”(j)”}”(hŒid:”h]”hŒid:”…””}”(hj‘hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhŸh¶h K¨hjubj)”}”(hhh]”hØ)”}”(hŒ&This shows the id of this probe event.”h]”hŒ&This shows the id of this probe event.”…””}”(hj¢hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K¨hjŸubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1júhŸh¶h K¨hj÷hžhubjû)”}”(hŒ˜trigger: This allows to install trigger commands which are executed when the event is hit (for details, see Documentation/trace/events.rst, section 6). ”h]”(j)”}”(hŒtrigger:”h]”hŒtrigger:”…””}”(hjÀhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhŸh¶h K¬hj¼ubj)”}”(hhh]”hØ)”}”(hŒŽThis allows to install trigger commands which are executed when the event is hit (for details, see Documentation/trace/events.rst, section 6).”h]”hŒŽThis allows to install trigger commands which are executed when the event is hit (for details, see Documentation/trace/events.rst, section 6).”…””}”(hjÑhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K«hjÎubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj¼ubeh}”(h]”h ]”h"]”h$]”h&]”uh1júhŸh¶h K¬hj÷hžhubeh}”(h]”h ]”h"]”h$]”h&]”uh1jõhjÖhžhhŸh¶h Nubeh}”(h]”Œper-probe-event-filtering”ah ]”h"]”Œper-probe event filtering”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K—ubh¢)”}”(hhh]”(h§)”}”(hŒEvent Profiling”h]”hŒEvent Profiling”…””}”(hjühžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjùhžhhŸh¶h K¯ubhØ)”}”(hŒÜYou can check the total number of probe hits and probe miss-hits via /sys/kernel/tracing/kprobe_profile. The first column is event name, the second is the number of probe hits, the third is the number of probe miss-hits.”h]”hŒÜYou can check the total number of probe hits and probe miss-hits via /sys/kernel/tracing/kprobe_profile. The first column is event name, the second is the number of probe hits, the third is the number of probe miss-hits.”…””}”(hj hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K°hjùhžhubeh}”(h]”Œevent-profiling”ah ]”h"]”Œevent profiling”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K¯ubh¢)”}”(hhh]”(h§)”}”(hŒKernel Boot Parameter”h]”hŒKernel Boot Parameter”…””}”(hj#hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj hžhhŸh¶h K¶ubhØ)”}”(hXeYou can add and enable new kprobe events when booting up the kernel by "kprobe_event=" parameter. The parameter accepts a semicolon-delimited kprobe events, which format is similar to the kprobe_events. The difference is that the probe definition parameters are comma-delimited instead of space. For example, adding myprobe event on do_sys_open like below::”h]”hXhYou can add and enable new kprobe events when booting up the kernel by “kprobe_event=†parameter. The parameter accepts a semicolon-delimited kprobe events, which format is similar to the kprobe_events. The difference is that the probe definition parameters are comma-delimited instead of space. For example, adding myprobe event on do_sys_open like below:”…””}”(hj1hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K·hj hžhubj\)”}”(hŒDp:myprobe do_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)”h]”hŒDp:myprobe do_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)”…””}”hj?sbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h K½hj hžhubhØ)”}”(hŒLshould be below for kernel boot parameter (just replace spaces with comma)::”h]”hŒKshould be below for kernel boot parameter (just replace spaces with comma):”…””}”(hjMhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h K¿hj hžhubj\)”}”(hŒDp:myprobe,do_sys_open,dfd=%ax,filename=%dx,flags=%cx,mode=+4($stack)”h]”hŒDp:myprobe,do_sys_open,dfd=%ax,filename=%dx,flags=%cx,mode=+4($stack)”…””}”hj[sbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KÁhj hžhubeh}”(h]”Œkernel-boot-parameter”ah ]”h"]”Œkernel boot parameter”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K¶ubh¢)”}”(hhh]”(h§)”}”(hŒUsage examples”h]”hŒUsage examples”…””}”(hjthžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjqhžhhŸh¶h KÅubhØ)”}”(hŒQTo add a probe as a new event, write a new definition to kprobe_events as below::”h]”hŒPTo add a probe as a new event, write a new definition to kprobe_events as below:”…””}”(hj‚hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KÆhjqhžhubj\)”}”(hŒoecho 'p:myprobe do_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/tracing/kprobe_events”h]”hŒoecho 'p:myprobe do_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/tracing/kprobe_events”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KÉhjqhžhubhØ)”}”(hX”This sets a kprobe on the top of do_sys_open() function with recording 1st to 4th arguments as "myprobe" event. Note, which register/stack entry is assigned to each function argument depends on arch-specific ABI. If you unsure the ABI, please try to use probe subcommand of perf-tools (you can find it under tools/perf/). As this example shows, users can choose more familiar names for each arguments. ::”h]”hX•This sets a kprobe on the top of do_sys_open() function with recording 1st to 4th arguments as “myprobe†event. Note, which register/stack entry is assigned to each function argument depends on arch-specific ABI. If you unsure the ABI, please try to use probe subcommand of perf-tools (you can find it under tools/perf/). As this example shows, users can choose more familiar names for each arguments.”…””}”(hjžhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KËhjqhžhubj\)”}”(hŒLecho 'r:myretprobe do_sys_open $retval' >> /sys/kernel/tracing/kprobe_events”h]”hŒLecho 'r:myretprobe do_sys_open $retval' >> /sys/kernel/tracing/kprobe_events”…””}”hj¬sbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KÓhjqhžhubhØ)”}”(hŒ×This sets a kretprobe on the return point of do_sys_open() function with recording return value as "myretprobe" event. You can see the format of these events via /sys/kernel/tracing/events/kprobes//format. ::”h]”hŒØThis sets a kretprobe on the return point of do_sys_open() function with recording return value as “myretprobe†event. You can see the format of these events via /sys/kernel/tracing/events/kprobes//format.”…””}”(hjºhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KÕhjqhžhubj\)”}”(hXÇcat /sys/kernel/tracing/events/kprobes/myprobe/format name: myprobe ID: 780 format: field:unsigned short common_type; offset:0; size:2; signed:0; field:unsigned char common_flags; offset:2; size:1; signed:0; field:unsigned char common_preempt_count; offset:3; size:1;signed:0; field:int common_pid; offset:4; size:4; signed:1; field:unsigned long __probe_ip; offset:12; size:4; signed:0; field:int __probe_nargs; offset:16; size:4; signed:1; field:unsigned long dfd; offset:20; size:4; signed:0; field:unsigned long filename; offset:24; size:4; signed:0; field:unsigned long flags; offset:28; size:4; signed:0; field:unsigned long mode; offset:32; size:4; signed:0; print fmt: "(%lx) dfd=%lx filename=%lx flags=%lx mode=%lx", REC->__probe_ip, REC->dfd, REC->filename, REC->flags, REC->mode”h]”hXÇcat /sys/kernel/tracing/events/kprobes/myprobe/format name: myprobe ID: 780 format: field:unsigned short common_type; offset:0; size:2; signed:0; field:unsigned char common_flags; offset:2; size:1; signed:0; field:unsigned char common_preempt_count; offset:3; size:1;signed:0; field:int common_pid; offset:4; size:4; signed:1; field:unsigned long __probe_ip; offset:12; size:4; signed:0; field:int __probe_nargs; offset:16; size:4; signed:1; field:unsigned long dfd; offset:20; size:4; signed:0; field:unsigned long filename; offset:24; size:4; signed:0; field:unsigned long flags; offset:28; size:4; signed:0; field:unsigned long mode; offset:32; size:4; signed:0; print fmt: "(%lx) dfd=%lx filename=%lx flags=%lx mode=%lx", REC->__probe_ip, REC->dfd, REC->filename, REC->flags, REC->mode”…””}”hjÈsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KÛhjqhžhubhØ)”}”(hŒRYou can see that the event has 4 arguments as in the expressions you specified. ::”h]”hŒOYou can see that the event has 4 arguments as in the expressions you specified.”…””}”(hjÖhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kïhjqhžhubj\)”}”(hŒ(echo > /sys/kernel/tracing/kprobe_events”h]”hŒ(echo > /sys/kernel/tracing/kprobe_events”…””}”hjäsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KòhjqhžhubhØ)”}”(hŒThis clears all probe points.”h]”hŒThis clears all probe points.”…””}”(hjòhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KôhjqhžhubhØ)”}”(hŒOr, ::”h]”hŒOr,”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Köhjqhžhubj\)”}”(hŒecho -:myprobe >> kprobe_events”h]”hŒecho -:myprobe >> kprobe_events”…””}”hjsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h KùhjqhžhubhØ)”}”(hŒ%This clears probe points selectively.”h]”hŒ%This clears probe points selectively.”…””}”(hjhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h KûhjqhžhubhØ)”}”(hŒnRight after definition, each event is disabled by default. For tracing these events, you need to enable it. ::”h]”hŒkRight after definition, each event is disabled by default. For tracing these events, you need to enable it.”…””}”(hj*hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Kýhjqhžhubj\)”}”(hŒxecho 1 > /sys/kernel/tracing/events/kprobes/myprobe/enable echo 1 > /sys/kernel/tracing/events/kprobes/myretprobe/enable”h]”hŒxecho 1 > /sys/kernel/tracing/events/kprobes/myprobe/enable echo 1 > /sys/kernel/tracing/events/kprobes/myretprobe/enable”…””}”hj8sbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h MhjqhžhubhØ)”}”(hŒ=Use the following command to start tracing in an interval. ::”h]”hŒ:Use the following command to start tracing in an interval.”…””}”(hjFhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Mhjqhžhubj\)”}”(hŒ=# echo 1 > tracing_on Open something... # echo 0 > tracing_on”h]”hŒ=# echo 1 > tracing_on Open something... # echo 0 > tracing_on”…””}”hjTsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h MhjqhžhubhØ)”}”(hŒHAnd you can see the traced information via /sys/kernel/tracing/trace. ::”h]”hŒEAnd you can see the traced information via /sys/kernel/tracing/trace.”…””}”(hjbhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h M hjqhžhubj\)”}”(hXLcat /sys/kernel/tracing/trace # tracer: nop # # TASK-PID CPU# TIMESTAMP FUNCTION # | | | | | <...>-1447 [001] 1038282.286875: myprobe: (do_sys_open+0x0/0xd6) dfd=3 filename=7fffd1ec4440 flags=8000 mode=0 <...>-1447 [001] 1038282.286878: myretprobe: (sys_openat+0xc/0xe <- do_sys_open) $retval=fffffffffffffffe <...>-1447 [001] 1038282.286885: myprobe: (do_sys_open+0x0/0xd6) dfd=ffffff9c filename=40413c flags=8000 mode=1b6 <...>-1447 [001] 1038282.286915: myretprobe: (sys_open+0x1b/0x1d <- do_sys_open) $retval=3 <...>-1447 [001] 1038282.286969: myprobe: (do_sys_open+0x0/0xd6) dfd=ffffff9c filename=4041c6 flags=98800 mode=10 <...>-1447 [001] 1038282.286976: myretprobe: (sys_open+0x1b/0x1d <- do_sys_open) $retval=3”h]”hXLcat /sys/kernel/tracing/trace # tracer: nop # # TASK-PID CPU# TIMESTAMP FUNCTION # | | | | | <...>-1447 [001] 1038282.286875: myprobe: (do_sys_open+0x0/0xd6) dfd=3 filename=7fffd1ec4440 flags=8000 mode=0 <...>-1447 [001] 1038282.286878: myretprobe: (sys_openat+0xc/0xe <- do_sys_open) $retval=fffffffffffffffe <...>-1447 [001] 1038282.286885: myprobe: (do_sys_open+0x0/0xd6) dfd=ffffff9c filename=40413c flags=8000 mode=1b6 <...>-1447 [001] 1038282.286915: myretprobe: (sys_open+0x1b/0x1d <- do_sys_open) $retval=3 <...>-1447 [001] 1038282.286969: myprobe: (do_sys_open+0x0/0xd6) dfd=ffffff9c filename=4041c6 flags=98800 mode=10 <...>-1447 [001] 1038282.286976: myretprobe: (sys_open+0x1b/0x1d <- do_sys_open) $retval=3”…””}”hjpsbah}”(h]”h ]”h"]”h$]”h&]”jkjluh1j[hŸh¶h MhjqhžhubhØ)”}”(hŒ¿Each line shows when the kernel hits an event, and <- SYMBOL means kernel returns from SYMBOL(e.g. "sys_open+0x1b/0x1d <- do_sys_open" means kernel returns from do_sys_open to sys_open+0x1b).”h]”hŒÃEach line shows when the kernel hits an event, and <- SYMBOL means kernel returns from SYMBOL(e.g. “sys_open+0x1b/0x1d <- do_sys_open†means kernel returns from do_sys_open to sys_open+0x1b).”…””}”(hj~hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hŸh¶h Mhjqhžhubeh}”(h]”Œusage-examples”ah ]”h"]”Œusage examples”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KÅubeh}”(h]”Œkprobe-based-event-tracing”ah ]”h"]”Œkprobe-based event tracing”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j¿Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”(jÊ]”j¿aj‚]”jxauŒnameids”}”(j™j–jGjDjrjojÐjÍj‰jÊjˆj…jÑj‚jÐjÍjöjójjjnjkj‘jŽuŒ nametypes”}”(j™‰jG‰jr‰jЉj‰ˆjˆ‰jшjЉjö‰j‰jn‰j‘‰uh}”(j–h£jDhùjojJjÍjujÊjÓj…jÓj‚jjÍjjójÖjjùjkj jŽjquŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”(hŒsystem_message”“”)”}”(hhh]”hØ)”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…””}”(hj(hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj%ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œline”KðŒsource”h¶uh1j#hjqhžhhŸh¶h Kðubj$)”}”(hhh]”hØ)”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…””}”(hjDhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hjAubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j>Œline”K÷Œsource”h¶uh1j#hjqhžhhŸh¶h K÷ubj$)”}”(hhh]”hØ)”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…””}”(hj_hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj\ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j>Œline”MŒsource”h¶uh1j#hjqhžhhŸh¶h Mubj$)”}”(hhh]”hØ)”}”(hŒfPossible title underline, too short for the title. Treating it as ordinary text because it's so short.”h]”hŒhPossible title underline, too short for the title. Treating it as ordinary text because it’s so short.”…””}”(hjzhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h×hjwubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j>Œline”M Œsource”h¶uh1j#hjqhžhhŸh¶h M ubeŒtransform_messages”]”(j$)”}”(hhh]”hØ)”}”(hhh]”hŒ7Hyperlink target "kprobetrace-types" is not referenced.”…””}”hj—sbah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj”ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j>Œsource”h¶Œline”KSuh1j#ubj$)”}”(hhh]”hØ)”}”(hhh]”hŒ5Hyperlink target "user-mem-access" is not referenced.”…””}”hj±sbah}”(h]”h ]”h"]”h$]”h&]”uh1h×hj®ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”j>Œsource”h¶Œline”Kuh1j#ubeŒ transformer”NŒ include_log”]”Œ decoration”Nhžhub.