Home
last modified time | relevance | path

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

/openbmc/qemu/docs/specs/
H A Dppc-spapr-hcalls.rst59 However, doing a hypercall for each access is extremely inefficient
63 This hypercall allows the guest to request a "memory op" to be applied
H A Dppc-spapr-uv-hcalls.rst15 to reserve a hypercall number range specific to this use case to avoid any
/openbmc/qemu/hw/s390x/
H A Dmeson.build33 's390-hypercall.c',
/openbmc/qemu/docs/system/i386/
H A Dhyperv.rst60 hypercall).
119 hypercall may target more than 64 virtual CPUs simultaneously, doing the same
/openbmc/qemu/hw/ppc/
H A Dspapr.c1229 uint8_t hypercall[16]; in spapr_dt_hypervisor() local
1239 if (!kvmppc_get_hypercall(cpu_env(first_cpu), hypercall, in spapr_dt_hypervisor()
1240 sizeof(hypercall))) { in spapr_dt_hypervisor()
1242 hypercall, sizeof(hypercall))); in spapr_dt_hypervisor()
4645 vhc->hypercall = emulate_spapr_hypercall; in spapr_machine_class_init()
/openbmc/qemu/docs/system/ppc/
H A Dpseries.rst108 guest (see the `H_RANDOM hypercall feature
/openbmc/qemu/target/ppc/
H A Dcpu.h1612 void (*hypercall)(PPCVirtualHypervisor *vhyp, PowerPCCPU *cpu); member
/openbmc/qemu/target/s390x/tcg/
H A Dinsn-data.h.inc1338 /* DIAGNOSE (KVM hypercall) */
1370 /* SERVICE CALL LOGICAL PROCESSOR (PV hypercall) */