Searched refs:hypercall (Results 1 – 9 of 9) sorted by relevance
| /linux-2.6.39/drivers/xen/xenfs/ |
| D | privcmd.c | 41 struct privcmd_hypercall hypercall; in privcmd_ioctl_hypercall() local
44 if (copy_from_user(&hypercall, udata, sizeof(hypercall))) in privcmd_ioctl_hypercall()
47 ret = privcmd_call(hypercall.op, in privcmd_ioctl_hypercall()
48 hypercall.arg[0], hypercall.arg[1], in privcmd_ioctl_hypercall()
49 hypercall.arg[2], hypercall.arg[3], in privcmd_ioctl_hypercall()
50 hypercall.arg[4]); in privcmd_ioctl_hypercall()
|
| /linux-2.6.39/Documentation/kvm/ |
| D | ppc-pv.txt | 32 'hypercall-instructions'. This property contains at most 4 opcodes that make
33 up the hypercall. To call a hypercall, just call these instructions.
48 r11 hypercall number 8th output value
51 Hypercall definitions are shared in generic code, so the same hypercall numbers
52 apply for x86 and powerpc alike with the exception that each KVM hypercall
68 map this shared page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE.
70 With this hypercall issued the guest always gets the magic page mapped at the
79 also define a new hypercall feature to indicate that the host can give you more
108 When mapping the magic page using the KVM hypercall KVM_HC_PPC_MAP_MAGIC_PAGE,
|
| D | api.txt | 605 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
606 page, and provides the starting address and size of the hypercall
1083 of 4 instructions that make up a hypercall.
1390 } hypercall;
1392 Unused. This was once used for 'hypercall to userspace'. To implement
1440 MOL uses a special hypercall interface it calls 'OSI'. To enable it, we catch
1443 If exit_reason is KVM_EXIT_OSI, then the vcpu has triggered such a hypercall.
1444 Userspace can now handle the hypercall and when it's done modify the gprs as
|
| /linux-2.6.39/arch/ia64/xen/ |
| D | Makefile | 5 obj-y := hypercall.o xenivt.o xensetup.o xen_pv_ops.o irq_xen.o \
|
| /linux-2.6.39/include/linux/ |
| D | kvm.h | 231 } hypercall; member
|
| /linux-2.6.39/arch/x86/kvm/ |
| D | vmx.c | 3219 vmx_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall) in vmx_patch_hypercall() argument
3224 hypercall[0] = 0x0f; in vmx_patch_hypercall()
3225 hypercall[1] = 0x01; in vmx_patch_hypercall()
3226 hypercall[2] = 0xc1; in vmx_patch_hypercall()
|
| D | svm.c | 3741 svm_patch_hypercall(struct kvm_vcpu *vcpu, unsigned char *hypercall)
3746 hypercall[0] = 0x0f;
3747 hypercall[1] = 0x01;
3748 hypercall[2] = 0xd9;
|
| D | x86.c | 5444 kvm_run->hypercall.ret); in kvm_arch_vcpu_ioctl_run()
|
| /linux-2.6.39/arch/x86/kernel/ |
| D | entry_32.S | 1060 # normal Linux return path in this case because if we use the IRET hypercall
|