Skip to content

hyperv: VMBus implementation

Jon Doron qemu-devel 4 versions – Applied

Status from this message: Queued, thanks. I'll take a look at the EOM handling threads next.

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v4 Latest6 patches 24 repliesApplied
  2. v37 patches 0 repliesSuperseded
  3. v27 patches 0 repliesSuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v15 patches19 repliesSuperseded

Changes in v4 from the cover letter

Decided to ditch the patch that envolves handling of EOM as there is still a discussion going on with it in the KVM mailing list.

Patches in v4 Applied

#Subject and filesSizeRepliesApplied
1/6hyperv: expose API to determine if synic is enabledhw/hyperv/hyperv.c include/hw/hyperv/hyperv.h+9 -00 replies
2/6vmbus: add vmbus protocol definitionsinclude/hw/hyperv/vmbus-proto.h+222 -00 replies
3/6vmbus: vmbus implementationMakefile.objs hw/hyperv/Kconfig hw/hyperv/Makefile.objs +4 more+2956 -00 replies
4/6i386:pc: whitelist dynamic vmbus-bridgehw/i386/pc_piix.c hw/i386/pc_q35.c+4 -00 replies
5/6i386: Hyper-V VMBus ACPI DSDT entryhw/hyperv/vmbus.c hw/i386/acpi-build.c include/hw/hyperv/vmbus-bridge.h+53 -021 replies
6/6vmbus: add infrastructure to save/load vmbus requestshw/hyperv/vmbus.c include/hw/hyperv/vmbus.h+102 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.

Read the v4 thread

Cover letter [PATCH v4 0/6] hyperv: VMBus implementation

This is a rebase of the old patchset from Roman for HyperV VMBus implementation.

How to use:
-device vmbus-bridge

Later on new paravirtualized devices can be implemented on top of it (Network/SCSI/etc.)

VMBus is a collection of technologies. At its lowest layer, it's a message passing and signaling mechanism, allowing efficient passing of messages to and from guest VMs. A layer higher, it's a mechanism for defining channels of communication, where each channel is tagged with a type (which implies a protocol) and a instance ID. A layer higher than that, it's a bus driver, serving as the basis of device enumeration within a VM, where a channel can optionally be exposed as a paravirtual device. When a server-side (paravirtual back-end) component wishes to offer a channel to a guest VM, it does so by specifying a channel type, a mode, and an instance ID. VMBus then exposes this in the guest.

More information about VMBus can be found in the file vmbuskernelmodeclientlibapi.h in Microsoft's WDK.

v4:
Decided to ditch the patch that envolves handling of EOM as there is still a discussion going on with it in the KVM mailing list.

v3:
Fixed an error asan

v2:
Rebased on top of latest patchset from Roman and Maciej

Jon Doron (6):
hyperv: expose API to determine if synic is enabled
vmbus: add vmbus protocol definitions
vmbus: vmbus implementation
i386:pc: whitelist dynamic vmbus-bridge
i386: Hyper-V VMBus ACPI DSDT entry
vmbus: add infrastructure to save/load vmbus requests

 Makefile.objs                    |    1 +
 hw/hyperv/Kconfig                |    5 +
 hw/hyperv/Makefile.objs          |    1 +
 hw/hyperv/hyperv.c               |    8 +
 hw/hyperv/trace-events           |   18 +
 hw/hyperv/vmbus.c                | 2778 ++++++++++++++++++++++++++++++
 hw/i386/acpi-build.c             |   43 +
 hw/i386/pc_piix.c                |    2 +
 hw/i386/pc_q35.c                 |    2 +
 include/hw/hyperv/hyperv.h       |    1 +
 include/hw/hyperv/vmbus-bridge.h |   35 +
 include/hw/hyperv/vmbus-proto.h  |  222 +++
 include/hw/hyperv/vmbus.h        |  230 +++
 13 files changed, 3346 insertions(+)
 create mode 100644 hw/hyperv/trace-events
 create mode 100644 hw/hyperv/vmbus.c
 create mode 100644 include/hw/hyperv/vmbus-bridge.h
 create mode 100644 include/hw/hyperv/vmbus-proto.h
 create mode 100644 include/hw/hyperv/vmbus.h
Signature · 1 line
2.24.1