Lines Matching full:leader
82 /* trigger the leader program on a cpu */
429 if (evsel->core.leader->nr_members > 1) { in bperf_check_target()
465 pr_err("Failed to open leader skeleton\n"); in bperf_reload_leader_program()
472 pr_err("Failed to load leader skeleton\n"); in bperf_reload_leader_program()
478 pr_err("Failed to attach leader program\n"); in bperf_reload_leader_program()
540 * Step 1: hold a fd on the leader program and the bpf_link, if in bperf__load()
565 * The bpf_link holds reference to the leader program, and the in bperf__load()
566 * leader program holds reference to the maps. Therefore, if in bperf__load()
595 /* attach fexit program to the leader program */ in bperf__load()
599 /* connect to leader diff_reading map */ in bperf__load()
660 * trigger the leader prog on each cpu, so the accum_reading map could get
786 * cs -> | leader prog |/ ||/ | |
806 * The leader prog is triggered on each context switch (cs). The leader
809 * multiple perf-stat sessions share the same leader prog.
812 * leader prog. It is possible to attach up to BPF_MAX_TRAMP_PROGS (38)
813 * follower progs to the same leader prog. The follower prog checks current
819 * Besides context switch, it is also necessary to trigger the leader prog
826 * the leader prog.