Searched refs:hypercalls (Results 1 - 8 of 8) sorted by relevance

/linux-master/arch/x86/xen/
H A Dtrace.c8 #include <asm/xen-hypercalls.h>
H A Dxen-head.S40 #include <asm/xen-hypercalls.h>
/linux-master/arch/x86/entry/syscalls/
H A DMakefile60 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh FORCE
61 $(call if_changed,hypercalls)
63 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h
70 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
/linux-master/arch/arm64/kvm/
H A DMakefile13 kvm-y += arm.o mmu.o mmio.o psci.o hypercalls.o pvtime.o \
/linux-master/tools/testing/selftests/kvm/
H A DMakefile152 TEST_GEN_PROGS_aarch64 += aarch64/hypercalls
/linux-master/arch/x86/include/asm/
H A Dkvm_host.h690 /* Preallocated buffer for handling hypercalls passing sparse vCPU set */
1567 u64 hypercalls; member in struct:kvm_vcpu_stat
/linux-master/arch/x86/kvm/
H A Dhyperv.c48 * As per Hyper-V TLFS, extended hypercalls start from 0x8001
49 * (HvExtCallQueryCapabilities). Response of this hypercalls is a 64 bit value
1405 * If Xen and Hyper-V hypercalls are both enabled, disambiguate
1872 * either offset in bytes from 'ingpa' for regular hypercalls or the
1873 * number of already consumed 'XMM halves' for 'fast' hypercalls.
2065 * Work around possible WS2012 bug: it sends hypercalls
2389 ++vcpu->stat.hypercalls;
H A Dx86.c295 STATS_DESC_COUNTER(VCPU, hypercalls),
10050 ++vcpu->stat.hypercalls;
10154 ++vcpu->stat.hypercalls;

Completed in 263 milliseconds