|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|
|
|
PROBE::VM.PAGEFAUL(3stap) Memory Tapset PROBE::VM.PAGEFAUL(3stap)
probe::vm.pagefault - Records that a page fault occurred
vm.pagefault
address
the address of the faulting memory access; i.e. the address
that caused the page fault
write_access
indicates whether this was a write or read access; 1
indicates a write, while 0 indicates a read
name
name of the probe point
The process which triggered the fault
tapset::memory(3stap)
This page is part of the systemtap (a tracing and live-system
analysis tool) project. Information about the project can be
found at ⟨https://sourceware.org/systemtap/⟩. If you have a bug
report for this manual page, send it to [email protected].
This page was obtained from the project's upstream Git repository
⟨git://sourceware.org/git/systemtap.git⟩ on 2024-06-14. (At that
time, the date of the most recent commit that was found in the
repository was 2024-06-13.) If you discover any rendering
problems in this HTML version of the page, or you believe there
is a better or more up-to-date source for the page, or you have
corrections or improvements to the information in this COLOPHON
(which is not part of the original manual page), send a mail to
[email protected]
SystemTap Tapset Reference April 2024 PROBE::VM.PAGEFAUL(3stap)
Pages that refer to this page: tapset::memory(3stap)
|
HTML rendering created 2024-06-26 by Michael Kerrisk, author of The Linux Programming Interface. For details of in-depth Linux/UNIX system programming training courses that I teach, look here. Hosting by jambit GmbH. |
|