Home
last modified time | relevance | path

Searched full:vmbus (Results 1 – 25 of 28) sorted by relevance

12

/linux/Documentation/ABI/stable/
H A Dsysfs-bus-vmbus1 What: /sys/bus/vmbus/hibernation
8 What: /sys/bus/vmbus/devices/<UUID>/id
12 Description: The VMBus child_relid of the device's primary channel
15 What: /sys/bus/vmbus/devices/<UUID>/class_id
19 Description: The VMBus interface type GUID of the device
22 What: /sys/bus/vmbus/devices/<UUID>/device_id
26 Description: The VMBus interface instance GUID of the device
29 What: /sys/bus/vmbus/devices/<UUID>/channel_vp_mapping
38 What: /sys/bus/vmbus/devices/<UUID>/device
45 What: /sys/bus/vmbus/devices/<UUID>/vendor
[all …]
/linux/Documentation/virt/hyperv/
H A Dcoco.rst171 CoCo VMs, Hyper-V has VMBus and VMBus devices that communicate using memory
177 These Hyper-V and VMBus memory pages are marked as decrypted:
179 * VMBus monitor pages
186 * VMBus ring buffers. The direct mapping is marked decrypted in
200 VMBus ring buffer, the length of the message is validated, and the message is
205 Many drivers for VMBus devices have been "hardened" by adding code to fully
206 validate messages received over VMBus, instead of assuming that Hyper-V is
208 vmbus_devs[] table. Other drivers for VMBus devices that are not needed in a
212 Two VMBus devices depend on the Hyper-V host to do DMA data transfers:
225 Finally, the VMBus virtual PCI driver needs special handling in a CoCo VM.
[all …]
H A Dvpci.rst43 guests as VMBus devices via the standard VMBus "offer"
44 mechanism, so they have a VMBus identity and appear under
45 /sys/bus/vmbus/devices. The VMBus vPCI driver in Linux at
54 presented dynamically through the VMBus offer mechanism, they
59 With this approach, the vPCI device is a VMBus device and a
60 PCI device at the same time. In response to the VMBus offer
62 VMBus connection to the vPCI VSP on the Hyper-V host. That
63 connection has a single VMBus channel. The channel is used to
66 is fully configured in Linux as a PCI device, the VMBus
71 the device and the hardware, with VMBus and the VMBus channel
[all …]
/linux/tools/hv/
H A Dvmbus_testing134 print("Error, path '{}' not a valid vmbus device".format(path))
144 # Create a map of the vmbus devices and their associated files
174 # read the vmbus device files, path must be absolute path before calling
190 # writing to vmbus device files, path must be absolute path before calling
279 description = "\nUse lsvmbus to get vmbus device type "
296 help = "Debugfs path to a vmbus device. The path "
303 "on ALL vmbus devices.")
308 "SINGLE vmbus device.")
318 "vmbus devices, or delay the ring buffer message "
319 "reads for vmbus devices (both in microseconds). This "
[all …]
H A Dlsvmbus18 vmbus_sys_path = '/sys/bus/vmbus/devices'
99 print(('VMBUS ID ' + format0) % (d.vmbus_id, d.dev_desc))
102 ('VMBUS ID ' + format1) %
107 ('VMBUS ID ' + format2) %
H A Dhv_fcopy_daemon.c
H A Dhv_vss_daemon.c259 vss_fd = open("/dev/vmbus/hv_vss", O_RDWR); in main()
261 syslog(LOG_ERR, "open /dev/vmbus/hv_vss failed; error: %d %s", in main()
H A Dhv_fcopy_uio_daemon.c39 "/sys/bus/vmbus/devices/eb765408-105f-49b6-b4aa-c123b64d17d4/" #subdir
539 syslog(LOG_ERR, "VMBus channel recv error: %d", ret); in main()
H A Dhv_kvp_daemon.c1843 kvp_fd = open("/dev/vmbus/hv_kvp", O_RDWR | O_CLOEXEC); in main()
1846 syslog(LOG_ERR, "open /dev/vmbus/hv_kvp failed; error: %d %s", in main()
/linux/drivers/uio/
H A Duio_hv_generic.c3 * uio_hv_generic - generic UIO driver for VMBus
13 * > /sys/bus/vmbus/drivers/uio_hv_generic/new_id
16 * > /sys/bus/vmbus/drivers/hv_netvsc/unbind
18 * > /sys/bus/vmbus/drivers/uio_hv_generic/bind
37 #define DRIVER_DESC "Generic UIO driver for VMBus devices"
146 * from vmbus when the primary channel is rescinded. in hv_uio_rescind()
148 * Unregister the device from vmbus here. in hv_uio_rescind()
169 /* Callback from VMBUS subsystem when new channel created. */
211 /* VMBus primary channel is opened on first use */
234 /* VMBus primary channel is closed on last close */
[all …]
H A DKconfig142 tristate "Generic driver for Hyper-V VMBus"
146 Hyper-V VMBus device. It is useful to provide direct access
/linux/net/vmw_vsock/
H A Dhyperv_transport.c18 /* Older (VMBUS version 'VERSION_WIN10' or before) Windows hosts have some
38 /* For recv, we use the VMBus in-place packet iterator APIs to directly copy
51 * guest and the host processing as one VMBUS packet is the smallest processing
54 * Note: the buffer can be eliminated in the future when we add new VMBus
56 * to VMBus ringbuffer.
81 /* Upper bound on the size of a VMbus packet for hv_sock */
132 * VMBus, because here it's obvious the host and the VM can easily identify
359 /* Use the socket buffer sizes as hints for the VMBUS ring size. For in hvs_open_connection()
362 * the mins to the default value and align to page size as per VMBUS in hvs_open_connection()
366 * VMBUS rin in hvs_open_connection()
[all...]
H A DKconfig80 Sockets over Hyper-V VMBus.
/linux/drivers/hv/
H A Dhv_debugfs.c82 /* Setup test state value for vmbus device */
147 /* Remove all dentrys associated with vmbus testing */
153 /* Delay buffer/message reads on a vmbus channel */
169 /* Initialize top dentry for vmbus testing */
H A Dhyperv_vmbus.h243 * The CPU that Hyper-V will interrupt for VMBUS messages, such as
260 * channel. When a channel sends an interrupt via VMBUS, it finds its
296 * On suspension of the vmbus, the accumulated offer messages
358 /* General vmbus interface */
H A Dchannel.c296 * CHANNELMSG_MODIFYCHANNEL messages are aynchronous. When VMbus version 5.3
298 * message. For VMbus version 5.2 and earlier, it never sends an ACK. With-
302 * The CHANNELMSG_MODIFYCHANNEL message type is supported since VMBus version
1218 * Sends data in @buffer directly to Hyper-V via the vmbus.
1264 * Sends data in @buffer directly to Hyper-V via the vmbus.
1281 * The desc argument must include space for the VMBus descriptor. The
1325 * Receives directly from the hyper-v vmbus and puts the data it received
1365 * @channel: Pointer to the VMbus channel struct
1467 * @channel: Pointer to the VMbus channel struct
H A Dring_buffer.c459 * Get first vmbus packet from ring buffer after read_index
516 * Get next vmbus packet from ring buffer.
H A Dmshv_vtl_main.c869 pr_debug("%s: Unmasking VTL2 VMBUS SINT on VP %d\n", __func__, smp_processor_id()); in mshv_vtl_synic_mask_vmbus_sint()
871 pr_debug("%s: Masking VTL2 VMBUS SINT on VP %d\n", __func__, smp_processor_id()); in mshv_vtl_synic_mask_vmbus_sint()
1339 * mshv_sint device adds VMBus relay ioctl support. in mshv_vtl_init()
H A Dhv_util.c705 MODULE_DEVICE_TABLE(vmbus, id_table);
/linux/Documentation/driver-api/
H A Duio-howto.rst668 supports devices on the Hyper-V VMBus similar to uio_pci_generic on
680 echo "f8615163-df3e-46c5-913f-f2d2f965ed0e" > /sys/bus/vmbus/drivers/uio_hv_generic/new_id
688 echo -n ed963694-e847-4b2a-85af-bc9cfc11d6f3 > /sys/bus/vmbus/drivers/hv_netvsc/unbind
689 echo -n ed963694-e847-4b2a-85af-bc9cfc11d6f3 > /sys/bus/vmbus/drivers/uio_hv_generic/bind
694 ls -l /sys/bus/vmbus/devices/ed963694-e847-4b2a-85af-bc9cfc11d6f3/driver
698 .../ed963694-e847-4b2a-85af-bc9cfc11d6f3/driver -> ../../../bus/vmbus/drivers/uio_hv_generic
712 The vmbus device regions are mapped into uio device resources:
723 /sys/bus/vmbus/devices/3811fe4d-0fa0-4b62-981a-74fc1084c757/channels/21/ring
/linux/Documentation/ABI/testing/
H A Ddebugfs-hyperv5 Description: Fuzz testing status of a vmbus device, whether its in an ON
H A Dsysfs-bus-vmbus1 What: /sys/bus/vmbus/devices/.../driver_override
/linux/drivers/input/serio/
H A Dhyperv-keyboard.c410 MODULE_DEVICE_TABLE(vmbus, id_table);
/linux/include/uapi/linux/
H A Dmshv.h398 /* VMBus device IOCTLs */
/linux/scripts/mod/
H A Dfile2alias.c832 * Looks like: vmbus:guid
844 module_alias_printf(mod, false, "vmbus:%s", guid_name); in do_vmbus_entry()
1492 {"vmbus", SIZE_hv_vmbus_device_id, do_vmbus_entry},

12