| /xen/docs/guest-guide/x86/ |
| A D | hypercall-abi.rst | 42 Different hypercalls take a different number of parameters. Each hypercall
52 The exact sequence of instructions required to issue a hypercall differs
74 Hypercall Page. This allows a guest to make a hypercall without needing to
81 The hypercall page is a page of guest RAM into which Xen will write suitable
84 Creating a hypercall page is an isolated operation from Xen's point of view.
85 It is the guests responsibility to ensure that the hypercall page, once
87 Multiple hypercall pages may be created by the guest, if it wishes.
89 The stubs are arranged by hypercall index, and start on 32-byte boundaries.
90 To invoke a specific hypercall, ``call`` the relevant stub [3]_:
109 Any guest can locate the Xen CPUID leaves and read the *hypercall transfer
[all …]
|
| A D | index.rst | 9 hypercall-abi
|
| /xen/tools/libs/call/ |
| A D | minios.c | 41 int osdep_hypercall(xencall_handle *xcall, privcmd_hypercall_t *hypercall) in osdep_hypercall() argument
46 call.op = hypercall->op; in osdep_hypercall()
48 call.args[i] = hypercall->arg[i]; in osdep_hypercall()
|
| A D | freebsd.c | 65 int osdep_hypercall(xencall_handle *xcall, privcmd_hypercall_t *hypercall) in osdep_hypercall() argument
70 ret = ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); in osdep_hypercall()
72 return (ret == 0) ? hypercall->retval : ret; in osdep_hypercall()
|
| A D | netbsd.c | 96 int do_xen_hypercall(xencall_handle *xcall, privcmd_hypercall_t *hypercall) in do_xen_hypercall() argument
99 int error = ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); in do_xen_hypercall()
110 return hypercall->retval; in do_xen_hypercall()
|
| A D | solaris.c | 83 int do_xen_hypercall(xencall_handle *xcall, privcmd_hypercall_t *hypercall) in do_xen_hypercall() argument
86 return ioctl(fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); in do_xen_hypercall()
|
| A D | linux.c | 83 int osdep_hypercall(xencall_handle *xcall, privcmd_hypercall_t *hypercall) in osdep_hypercall() argument
85 return ioctl(xcall->fd, IOCTL_PRIVCMD_HYPERCALL, hypercall); in osdep_hypercall()
|
| A D | private.h | 56 int osdep_hypercall(xencall_handle *xcall, privcmd_hypercall_t *hypercall);
|
| /xen/xen/xsm/flask/policy/ |
| A D | access_vectors | 45 # kexec hypercall
64 # mca hypercall
70 # hypfs hypercall
159 hypercall
313 # source = domain making the hypercall
350 # source = domain making the hypercall
369 # source = domain making the hypercall
375 # source = domain making the hypercall
406 # source = domain making the hypercall
411 # source = domain making the hypercall
[all …]
|
| /xen/docs/ |
| A D | INDEX | 1 hypercall Hypercall Interfaces
2 hypercall/arm/index ARM
3 hypercall/x86_32/index x86_32
4 hypercall/x86_64/index x86_64
|
| A D | Makefile | 31 $(patsubst %,html/hypercall/%/index.html,$(DOC_ARCHES))
202 $(foreach i,$(filter-out x86_32 x86_64,$(DOC_ARCHES)),html/hypercall/$(i)/index.html): EXTRA_EXCLUD…
204 html/hypercall/%/index.html: $(CURDIR)/xen-headers Makefile
214 -include $(wildcard html/hypercall/*/.deps)
|
| /xen/docs/features/ |
| A D | hypervisorfs.pandoc | 20 while the toolstack is able to use a hypercall to query the entry
47 Access to the hypervisor filesystem is done via the stable new hypercall
48 __HYPERVISOR_filesystem_op. This hypercall supports a sub-command
56 * hypercall interface specification
|
| /xen/docs/designs/ |
| A D | dmop.pandoc | 11 The problem occurs when you a device model issues an hypercall that
18 having to have specific knowledge of the hypercall's semantics.
28 A DMOP hypercall consists of a domid (which is audited to verify that it
52 @domid is the domain the hypercall operates on.
69 1. Check hypercall is DMOP.
|
| /xen/tools/debugger/gdbsx/xg/ |
| A D | xg_main.c | 170 privcmd_hypercall_t hypercall; in _domctl_hcall() local
179 hypercall.op = __HYPERVISOR_domctl; in _domctl_hcall()
180 hypercall.arg[0] = (unsigned long)&domctl; in _domctl_hcall()
182 rc = ioctl(_dom0_fd, IOCTL_PRIVCMD_HYPERCALL, &hypercall); in _domctl_hcall()
198 privcmd_hypercall_t hypercall; in _check_hyp() local
218 hypercall.op = __HYPERVISOR_xen_version; in _check_hyp()
219 hypercall.arg[0] = (unsigned long)XENVER_capabilities; in _check_hyp()
220 hypercall.arg[1] = (unsigned long)&xen_caps; in _check_hyp()
222 rc = ioctl(_dom0_fd, IOCTL_PRIVCMD_HYPERCALL, &hypercall); in _check_hyp()
|
| /xen/xen/arch/x86/pv/ |
| A D | Makefile | 9 obj-y += hypercall.o
|
| /xen/xen/arch/x86/hvm/ |
| A D | Makefile | 13 obj-y += hypercall.o
|
| /xen/docs/misc/ |
| A D | pvh.pandoc | 44 The setup of the hypercall page is also performed in the same way
53 argument passed to the hypercall must be of the type vcpu_hvm_context.
55 this hypercall allows starting the vCPU in several modes (16/32/64bits),
|
| A D | xenstore-paths.pandoc | 644 [BLKIF]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,blkif.h.html
645 [FBIF]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,fbif.h.html
646 [HVMPARAMS]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,hvm,params.h.html
647 [KBDIF]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,kbdif.h.html
649 [NETIF]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,netif.h.html
650 [SCSIIF]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,vscsiif.h.html
651 [SI]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,xen.h.html#Struct_start…
652 [USBIF]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,usbif.h.html
653 [VCPU]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,vcpu.h.html
654 [XSWIRE]: https://xenbits.xen.org/docs/unstable/hypercall/x86_64/include,public,io,xs_wire.h.html
|
| A D | netif-staging-grants.pandoc | 146 11.1) Perform hypercall `EVTCHNOP_send` which might mean a __VMEXIT__
217 27.2) Once done, perform `GNTTABOP_unmap_grant_ref` hypercall. Underlying
218 this hypercall a TLB flush of all backend vCPUS is done.
227 27.4.1) If so, Perform hypercall `EVTCHNOP_send` which might mean a __VMEXIT__
346 12) Perform the `GNTTABOP_copy` hypercall.
385 27.1) If so, Perform hypercall `EVTCHNOP_send` which might mean a __VMEXIT__
|
| /xen/docs/hypervisor-guide/ |
| A D | code-coverage.rst | 40 The ``SYSCTL_coverage_op`` hypercall is used to interact with the coverage
42 wraps this hypercall.
|
| /xen/tools/flask/policy/modules/ |
| A D | guest_features.te | 5 # Allow all domains to enable the Argo interdomain communication hypercall;
|
| /xen/ |
| A D | CHANGELOG.md | 14 the Xen hypercall interface or the viridian one.
|
| /xen/docs/admin-guide/ |
| A D | introduction.rst | 27 Xen also provides a hypercall interface to guests, including event channels
|
| /xen/tools/flask/policy/policy/ |
| A D | mls | 77 …troy setaffinity scheduler setdomainmaxmem setdomainhandle setdebugging hypercall settime set_targ…
|
| /xen/docs/specs/ |
| A D | libxc-migration-stream.pandoc | 463 XEN_DOMCTL_{get,set}tscinfo hypercall sub-ops.
492 XEN_DOMCTL_{get,set}hvmcontext hypercall sub-ops.
512 HVMOP_{get,set}\_param hypercall sub-ops.
641 hypercall sub-ops.
661 hypercall sub-ops.
|