Searched refs:interdomain (Results 1 – 12 of 12) sorted by relevance
42 status.u.interdomain.dom, status.u.interdomain.port); in main()
387 lchn->u.interdomain.remote_dom = rd; in evtchn_bind_interdomain()388 lchn->u.interdomain.remote_port = rport; in evtchn_bind_interdomain()392 rchn->u.interdomain.remote_dom = ld; in evtchn_bind_interdomain()393 rchn->u.interdomain.remote_port = lport; in evtchn_bind_interdomain()669 d2 = chn1->u.interdomain.remote_dom; in evtchn_close()699 port2 = chn1->u.interdomain.remote_port; in evtchn_close()765 rd = lchn->u.interdomain.remote_dom; in evtchn_send()766 rport = lchn->u.interdomain.remote_port; in evtchn_send()979 status->u.interdomain.dom = in evtchn_status()981 status->u.interdomain.port = chn->u.interdomain.remote_port; in evtchn_status()[all …]
275 bool "Argo: hypervisor-mediated interdomain communication" if EXPERT
5 # Allow all domains to enable the Argo interdomain communication hypercall;
229 } interdomain; /* EVTCHNSTAT_interdomain */ member
295 # when creating an interdomain event channel endpoint:300 # interdomain event channel is established.308 # when creating an interdomain event channel endpoint:530 # Class argo is used to describe the Argo interdomain communication system.
567 peer = chn->u.interdomain.remote_dom; in flask_get_peer_sid()
108 } interdomain; /* state == ECS_INTERDOMAIN */ member
218 | `evtchn` | The port number of the interdomain channel used |
5 Argo is an interdomain communication mechanism. It provides Xen hypervisor
191 an interdomain bind, and then, when it wishes to ask the guest to
188 Controls for the Argo hypervisor-mediated interdomain communication service.193 Argo is a interdomain communication mechanism, where Xen acts as the central
Completed in 135 milliseconds