Home
last modified time | relevance | path

Searched refs:KVM (Results 1 – 8 of 8) sorted by relevance

/tools/testing/selftests/rcutorture/bin/
Dkvm.sh25 KVM="`pwd`/tools/testing/selftests/rcutorture"; export KVM
26 PATH=${KVM}/bin:$PATH; export PATH
30 TORTURE_INITRD="$KVM/initrd"; export TORTURE_INITRD
199 CONFIGFRAG=${KVM}/configs/${TORTURE_SUITE}; export CONFIGFRAG
208 resdir=$KVM/res
293 KVM="$KVM"; export KVM
330 -v KVM="$KVM" \
Dkvm-test-1-run.sh99 echo No identifiable boot image, not running KVM, see $resdir.
106 echo Build failed, not running KVM, see $resdir.
125 cd $KVM
/tools/kvm/kvm_stat/
Dkvm_stat.txt6 kvm_stat - Report KVM kernel module event counters
15 kvm_stat prints counts of KVM kernel module trace events. These events signify
25 The set of KVM kernel module trace events may be specific to the kernel version
26 or architecture. It is best to check the KVM kernel module source code for the
/tools/testing/vsock/
DREADME3 These tests exercise net/vmw_vsock/ host<->guest sockets for VMware, KVM, and
/tools/testing/selftests/rcutorture/doc/
Drcu-test-image.txt35 https://help.ubuntu.com/community/KVM/CreateGuests
DTREE_RCU-kconfig.txt67 Always used in KVM testing.
/tools/perf/Documentation/
Dperf-list.txt51 G - guest counting (in KVM guests)
52 H - host counting (not in KVM guests)
Dperf-kvm.txt54 of KVM events. Currently, vmexit, mmio (x86 only) and ioport (x86 only)