Home
last modified time | relevance | path

Searched refs:kcore (Results 1 – 18 of 18) sorted by relevance

/openbmc/linux/tools/perf/util/
H A Dsymbol-elf.c1914 struct kcore { struct
1921 static int kcore__open(struct kcore *kcore, const char *filename) in kcore__open() argument
1925 kcore->fd = open(filename, O_RDONLY); in kcore__open()
1926 if (kcore->fd == -1) in kcore__open()
1929 kcore->elf = elf_begin(kcore->fd, ELF_C_READ, NULL); in kcore__open()
1930 if (!kcore->elf) in kcore__open()
1933 kcore->elfclass = gelf_getclass(kcore->elf); in kcore__open()
1934 if (kcore->elfclass == ELFCLASSNONE) in kcore__open()
1937 ehdr = gelf_getehdr(kcore->elf, &kcore->ehdr); in kcore__open()
1944 elf_end(kcore->elf); in kcore__open()
[all …]
H A Drecord.h52 bool kcore; member
/openbmc/linux/tools/perf/Documentation/
H A Dperf.data-directory-format.txt31 the --kcore option which puts a copy of /proc/kcore into the directory.
34 $ sudo perf record --kcore uname
43 ├── [-r-------- 40230912] kcore
53 Using perf.data/kcore_dir/kcore for kernel data
H A Dperf-buildid-cache.txt31 --kcore::
32 Add specified kcore file to the cache. For the current host that is
33 /proc/kcore which requires root permissions to read. Be aware that
39 permissions for root only. kcore will not be added if there is already a
40 kcore in the cache (with the same build-id) that has the same modules at
41 the same addresses. Use the -v option to see if a copy of kcore is
H A Dperf-intel-pt.txt70 code. A fairly good kernel image is available in /proc/kcore but to get an
71 accurate image a copy of /proc/kcore needs to be made under the same conditions
72 as the data capture. 'perf record' can make a copy of /proc/kcore if the option
73 --kcore is used, but access to /proc/kcore is restricted e.g.
75 sudo perf record -o pt_ls --kcore -e intel_pt// -- ls
78 simply 'data') and copies of /proc/kcore, /proc/kallsyms and /proc/modules into
1275 …hfs needs -o direct_io to enable reading of proc files. root access is needed to read /proc/kcore.
1280 Copy the guest /proc/kallsyms, /proc/modules and /proc/kcore
1282 $ perf buildid-cache -v --kcore vm0/proc/kcore
1283 …kcore added to build-id cache directory /home/user/.debug/[kernel.kcore]/9600f316a53a0f54278885e8d…
[all …]
H A Dperf-record.txt693 --kcore::
694 Make a copy of /proc/kcore and place it into a directory with the perf data file.
H A Dperf-config.txt233 and /proc/kcore files to be used at analysis time.
/openbmc/linux/fs/proc/
H A DMakefile32 proc-$(CONFIG_PROC_KCORE) += kcore.o
H A DKconfig33 bool "/proc/kcore support" if !ARM
/openbmc/linux/Documentation/translations/zh_TW/admin-guide/
H A DREADME.rst345 使用新內核重新啓動後，執行 ``gdb vmlinux /proc/kcore`` 。現在可以使用所有
/openbmc/linux/tools/perf/
H A Dbuiltin-record.c942 char kcore[PATH_MAX]; in record__kcore_readable() local
945 scnprintf(kcore, sizeof(kcore), "%s/proc/kcore", machine->root_dir); in record__kcore_readable()
947 fd = open(kcore, O_RDONLY); in record__kcore_readable()
2392 if (rec->opts.kcore && in __cmd_record()
2441 if (rec->opts.kcore) { in __cmd_record()
3409 OPT_BOOLEAN(0, "kcore", &record.opts.kcore, "copy /proc/kcore"),
3997 if (rec->opts.kcore) in cmd_record()
4000 if (rec->opts.kcore || record__threads_enabled(rec)) in cmd_record()
/openbmc/linux/Documentation/bpf/
H A Ddrgn.rst9 Instead it's reading directly from ``/proc/kcore`` or vmcore and pretty prints
/openbmc/linux/Documentation/admin-guide/
H A Ddevices.rst94 /dev/core /proc/kcore symbolic Backward compatibility
H A Ddevices.txt7 2 = /dev/kmem OBSOLETE - replaced by /proc/kcore
11 6 = /dev/core OBSOLETE - replaced by /proc/kcore
/openbmc/openbmc/meta-security/recipes-ids/tripwire/files/
H A Dtwpol-yocto.txt1054 /proc/kcore -> $(Device) ;
/openbmc/linux/Documentation/filesystems/
H A Dproc.rst709 kcore Kernel core image (can be ELF or A.OUT(deprecated in 2.4))
/openbmc/linux/
H A Dopengrok1.0.log[all...]
H A Dopengrok2.0.log[all...]