@@ -64,7 +64,7 @@ This guide is incomplete. If something feels missing, check the bcc and kernel s
-[1. trace_print()](#1-trace_print)
-[2. trace_fields()](#2-trace_fields)
-[Output](#output)
-[1. kprobe_poll()](#1-kprobe_poll)
-[1. perf_buffer_poll()](#1-perf_buffer_poll)
-[Maps](#maps)
-[1. get_table()](#1-get_table)
-[2. open_perf_buffer()](#2-open_perf_buffer)
...
...
@@ -1023,14 +1023,14 @@ Examples in situ:
Normal output from a BPF program is either:
- per-event: using PERF_EVENT_OUTPUT, open_perf_buffer(), and kprobe_poll().
- per-event: using PERF_EVENT_OUTPUT, open_perf_buffer(), and perf_buffer_poll().
- map summary: using items(), or print_log2_hist(), covered in the Maps section.
### 1. kprobe_poll()
### 1. perf_buffer_poll()
Syntax: ```BPF.kprobe_poll()```
Syntax: ```BPF.perf_buffer_poll()```
This polls from the ring buffers for all of the open kprobes, calling the callback function that was given in the BPF constructor for each entry, usually via ```open_perf_buffer()```.
This polls from all open perf ring buffers, calling the callback function that was provided when calling open_perf_buffer for each entry.