Home
last modified time | relevance | path

Searched refs:hypercalls (Results 1 – 11 of 11) sorted by relevance

/linux-4.4.14/arch/x86/entry/syscalls/
DMakefile53 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh
54 $(call if_changed,hypercalls)
56 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h
62 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
/linux-4.4.14/Documentation/virtual/kvm/
D00-INDEX9 hypercalls.txt
10 - KVM hypercalls.
Dppc-pv.txt26 hypercalls as described below.
28 KVM hypercalls
194 1) KVM hypercalls (ePAPR)
197 generic hypercalls are implemented here, like the ePAPR idle hcall. These are
200 2) PAPR hypercalls
202 PAPR hypercalls are needed to run server PowerPC PAPR guests (-M pseries in QEMU).
203 These are the same hypercalls that pHyp, the POWER hypervisor implements. Some of
207 3) OSI hypercalls
210 before KVM). This is supported to maintain compatibility. All these hypercalls get
Ds390-diag.txt4 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for
5 native hypercalls and for selected hypercalls found on other s390
Dhypercalls.txt27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'
58 used to enumerate which hypercalls are available. On PPC, either device tree
Dapi.txt3234 hypercalls and exit with this exit struct that contains all the guest gprs.
3254 The possible hypercalls are defined in the Power Architecture Platform
3396 This capability enables interception of OSI hypercalls that otherwise would
3397 be treated as normal system calls to be injected into the guest. OSI hypercalls
3411 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
3579 This capability controls whether individual sPAPR hypercalls (hcalls)
/linux-4.4.14/drivers/lguest/
DMakefile3 lg-y = core.o hypercalls.o page_tables.o interrupts_and_traps.o \
/linux-4.4.14/drivers/xen/
DKconfig167 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
/linux-4.4.14/arch/x86/include/asm/
Dkvm_host.h736 u32 hypercalls; member
/linux-4.4.14/Documentation/vm/
Dfrontswap.txt224 and use "batched" hypercalls.
/linux-4.4.14/arch/x86/kvm/
Dx86.c162 { "hypercalls", VCPU_STAT(hypercalls) },
5929 ++vcpu->stat.hypercalls; in kvm_emulate_hypercall()