utput=<path>
               Output file name, for the _record_ subcommand. Doesnât work
               with _report_ , just redirect the output to a file when using
               _report_.
    
           --host
               Collect host side performance profile.
    
           --guest
               Collect guest side performance profile.
    
           --guestmount=<path>
               Guest OS root file system mount directory. Users mount guest
               OS root directories under <path> by a specific filesystem
               access method, typically, sshfs. For example, start 2 guest
               OS, oneâs pid is 8888 and the otherâs is 9999:
    
                   $ mkdir ~/guestmount
                   $ cd ~/guestmount
                   $ sshfs -o allow_other,direct_io -p 5551 localhost:/ 8888/
                   $ sshfs -o allow_other,direct_io -p 5552 localhost:/ 9999/
                   $ perf kvm --host --guest --guestmount=~/guestmount top
    
           --guestkallsyms=<path>
               Guest OS /proc/kallsyms file copy. perf reads it to get guest
               kernel symbols. Users copy it out from guest OS.
    
           --guestmodules=<path>
               Guest OS /proc/modules file copy. perf reads it to get guest
               kernel module information. Users copy it out from guest OS.
    
           --guestvmlinux=<path>
               Guest OS kernel vmlinux.
    
           --guest-code
               Indicate that guest code can be found in the hypervisor
               process, which is a common case for KVM test programs.
    
           --stdio
               Use the stdio interface.
    
           -v, --verbose
               Be more verbose (show counter open errors, etc).
    

##  STAT REPORT OPTIONS  top

    
    
           --vcpu=<value>
               analyze events which occur on this vcpu. (default: all vcpus)
    
           --event=<value>
               event to be analyzed. Possible values: vmexit, mmio (x86
               only), ioport (x86 only). (default: vmexit)
    
           -k, --key=<value>
               Sorting key. Possible values: sample (default, sort by
               samples number), percent_sample (sort by sample percentage),
               time (sort by average time), precent_time (sort by time
               percentage), max_t (sort by maximum time), min_t (sort by
               minimum time), mean_t (sort by mean time).
    
           -p, --pid=
               Analyze events only for given process ID(s) (comma separated
               list).
    

##  STAT LIVE OPTIONS  top

    
    
           -d, --display
               Time in seconds between display updates
    
           -m, --mmap-pages=
               Number of mmap data pages (must be a power of two) or size
               specification with appended unit character - B/K/M/G. The
               size is rounded up to have nearest pages power of two value.
    
           -a, --all-cpus
               System-wide collection from all CPUs.
    
           -p, --pid=
               Analyze events only for given process ID(s) (comma separated
               list).
    
           --vcpu=<value>
               analyze events which occur on this vcpu. (default: all vcpus)
    
           --event=<value>
               event to be analyzed. Possible values: vmexit, mmio (x86
               only), ioport (x86 only). (default: vmexit)
    
           -k, --key=<value>
               Sorting key. Possible values: sample (default, sort by
               samples number), time (sort by average time).
    
           --duration=<value>
               Show events other than HLT (x86 only) or Wait state (s390
               only) that take longer than duration usecs.
    
           --proc-map-timeout
               When processing pre-existing threads /proc/XXX/mmap, it may
               take a long time, because the file may be huge. A time out is
               needed in such cases. Th