Home
last modified time | relevance | path

Searched full:vmbus (Results 1 – 25 of 40) 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 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 …]
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.
H A Dindex.rst11 vmbus
/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()
/linux/Documentation/devicetree/bindings/bus/
H A Dmicrosoft,vmbus.yaml4 $id: http://devicetree.org/schemas/bus/microsoft,vmbus.yaml#
7 title: Microsoft Hyper-V VMBus
13 VMBus is a software bus that implement the protocols for communication
18 const: microsoft,vmbus
47 vmbus@ff0000000 {
48 compatible = "microsoft,vmbus";
/linux/drivers/hv/
H A Dconnection.c49 * Table of VMBus versions listed from newest to oldest.
65 * Maximal VMBus protocol version guests can negotiate. Useful to cap the
66 * VMBus version for testing and debugging purpose.
72 "Maximal VMBus protocol version which can be negotiated");
89 * VMBus protocol 5.0 (VERSION_WIN10_V5) and higher require that we must in vmbus_negotiate_version()
173 /* Initialize the vmbus connection */ in vmbus_connect()
210 * Setup the vmbus event connection for channel interrupt in vmbus_connect()
268 * Negotiate a compatible VMBUS version number with the in vmbus_connect()
293 pr_err("Invalid VMBus version %d.%d (expected >= %d.%d) from the host supporting isolation\n", in vmbus_connect()
300 pr_info("Vmbus version:%d.%d\n", in vmbus_connect()
[all …]
H A Dvmbus_drv.c60 * vmbus connection, which is necessary in a panic event.
63 * framebuffer panic notifier exists - we need vmbus connection alive
189 return sysfs_emit(buf, "vmbus:%*phN\n", UUID_SIZE, &hv_dev->dev_type); in modalias_show()
551 /* Set up per device attributes in /sys/bus/vmbus/devices/<bus device> */
615 /* Set up the attribute for /sys/bus/vmbus/hibernation */
635 * This routine is invoked when a device is added or removed on the vmbus to
639 * The alias string will be of the form vmbus:guid where guid is the string
646 const char *format = "MODALIAS=vmbus:%*phN"; in vmbus_uevent()
828 * vmbus_probe - Add the new vmbus's child device
854 * vmbus_dma_configure -- Configure DMA coherence for VMbus device
[all …]
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 Dhv.c415 unsigned long *recv_int_page = event->flags; /* assumes VMBus version >= VERSION_WIN8 */ in hv_synic_event_pending()
423 /* Special case - VMBus channel protocol messages */ in hv_synic_event_pending()
451 * path where the vmbus is already disconnected, the CPU must be in hv_synic_cleanup()
459 * cleanup. In case we find one and vmbus is still connected, we in hv_synic_cleanup()
490 * and VMBus is connected, fail the CPU offlining operation. in hv_synic_cleanup()
H A Dhyperv_vmbus.h220 * The CPU that Hyper-V will interrupt for VMBUS messages, such as
237 * channel. When a channel sends an interrupt via VMBUS, it finds its
272 * On suspension of the vmbus, the accumulated offer messages
342 /* General vmbus interface */
H A Dchannel.c291 * CHANNELMSG_MODIFYCHANNEL messages are aynchronous. When VMbus version 5.3
293 * message. For VMbus version 5.2 and earlier, it never sends an ACK. With-
297 * The CHANNELMSG_MODIFYCHANNEL message type is supported since VMBus version
1019 * Sends data in @buffer directly to Hyper-V via the vmbus.
1065 * Sends data in @buffer directly to Hyper-V via the vmbus.
1141 * The buffer includes the vmbus descriptor.
1185 * Receives directly from the hyper-v vmbus and puts the data it received
1225 * @channel: Pointer to the VMbus channel struct
1327 * @channel: Pointer to the VMbus channel struct
H A Dhv_snapshot.c34 /* See comment with struct hv_vss_msg regarding the max VMbus packet size */
52 * read additional packets from the VMBUs until the current packet is fully
72 static const char vss_devname[] = "vmbus/hv_vss";
/linux/drivers/clocksource/
H A Dhyperv_timer.c35 * where it sends a VMbus message when it expires. The old
40 * Because Direct Mode does not require processing a VMbus
46 * delayed until VMbus is initialized and can process the
57 * as a VMbus message.
117 * When it expires, the timer will generate a VMbus message, in hv_ce_set_oneshot()
118 * to be handled by the normal VMbus interrupt handler. in hv_ce_set_oneshot()
317 * hv_stimer_legacy_init -- Called from the VMbus driver to handle
340 * hv_stimer_legacy_cleanup -- Called from the VMbus driver to
355 * vmbus exit
/linux/include/linux/
H A Dhyperv.h249 * VMBUS version is 32 bit entity broken up into
520 /* Query VMBus Version parameters */
526 /* VMBus Version Supported parameters */
578 /* Identifies the specific VMBus channel that is being opened. */
718 * On new hosts that support VMBus protocol 5.0, we must use
736 * Represents each channel msg on the vmbus connection This is a
801 * Provides request ids for VMBus. Encapsulates guest memory
969 * Support per-channel state for use by vmbus drivers.
1064 /* request/transaction ids for VMBus */
1276 * from vmbus driver to hvsock driver, we can handle hvsock offer as
[all …]
/linux/drivers/pci/controller/
H A Dpci-hyperv.c96 * Size of requestor for VMbus; the value is based on the observation
702 * always fails since the vmbus channel has been closed: in hv_arch_irq_unmask()
2032 * remove the ID from the VMbus requestor if the identifier is still in hv_compose_msi_msg()
2709 "PCI VMBus BUS_RELATIONS: ignored\n"); in hv_pci_start_relations_work()
2894 dev_info(&hdev->device, "PCI VMBus EJECT: ignored\n"); in hv_pci_eject_device()
3080 * @hdev: VMBus's tracking struct for this root PCI bus.
3089 * asynchronous messaging via VMBus. Windows 10 increases the
3143 "PCI VMBus probing: Using version %#x\n", in hv_pci_protocol_negotiation()
3202 * node (in this case, VMBus) or change it such that it
3203 * understands VMBus. The pnp layer, however, has been declared
[all …]
/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/net/vmw_vsock/
H A DKconfig80 Sockets over Hyper-V VMBus.
/linux/include/clocksource/
H A Dhyperv_timer.h27 /* Routines called by the VMbus driver */
/linux/drivers/gpu/drm/hyperv/
H A Dhyperv_drm_proto.c211 drm_err_ratelimited(&hv->dev, "Unable to send packet via vmbus; error %d\n", ret); in hyperv_sendpacket()
484 drm_err(dev, "Unable to open vmbus channel\n"); in hyperv_connect_vsp()

12