Searched refs:perf_events (Results  1 – 10 of 10) sorted by relevance
| /Linux-v5.4/drivers/oprofile/ | 
| D | oprofile_perf.c | 30 static DEFINE_PER_CPU(struct perf_event **, perf_events);43 		if (per_cpu(perf_events, cpu)[id] == event)  in op_overflow_handler()  local
 79 	if (!counter_config[event].enabled || per_cpu(perf_events, cpu)[event])  in op_create_counter()
 96 	per_cpu(perf_events, cpu)[event] = pevent;  in op_create_counter()  local
 103 	struct perf_event *pevent = per_cpu(perf_events, cpu)[event];  in op_destroy_counter()
 107 		per_cpu(perf_events, cpu)[event] = NULL;  in op_destroy_counter()  local
 262 			event = per_cpu(perf_events, cpu)[id];  in oprofile_perf_exit()
 267 		kfree(per_cpu(perf_events, cpu));  in oprofile_perf_exit()
 301 		per_cpu(perf_events, cpu) = kcalloc(num_counters,  in oprofile_perf_init()
 303 		if (!per_cpu(perf_events, cpu)) {  in oprofile_perf_init()
 
 | 
| /Linux-v5.4/Documentation/admin-guide/ | 
| D | perf-security.rst | 9 Usage of Performance Counters for Linux (perf_events) [1]_ , [2]_ , [3]_12 direct usage of perf_events system call API [2]_ and over data files
 14 depends on the nature of data that perf_events performance monitoring
 46 properly. So, perf_events/Perf performance monitoring is the subject for
 49 perf_events/Perf access control
 56 all kernel security permission checks so perf_events performance
 70 as privileged processes with respect to perf_events performance
 73 Unprivileged processes using perf_events system call API is also subject
 85 perf_events/Perf privileged users
 90 perf_events/Perf privileged users who are permitted to execute
 [all …]
 
 | 
| /Linux-v5.4/kernel/trace/ | 
| D | trace_event_perf.c | 109 	tp_event->perf_events = list;  in perf_trace_event_reg()142 		free_percpu(tp_event->perf_events);  in perf_trace_event_reg()
 143 		tp_event->perf_events = NULL;  in perf_trace_event_reg()
 165 	free_percpu(tp_event->perf_events);  in perf_trace_event_unreg()
 166 	tp_event->perf_events = NULL;  in perf_trace_event_unreg()
 366 		pcpu_list = tp_event->perf_events;  in perf_trace_add()
 
 | 
| D | trace_uprobe.c | 40 	struct list_head	perf_events;  member271 	INIT_LIST_HEAD(&filter->perf_events);  in NOKPROBE_SYMBOL()
 276 	return !filter->nr_systemwide && list_empty(&filter->perf_events);  in uprobe_filter_is_empty()
 1199 	list_for_each_entry(event, &filter->perf_events, hw.tp_list) {  in __uprobe_perf_filter()
 1253 		list_add(&event->hw.tp_list, &tu->filter.perf_events);  in uprobe_perf_open()
 1326 	head = this_cpu_ptr(call->perf_events);  in __uprobe_perf_func()
 
 | 
| D | trace_syscalls.c | 604 	head = this_cpu_ptr(sys_data->enter_event->perf_events);  in perf_syscall_enter()703 	head = this_cpu_ptr(sys_data->exit_event->perf_events);  in perf_syscall_exit()
 
 | 
| D | trace_kprobe.c | 1376 	head = this_cpu_ptr(call->perf_events);  in kprobe_perf_func()1412 	head = this_cpu_ptr(call->perf_events);  in kretprobe_perf_func()
 
 | 
| /Linux-v5.4/Documentation/powerpc/ | 
| D | pmu-ebb.rst | 14 using the Linux perf_events API.32 It is a feature of the perf_events API that events can be created on other
 53 existing "pinned" and "exclusive" attributes of perf_events. This means EBB
 68 perf_events subsystem.
 91 perf_events API. This can be achieved either via the ioctl() interface, or the
 94 However, due to the design of the perf_events API, enabling an event does not
 
 | 
| /Linux-v5.4/tools/perf/Documentation/ | 
| D | perf.data-file-format.txt | 374 that have perf_events records in compressed form.387 This section is the bulk of the file. It consist of a stream of perf_events
 585 This is the canonical description of the kernel generated perf_events
 588 perf_events manpage
 591 http://web.eece.maine.edu/~vweaver/projects/perf_events/programming.html
 595 perf_events"
 
 | 
| /Linux-v5.4/include/trace/ | 
| D | perf.h | 48 	head = this_cpu_ptr(event_call->perf_events);			\
 | 
| /Linux-v5.4/include/linux/ | 
| D | trace_events.h | 280 	struct hlist_head __percpu	*perf_events;  member
 |