| /xen/docs/misc/ |
| A D | hvm-emulated-unplug.pandoc | 1 #Xen HVM emulated device unplug protocol
3 The protocol covers three basic things:
13 The current protocol works like this (from the point of view of
25 the moment, the only drivers using this protocol are our
71 NOTE: The IO ports implementing the unplug protocol are implemented
73 present in the system then this protocol will not work.
76 Unplug protocol for old SUSE PVonHVM
84 SLES11SP4/SLE12 the official protocol was used.
86 Unplug protocol for old Novell VMDP
88 During Xen-3.0 timeframe an unofficial unplug protocol was used in
[all …]
|
| A D | pv-drivers-lifecycle.pandoc | 11 The first step toward acceptance of a new PV protocol is to write a
13 handshake mechanism, the ABI, how the protocol works and anything else
23 After the high level design of the protocol has been discussed and
30 protocol to the relevant open source mailing lists, such as LKML,
44 The protocol version is likely bumped. More testing leads to confidence
|
| A D | stubdom.txt | 26 Toolstack to MiniOS ioemu stubdomain protocol
29 This section describe communication protocol between toolstack and
30 qemu-traditional running in MiniOS stubdomain. The protocol include
39 (its backend is responsible for exposing them using appropriate protocol
78 Toolstack to Linux ioemu stubdomain protocol
81 This section describe communication protocol between toolstack and
82 qemu-upstream running in Linux stubdomain. The protocol include
91 (its backend is responsible for exposing them using appropriate protocol
|
| A D | 9pfs.pandoc | 5 9pfs is a network filesystem protocol developed for Plan 9. 9pfs is very
13 ### 9pfs protocol
51 The transport protocol supports multiple rings up to the maximum
66 [XenbusStateInitialising]. The protocol node name is **9pfs**.
78 List of comma separated protocol versions supported by the backend.
81 protocol, not the version of 9pfs supported by the server.
114 Only "none" is supported in this version of the protocol.
295 well-known. In this protocol:
306 ring is full. This version of the protocol doesn't take advantage of it,
311 out, without any additional fields in the protocol, by comparing the
[all …]
|
| A D | pvcalls.pandoc | 56 PV Calls is a paravirtualized protocol that allows the implementation of
63 the protocol is meant to be easily extended to cover different sets of
101 state of [XenbusStateInitialising]. The protocol node name
130 List of comma separated protocol versions supported by the backend.
248 uint32_t protocol;
317 **version** of the protocol.
385 protocol. **id** is freely chosen by the frontend and references this
388 the protocol.
397 - **protocol**: the particular protocol to be used with the socket, usually 0
738 #### Expanding the protocol
[all …]
|
| A D | xenstore-paths.pandoc | 6 The XenStore wire protocol itself is described in
161 This protocol is not currently well documented.
202 Note that the use of this event channel suspend protocol is optional
205 use the xenstore-based protocol instead (see ~/control/shutdown,
207 protocol.
428 This protocol is Linux only.
437 The precise protocol is not yet documented.
484 protocol definition.
|
| A D | xenstore-ring.txt | 4 information. The [xenstore protocol](xenstore.txt) is layered on top of
104 [xenstore protocol](xenstore.txt) packets it may have;
|
| A D | efi.pandoc | 34 the multiboot2 protocol. When booting using GRUB or another multiboot aware
36 the loader to Xen using the multiboot protocol.
|
| A D | x86-xenpv-bootloader.pandoc | 16 bootloader to load and the protocol/format expected from the
|
| /xen/docs/misc/arm/ |
| A D | booting.txt | 4 Xen follows the zImage protocol defined for 32-bit ARM Linux[1] and the
5 Image protocol defined for ARM64 Linux[2].
19 NOTE: although Xen uses the zImage protocol there is no compression
21 zImage protocol should still be used and not the stricter "raw
22 (non-zImage)" protocol described in arm/Booting.
|
| /xen/docs/ |
| A D | README.remus | 16 This code is based on DRBD 8.3.11 and uses a new replication protocol (named
17 protocol D) for asynchronous disk checkpoint replication. A protected VM's DRBD
18 disks on the primary and backup hosts need to be configured to use protocol D
19 as the replication protocol. An example resource configuration file can be found
|
| A D | INDEX | 9 misc/hvm-emulated-unplug Xen HVM emulated device unplug protocol
15 misc/xenstore Xenstore protocol specification
|
| /xen/tools/hotplug/Linux/ |
| A D | colo-proxy-setup | 41 do_without_error tc filter add dev $vifname parent 1: protocol ip prio 10 \
43 do_without_error tc filter add dev $vifname parent 1: protocol arp prio 11 \
45 do_without_error tc filter add dev $vifname parent 1: protocol ipv6 prio \
61 do_without_error tc filter del dev $vifname parent 1: protocol ip prio 10 u32 match u32 \
63 do_without_error tc filter del dev $vifname parent 1: protocol arp prio 11 u32 match u32 \
65 do_without_error tc filter del dev $vifname parent 1: protocol ipv6 prio 12 u32 match u32 \
|
| /xen/docs/hypervisor-guide/x86/ |
| A D | how-xen-boots.rst | 21 protocol.
55 which indicates the ability to use the PVH boot protocol, and registers
73 The MB2+EFI entrypoint depends on being entered with the MB2 protocol, and
74 will terminate if the entry protocol is wrong, or if EFI details aren't
88 build. However, entry via anything other than the EFI64 protocol is
|
| /xen/docs/designs/ |
| A D | non-cooperative-migration.md | 32 protocol itself being an exception to this for obvious chicken-and-egg
35 Typical protocol establishment is based on use of two separate xenstore
69 to protocol establishment. Upon PV device creation the toolstack will set
73 protocol specific information into the xenstore backend area (to be read
76 following illustration is true of the netif protocol.
88 Because the domid of both ends of a PV protocol forms a key part of
89 negotiating the data plane for that protocol (because it is encoded into
94 in re-negotiating the protocol using the new domid after migration.
145 and some event channel state (particularly if using the *2l* protocol).
214 example, the shared rings of a PV protocol are *granted* by a frontend
[all …]
|
| A D | argo.pandoc | 19 according to the agreed transfer protocol. This structure ensures that
27 - Provide a protocol implementation adhering to hardware synchronization
33 - Transmit only the intended data, adhering to the access protocol of the data
60 that pertains to more than one domain, a locking protocol defines which locks
146 The protocol to safely acquire write access to the per-ring data structure,
192 structs of all domains simplifies the protocol.
431 removing state from the data structures of multiple domains, a locking protocol
|
| /xen/config/ |
| A D | Tools.mk.in | 40 # Download GIT repositories via HTTP or GIT's own protocol?
41 # GIT's protocol is faster and more robust, when it works at all (firewalls
|
| /xen/ |
| A D | SUPPORT.md | 428 Note that the "keyboard protocol" includes mouse / pointer /
437 ### PV SCSI protocol (frontend)
452 Guest-side driver capable of speaking the Xen 9pfs protocol
476 Host-side implementations of the Xen PV block protocol.
492 Host-side implementations of Xen PV network protocol
500 Host-side implementation of the Xen PV framebuffer protocol
506 Host-side implementation of the Xen PV console protocol
512 Host-side implementation of the Xen PV keyboard protocol.
519 Host-side implementation of the Xen PV USB protocol
523 ### PV SCSI protocol (backend)
[all …]
|
| A D | CHANGELOG.md | 23 - Support in kdd for initial KD protocol handshake for Win 7, 8 and 10 (64 bit).
|
| /xen/automation/build/archlinux/ |
| A D | current.dockerfile | 41 spice-protocol \
|
| /xen/xen/include/public/io/ |
| A D | pvcalls.h | 70 uint32_t protocol; member
|
| /xen/stubdom/ |
| A D | vtpm-parent-sign-ek.patch | 67 + * @auth1: [in, out] Authorization protocol parameters
182 + * be used on subsequent boots to certify AIKs via the usual Privacy CA protocol.
|
| A D | vtpm-deepquote-anyloc.patch | 52 * @auth1: [in, out] Authorization protocol parameters
|
| /xen/docs/man/ |
| A D | xen-pci-device-reservations.7.pod | 84 and unplug protocol.
|
| /xen/tools/libxc/ |
| A D | xc_dom_x86.c | 118 const char *protocol; in xc_domain_get_native_protocol() local
127 protocol = XEN_IO_PROTO_ABI_X86_32; in xc_domain_get_native_protocol()
130 protocol = XEN_IO_PROTO_ABI_X86_64; in xc_domain_get_native_protocol()
133 protocol = NULL; in xc_domain_get_native_protocol()
136 return protocol; in xc_domain_get_native_protocol()
|