Home
last modified time | relevance | path

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

123

/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 Dvmbus.rst3 VMBus title
5 VMBus is a software construct provided by Hyper-V to guest VMs. It
15 VMBus is modeled in Linux as a bus, with the expected /sys/bus/vmbus
16 entry in a running Linux guest. The VMBus driver (drivers/hv/vmbus_drv.c)
17 establishes the VMBus control path with the Hyper-V host, then
52 VMBus channels
54 An instance of a synthetic device uses VMBus channels to communicate
76 VMBus control path as a GPA Descriptor List (GPADL). See function
105 VMBus channel messages
107 All messages sent in a VMBus channel have a standard header that includes
[all …]
H A Dhibernation.rst87 enablement is also visible in /sys/bus/vmbus/hibernation. See function
106 Handling VMBus Devices During Hibernation & Resume
108 The VMBus bus driver, and the individual VMBus device drivers,
112 primary VMBus channels and their associated Linux devices, such as
120 VMBus devices are identified by class and instance GUID. (See section
121 "VMBus device creation/deletion" in
122 Documentation/virt/hyperv/vmbus.rst.) Upon resume from hibernation,
126 devices to be matched to the primary VMBus channel data structures in
128 offered that don't match primary VMBus channel data structures that
130 primary VMBus channels that exist in the resumed hibernation image are
[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.
[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 …]
H A Doverview.rst43 * VMBus: VMBus is a higher-level software construct that is built on
57 VMBus is not documented. This documentation provides a high-level
58 overview of VMBus and how it works, but the details can be discerned
77 in a VMBus message.
136 mechanisms, provided no VMBus channel interrupts are assigned to
137 the CPU. See the section on VMBus Interrupts for more details
138 on how VMBus channel interrupts can be re-assigned to permit
172 VMBus has its own protocol version that is negotiated during the
173 initial VMBus connection from the guest to Hyper-V. This version
178 Furthermore, each synthetic device on VMBus also has a protocol
[all …]
H A Dclocks.rst68 results in a VMBus control message that is demultiplexed by
69 vmbus_isr() as described in the Documentation/virt/hyperv/vmbus.rst
/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) %
/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 implements the protocols for communication
18 const: microsoft,vmbus
56 vmbus@ff0000000 {
57 compatible = "microsoft,vmbus";
/linux/drivers/hv/
H A Dconnection.c49 * Table of VMBus versions listed from newest to oldest.
66 * Maximal VMBus protocol version guests can negotiate. Useful to cap the
67 * VMBus version for testing and debugging purpose.
73 "Maximal VMBus protocol version which can be negotiated");
90 * VMBus protocol 5.0 (VERSION_WIN10_V5) and higher require that we must in vmbus_negotiate_version()
177 /* Initialize the vmbus connection */ in vmbus_connect()
222 * Setup the vmbus event connection for channel interrupt in vmbus_connect()
281 * Negotiate a compatible VMBUS version number with the in vmbus_connect()
306 pr_err("Invalid VMBus version %d.%d (expected >= %d.%d) from the host supporting isolation\n", in vmbus_connect()
313 pr_info("Vmbus version:%d.%d\n", in vmbus_connect()
[all …]
H A Dvmbus_drv.c50 /* VMBus Root Device */
62 * If the Confidential VMBus is used, the data on the "wire" is not
75 * vmbus connection, which is necessary in a panic event.
78 * framebuffer panic notifier exists - we need vmbus connection alive
210 return sysfs_emit(buf, "vmbus:%*phN\n", UUID_SIZE, &hv_dev->dev_type); in modalias_show()
572 /* Set up per device attributes in /sys/bus/vmbus/devices/<bus device> */
636 /* Set up the attribute for /sys/bus/vmbus/hibernation */
656 * This routine is invoked when a device is added or removed on the vmbus to
660 * The alias string will be of the form vmbus:guid where guid is the string
667 const char *format = "MODALIAS=vmbus:%*phN"; in vmbus_uevent()
[all …]
H A Dhv.c81 * If the VMBus isn't confidential, use the CoCo-specific in hv_post_message()
99 * In the Confidential VMBus case, there is the paravisor in hv_post_message()
387 * VMBus is confidential). in hv_synic_init()
389 * Then enable interrupts via the paravisor if VMBus is confidential, in hv_synic_init()
512 recv_int_page = event->flags; /* assumes VMBus version >= VERSION_WIN8 */ in __hv_synic_event_pending()
516 /* Special case - VMBus channel protocol messages */ in __hv_synic_event_pending()
589 * path where the vmbus is already disconnected, the CPU must be in hv_synic_cleanup()
623 * are still set after this operation and VMBus is connected, fail the in hv_synic_cleanup()
635 * disable the host interrupts if VMBus is not in hv_synic_cleanup()
643 * Perform the same steps for the Confidential VMBus. in hv_synic_cleanup()
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 DKconfig62 tristate "Microsoft Hyper-V VMBus driver"
66 Select this option to enable Hyper-V Vmbus driver.
107 space to a usermode process in VTL2 and supports getting new VMBus messages and channel
H A Dchannel_mgmt.c351 * alloc_channel - Allocate and initialize a vmbus channel object
375 * free_channel - Release the resources used by the vmbus channel object
409 * the VMBus connection is marked as ready for the resume event in vmbus_channel_map_relid()
411 * of the VMBus driver and vmbus_chan_sched() can not run before in vmbus_channel_map_relid()
831 * data in its disk cache before the VMbus UNLOAD request will in vmbus_wait_for_unload()
879 pr_notice("Waiting for VMBus UNLOAD to complete\n"); in vmbus_wait_for_unload()
883 pr_err("Continuing even though VMBus UNLOAD did not complete\n"); in vmbus_wait_for_unload()
1017 * vmbus_onoffer - Handler for channel offers from vmbus in parent partition.
1047 pr_err("Invalid offer relid=%d: no support for confidential VMBus\n", in vmbus_onoffer()
1100 * Mellanox VF vmbus device can change when the host in vmbus_onoffer()
[all …]
H A Dchannel.c292 * CHANNELMSG_MODIFYCHANNEL messages are aynchronous. When VMbus version 5.3
294 * message. For VMbus version 5.2 and earlier, it never sends an ACK. With-
298 * The CHANNELMSG_MODIFYCHANNEL message type is supported since VMBus version
1041 * Sends data in @buffer directly to Hyper-V via the vmbus.
1087 * Sends data in @buffer directly to Hyper-V via the vmbus.
1104 * The desc argument must include space for the VMBus descriptor. The
1148 * Receives directly from the hyper-v vmbus and puts the data it received
1188 * @channel: Pointer to the VMbus channel struct
1290 * @channel: Pointer to the VMbus channel struct
H A Dhyperv_vmbus.h241 * The CPU that Hyper-V will interrupt for VMBUS messages, such as
258 * channel. When a channel sends an interrupt via VMBUS, it finds its
293 * On suspension of the vmbus, the accumulated offer messages
355 /* General vmbus interface */
/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()
168 /* Callback from VMBUS subsystem when new channel created. */
210 /* VMBus primary channel is opened on first use */
233 /* VMBus primary channel is closed on last close */
H A DKconfig142 tristate "Generic driver for Hyper-V VMBus"
146 Hyper-V VMBus device. It is useful to provide direct access
/linux/drivers/clocksource/
H A Dhyperv_timer.c36 * where it sends a VMbus message when it expires. The old
41 * Because Direct Mode does not require processing a VMbus
47 * delayed until VMbus is initialized and can process the
58 * as a VMbus message.
118 * When it expires, the timer will generate a VMbus message, in hv_ce_set_oneshot()
119 * to be handled by the normal VMbus interrupt handler. in hv_ce_set_oneshot()
318 * hv_stimer_legacy_init -- Called from the VMbus driver to handle
341 * hv_stimer_legacy_cleanup -- Called from the VMbus driver to
356 * vmbus exit
/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 ring buffer is physically contiguous allocation, restrict it in hvs_open_connection()
[all …]
/linux/include/linux/
H A Dhyperv.h249 * VMBUS version is 32 bit entity broken up into
474 /* Query VMBus Version parameters */
480 /* VMBus Version Supported parameters */
532 /* Identifies the specific VMBus channel that is being opened. */
650 u32 feature_flags; /* VMBus version 6.0 */
679 * On new hosts that support VMBus protocol 5.0, we must use
697 * Represents each channel msg on the vmbus connection This is a
748 * Provides request ids for VMBus. Encapsulates guest memory
916 * Support per-channel state for use by vmbus drivers.
1011 /* request/transaction ids for VMBus */
[all …]
/linux/drivers/pci/controller/
H A Dpci-hyperv.c98 * Size of requestor for VMbus; the value is based on the observation
699 * always fails since the vmbus channel has been closed: in hv_irq_retarget_interrupt()
971 WARN_ONCE(1, "Invalid firmware configuration for VMBus interrupts\n"); in hv_pci_irqchip_init()
2094 * remove the ID from the VMbus requestor if the identifier is still in hv_compose_msi_msg()
2838 "PCI VMBus BUS_RELATIONS: ignored\n"); in hv_pci_start_relations_work()
3021 dev_info(&hdev->device, "PCI VMBus EJECT: ignored\n"); in hv_pci_eject_device()
3207 * @hdev: VMBus's tracking struct for this root PCI bus.
3216 * asynchronous messaging via VMBus. Windows 10 increases the
3270 "PCI VMBus probing: Using version %#x\n", in hv_pci_protocol_negotiation()
3329 * node (in this case, VMBus) or change it such that it
[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

123