Searched refs:hypercalls (Results 1 – 14 of 14) sorted by relevance
54 $(out)/xen-hypercalls.h: $(srctree)/scripts/xen-hypercalls.sh55 $(call if_changed,hypercalls)57 $(out)/xen-hypercalls.h: $(srctree)/include/xen/interface/xen*.h63 syshdr-$(CONFIG_XEN) += xen-hypercalls.h
26 hypercalls as described below.28 KVM hypercalls194 1) KVM hypercalls (ePAPR)197 generic hypercalls are implemented here, like the ePAPR idle hcall. These are200 2) PAPR hypercalls202 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 of207 3) OSI hypercalls210 before KVM). This is supported to maintain compatibility. All these hypercalls get
16 hypercalls.txt17 - KVM hypercalls.
4 KVM on s390 supports the DIAGNOSE call for making hypercalls, both for5 native hypercalls and for selected hypercalls found on other s390
27 KVM hypercalls uses 4 byte opcode, that are patched with 'hypercall-instructions'32 KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall63 used to enumerate which hypercalls are available. On PPC, either device tree
3061 This capability means the kernel is capable of handling hypercalls3064 User space should expect that its handlers for these hypercalls3073 The hypercalls mentioned above may or may not be processed successfully3892 hypercalls and exit with this exit struct that contains all the guest gprs.3912 The possible hypercalls are defined in the Power Architecture Platform4082 This capability enables interception of OSI hypercalls that otherwise would4083 be treated as normal system calls to be injected into the guest. OSI hypercalls4097 This capability enables interception of PAPR hypercalls. PAPR hypercalls are4305 This capability controls whether individual sPAPR hypercalls (hcalls)4758 hypercalls:
7 generated-y += xen-hypercalls.h
914 u64 hypercalls; member
59 of UEFI runtime services implemented via hypercalls, see
202 (e.g. cleancache and frontswap) to Xen tmem hypercalls.
239 and use "batched" hypercalls.
1394 ++vcpu->stat.hypercalls; in kvm_hv_hypercall_complete()
188 { "hypercalls", VCPU_STAT(hypercalls) },6881 ++vcpu->stat.hypercalls; in kvm_emulate_hypercall()
258 can make hypercalls directly while the user code must use wrappers
