Lines Matching defs:host
6 * between the host and the VM. This driver implements the necessary
27 /* The MTU is 16KB per the host side's design */
49 /* We can send up to HVS_MTU_SIZE bytes of payload to the host, but let's use
51 * guest and the host processing as one VMBUS packet is the smallest processing
111 * when we write apps to connect to the host, we can only use VMADDR_CID_ANY
116 * On the host, Hyper-V Sockets are supported by Winsock AF_HYPERV:
129 * VMBus, because here it's obvious the host and the VM can easily identify
130 * each other. Though the VmID is useful on the host, especially in the case
136 * Hyper-V Sockets apps on the host and in Linux VM is:
139 * The only valid Service GUIDs, from the perspectives of both the host and *
144 * When we write apps on the host to connect(), the GUID ServiceID is used.
146 * port and the driver will form the GUID and use that to request the host.
329 /* Remote peer is always the host */
359 * Older versions of hv_sock host side code cannot handle bigger VMBUS
394 * notifications from the host when there is enough writable space.
395 * The host is optimized to send notifications only when the pending
449 union hvs_service_id vm, host;
456 host.srv_id = srv_id_template;
457 host.svm_port = vsk->remote_addr.svm_port;
458 h->host_srv_id = host.srv_id;
849 * in vmbus_probe(): on error the host will rescind the device in