Home
last modified time | relevance | path

Searched refs:perf (Results 1 – 25 of 70) sorted by relevance

123

/openbmc/openbmc/poky/meta/recipes-kernel/perf/
H A Dperf.bb8 HOMEPAGE = "https://perf.wiki.kernel.org/index.php/Main_Page"
50 PROVIDES = "virtual/perf"
54 # needed for building the tools/perf Python bindings
64 # needed for building the tools/perf Perl binding
65 include ${@bb.utils.contains('PACKAGECONFIG', 'perl', 'perf-perl.inc', '', d)}
77 # overriding the flags included here. But for some, perf does not add
79 # for those. Also include ${DEBUG_PREFIX_MAP} which ensures perf is
97 -C ${S}/tools/perf \
123 'perfexecdir=${libexecdir}/perf-core' \
134 # perf's build system by default ignores any -j argument, but does
[all …]
/openbmc/qemu/block/
H A Dbackup.c46 BackupPerf perf; member
158 job->perf.max_workers, job->perf.max_chunk, in backup_loop()
361 BackupPerf *perf, in backup_job_create() argument
416 if (perf->max_workers < 1 || perf->max_workers > INT_MAX) { in backup_job_create()
421 if (perf->max_chunk < 0) { in backup_job_create()
462 perf->min_cluster_size, &bcs, on_cbw_error, errp); in backup_job_create()
469 if (perf->max_chunk && perf->max_chunk < cluster_size) { in backup_job_create()
471 "cluster size (%" PRIi64 ")", perf->max_chunk, cluster_size); in backup_job_create()
494 job->perf = *perf; in backup_job_create()
496 block_copy_set_copy_opts(bcs, perf->use_copy_range, compress); in backup_job_create()
/openbmc/openbmc/poky/documentation/profile-manual/
H A Dexamples.rst20 tools, in this case 'perf stat', 'perf script', 'perf record' and 'perf
H A Dusage.rst13 perf chapter
16 The perf tool is the profiling and tracing tool that comes bundled
27 In many ways, perf aims to be a superset of all the tracing and
29 covered in this How-to. The past couple of years have seen perf subsume a
33 now implemented by the perf subsystem. Extrapolation suggests that at
36 many cases show how the same things can be accomplished in perf and the
42 `perf(1) <https://linux.die.net/man/1/perf>`__.
44 perf Setup
50 In particular, you'll get the most mileage out of perf if you profile an
55 perf runs on the target system for the most part. You can archive
[all …]
/openbmc/openbmc/poky/meta/recipes-devtools/valgrind/valgrind/
H A Dfixed-perl-path.patch22 perf/vg_perf.in | 2 +-
36 diff --git a/perf/vg_perf.in b/perf/vg_perf.in
38 --- a/perf/vg_perf.in
39 +++ b/perf/vg_perf.in
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-test/fbtest/
H A Dfb-test_1.1.0.bb17 # avoid collisions with perf (perf) and mesa-demos (offset)
18 for prog in perf rect offset ; do
/openbmc/openbmc/poky/scripts/contrib/
H A Dbuild-perf-test-wrapper.sh15 archive_dir=~/perf-results/archives
34 (default: GIT_TOP_DIR/build-perf-test)
181 oe-build-perf-test --out-dir "$results_dir" \
211 oe-build-perf-report -r "$results_repo" > $report_txt
212 oe-build-perf-report -r "$results_repo" --html > $report_html
218 …"$script_dir"/oe-build-perf-report-email.py --to "$email_to" --subject "Build Perf Test Report for…
/openbmc/qemu/tests/qemu-iotests/
H A D257.out33 …", "job-id": "ref_backup_0", "sync": "full", "target": "ref_target_0", "x-perf": {"max-workers": 1…
80 …", "job-id": "ref_backup_1", "sync": "full", "target": "ref_target_1", "x-perf": {"max-workers": 1…
94 …, "job-id": "backup_1", "sync": "bitmap", "target": "backup_target_1", "x-perf": {"max-workers": 1…
218 …", "job-id": "ref_backup_2", "sync": "full", "target": "ref_target_2", "x-perf": {"max-workers": 1…
232 …, "job-id": "backup_2", "sync": "bitmap", "target": "backup_target_2", "x-perf": {"max-workers": 1…
302 …", "job-id": "ref_backup_0", "sync": "full", "target": "ref_target_0", "x-perf": {"max-workers": 1…
349 …", "job-id": "ref_backup_1", "sync": "full", "target": "ref_target_1", "x-perf": {"max-workers": 1…
365 …, "job-id": "backup_1", "sync": "bitmap", "target": "backup_target_1", "x-perf": {"max-workers": 1…
425 …", "job-id": "ref_backup_2", "sync": "full", "target": "ref_target_2", "x-perf": {"max-workers": 1…
439 …, "job-id": "backup_2", "sync": "bitmap", "target": "backup_target_2", "x-perf": {"max-workers": 1…
[all …]
/openbmc/openbmc/poky/meta/recipes-graphics/cairo/
H A Dcairo_1.18.4.bb19 LICENSE:${PN}-perf-utils = "GPL-3.0-or-later"
52 MULTILIB_SCRIPTS = "${PN}-perf-utils:${bindir}/cairo-trace"
69 PACKAGES =+ "cairo-gobject cairo-script-interpreter cairo-perf-utils"
79 DESCRIPTION:cairo-perf-utils = "The Cairo library performance utilities"
84 FILES:${PN}-perf-utils = "${bindir}/cairo-* ${libdir}/cairo/libcairo-trace.so ${libdir}/cairo/libca…
/openbmc/openbmc-tools/witherspoon-debug/
H A DREADME.md27 3. Make `perf(1)` work by
30 3. Disabling `perf(1)`'s buildid tracking (fills the RW filesystem)
H A Ddebug73 LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/perf config --user buildid.dir=/dev/null
/openbmc/openbmc/poky/meta/recipes-core/packagegroups/
H A Dpackagegroup-core-tools-profile.bb24 PERF = "perf"
26 PERF:libc-musl:arm = "perf"
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/open-vm-tools/open-vm-tools/
H A Dtools.conf2 disable-perf-mon=1
/openbmc/qemu/docs/devel/
H A Dtcg.rst196 The Linux ``perf`` tool will treat all JITted code as a single block as
202 available); its output needs to be integrated with the ``perf.data`` file
207 perf record $QEMU -perfmap $REMAINING_ARGS
208 perf report
210 perf record -k 1 $QEMU -jitdump $REMAINING_ARGS
211 DEBUGINFOD_URLS= perf inject -j -i perf.data -o perf.data.jitted
212 perf report -i perf.data.jitted
/openbmc/openbmc/poky/documentation/styles/config/vocabularies/OpenSource/
H A Daccept.txt10 perf
/openbmc/openbmc/meta-phosphor/classes/
H A Dobmc-phosphor-debug-tarball.bbclass10 IMAGE_INSTALL:append = " busybox packagegroup-obmc-phosphor-debugtools perf "
/openbmc/qemu/tcg/
H A Dmeson.build27 tcg_ss.add(files('perf.c'))
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/oprofile/oprofile/
H A D0001-configure-Include-unistd.h-for-getpid-API.patch6 This fixes the check for perf events support in configure
/openbmc/openbmc/poky/meta/recipes-kernel/systemtap/systemtap/
H A D0001-improve-reproducibility-for-c-compiling.patch28 #define INTERNED_STRING_FIND_MEMMEM 1 /* perf stat indicates a very slight benefit */
/openbmc/u-boot/arch/arm/dts/
H A Dstm32mp15-ddr.dtsi89 st,ctl-perf = <
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/rocksdb/files/
H A D0006-Implement-timer-for-arm-v6.patch25 + // Read the user mode perf monitor counter access permissions.
/openbmc/openbmc/poky/documentation/test-manual/
H A Dintro.rst107 commonly used usage scenarios are run through ``oe-build-perf-test``.
285 - *oe-build-perf-test:*
294 $ oe-build-perf-test <options>
298 Scripts include the ``build-perf-test-wrapper`` script with
299 examples of how to use the oe-build-perf-test from the command
305 Use the ``oe-build-perf-report`` command to generate text reports
307 …:yocto_dl:`html </releases/yocto/yocto-4.3/testresults/buildperf-debian11/perf-debian11_nanbield_2…
309 …:yocto_dl:`txt </releases/yocto/yocto-4.3/testresults/buildperf-debian11/perf-debian11_nanbield_20…
479 ``oe-build-perf-test``
/openbmc/openbmc/poky/meta/conf/distro/include/
H A Dlto.inc21 LTO:pn-perf = ""
/openbmc/u-boot/doc/device-tree-bindings/memory-controllers/
H A Dst,stm32mp1-ddr.txt82 - st,ctl-perf : controleur values depending of performance and scheduling
234 st,ctl-perf = <
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/nana/
H A Dnana_git.bb30 ${S}/man/Makefile ${S}/perf/Makefile \

123