Lines Matching refs:backend
40 A Xen paravirtualized backend typically runs in Dom0 and it is used to
58 sends POSIX function calls to the backend, which implements them and
67 * full visibility of the guest behavior on the backend domain, allowing
74 * guest services listen on ports bound directly to the backend domain IP
99 The frontend and the backend connect via [xenstore] to
109 Protocol version, chosen among the ones supported by the backend
122 The Xen grant reference granting permission for the backend to map
130 List of comma separated protocol versions supported by the backend.
154 - Query virtual device - Query backend device
156 - Setup OS device instance. - Publish backend features
175 - Query backend device properties.
183 Once frontend and backend are connected, they have a shared page, which
221 to the backend. We shall refer to this ring as **commands ring** to
321 Both fields are echoed back by the backend. See [Socket families and
379 backend, ret is ENOTSUP.
382 After calling `RING_PUSH_RESPONSES_AND_CHECK_NOTIFY`, the backend checks whether
446 **connect** command, the backend:
503 When a release command is issued on a passive socket, the backend
509 - backend releases the socket
510 - backend unmaps the data ring
511 - backend unmaps the indexes page
512 - backend unbinds the event channel
513 - backend replies to frontend with an **ret** value
521 - **reuse**: an optimization hint for the backend. The field is
523 backend know that it will reuse exactly the same set of grant pages
525 the next active sockets. The backend can take advantage of it by
527 backend is free to ignore the hint. Reused data rings are found by
654 The backend will reply to the request only when a new connection is
655 successfully accepted, i.e. the backend does not return EAGAIN or
661 - backend waits for a connection to be available on the socket
663 - backend accepts the new connection
664 - backend creates an internal mapping from **id_new** to the new socket
665 - backend maps the grant reference **ref**, the indexes page, see struct
667 - backend maps all the grant references listed in `struct
670 - backend binds to the **evtchn**
671 - backend replies to the frontend with a **ret** value
712 the queue of the passive socket, the backend generates a response and
749 ABI. Naturally, a feature flag among the backend xenstore nodes should
864 below. The backend maps the grant references contiguously. Of the
918 **max-page-order**, as specified by the backend on XenBus. It has to
927 It contains data read from the socket. The producer is the backend, the
931 the consumer is the backend.
935 array. **in_prod** is increased by the backend, after writing data to **in**.
940 how much data has already been consumed by the backend. **out_prod** is
942 increased by the backend, after reading data from **out**.
985 in -> backend to frontend only
986 out-> frontend to backend only
989 backend is the producer. Everything is the same but mirrored for the
992 The producer, the backend in this case, never reads from the **in**
1050 The producer (the backend for **in**, the frontend for **out**) writes to the
1062 The consumer (the backend for **out**, the frontend for **in**) reads from the
1077 *[in|out]_error* is set by the backend when an error occurs writing or