Searched refs:guest (Results 1 – 9 of 9) sorted by relevance
/tools/perf/Documentation/ |
D | perf-kvm.txt | 6 perf-kvm - Tool to trace/measure kvm guest os 11 'perf kvm' [--host] [--guest] [--guestmount=<path> 14 'perf kvm' [--host] [--guest] [--guestkallsyms=<path> --guestmodules=<path> 23 a performance counter profile of guest os in realtime 28 default behavior of perf kvm as --guest, so if neither --host nor --guest 29 is input, the perf data file name is perf.data.guest. If --host is input, 31 perf.data.host, please input --host --no-guest. The behaviors are shown as 33 Default('') -> perf.data.guest 35 --guest -> perf.data.guest 36 --host --guest -> perf.data.kvm [all …]
|
D | perf-list.txt | 29 G - guest counting (in KVM guests) 69 registers: event, umask, edge, inv, cmask. Esp. guest/host only and
|
D | perf-report.txt | 86 on guest machine 88 guest machine
|
/tools/virtio/virtio-trace/ |
D | README | 4 Trace agent is a user tool for sending trace data of a guest to a Host in low 48 For example, if a guest use three CPUs, the names are 83 example, if a guest use three CPUs, chardev names should be trace-path-cpu0, 86 3) Boot the guest 87 You can find some chardev in /dev/virtio-ports/ in the guest. 93 0) Build trace agent in a guest 96 1) Enable ftrace in the guest 100 2) Run trace agent in the guest 104 option, trace data are output via stdout in the guest. 109 the guest will stop by specification of chardev in QEMU. This blocking mode may [all …]
|
/tools/lguest/ |
D | lguest.txt | 27 - The easiest way to run lguest is to use same kernel as guest and host. 33 "Paravirtualized guest support" = Y 34 "Lguest guest support" = Y 86 inside the guest. 94 eth0 inside the guest at 192.168.19.2. 97 using --tunnet=bridge:<bridgename>, and perhaps run dhcp on the guest 109 Then use --tunnet=bridge:lg0 when launching the guest. 118 /dev/hwrng in the guest that will read from the host's /dev/random. 120 to provide entropy to the guest kernel's /dev/random.
|
/tools/ |
D | Makefile | 48 cgroup firewire hv guest usb virtio vm net: FORCE target
|
/tools/testing/ktest/examples/ |
D | README | 19 kvm.conf - A example of a config that is used to test a virtual guest running
|
/tools/testing/selftests/rcutorture/doc/ |
D | rcu-test-image.txt | 2 that contains the filesystem used by the guest-OS kernel. There are
|
/tools/perf/util/ |
D | evsel.c | 301 MOD_PRINT(guest, 'G'); in perf_evsel__add_modifiers()
|