Searched full:synthesizing (Results 1 – 16 of 16) sorted by relevance
134 "synthesizing events on the perf process itself:"); in run_single_threaded()217 "synthesizing events on CPU 0:"); in run_multi_threaded()
26 pr_debug("Not enough memory synthesizing mmap event " in perf_event__synthesize_extra_kmaps()
96 pr_debug2("Synthesizing TSC conversion information\n"); in perf_event__synth_time_conv()
602 pr_debug("Not enough memory synthesizing mmap event " in perf_event__synthesize_modules()1014 pr_debug("Not enough memory synthesizing mmap event " in __perf_event__synthesize_kernel_mmap()1609 pr_debug2("Synthesizing id index\n"); in perf_event__synthesize_id_index()
815 pr_debug("Synthesizing 'branches' event with id %" PRIu64 " sample type %#" PRIx64 "\n", in intel_bts_synth_events()
1903 * When synthesizing FORK events, we are trying to create thread in machine__process_fork_event()1909 * But when synthesizing, this should not be done. If we do, we end up in machine__process_fork_event()
278 * .plt, synthesizing its symbols, that aren't on the symtabs (be it
1198 pr_debug2("Synthesizing auxtrace information\n"); in perf_event__synthesize_auxtrace_info()
2923 pr_debug("Synthesizing '%s' event with id %" PRIu64 " sample type %#" PRIx64 "\n", in intel_pt_synth_event()
53 addresses by synthesizing Enhanced Allocation (EA) capabilities for
166 * can safely run synthesizing function. in mmap_events()
273 The number of threads to run when synthesizing events for existing processes.
620 The number of threads to run when synthesizing events for existing processes.
824 Synthesizing auxtrace information
507 synthesizing instruction and branch events from the instruction trace.
386 * rather than synthesizing an interrupt in software in xive_do_source_eoi()