src-test/sys/dev/hyperv, branch main

hyperv/vmbus: avoid crash, panic if vbe fb info is missing

2020-12-10T13:11:52Z

Do not assume that VBE framebuffer metadata can be used. Like with the EFI fb metadata, it may be null, so we should take care not to dereference the null vbefb pointer. This avoids a panic when booting -CURRENT on a gen1 VM in Azure. Approved by: tsoome Sponsored by: Miles AS Differential Revision: https://reviews.freebsd.org/D27533

fix vmbus_fb_mmio_res after r368168

2020-11-30T08:31:41Z

mixed efifb versus vbefb struct use did slip in by mistake.

Add VT driver for VBE framebuffer device

2020-11-30T08:22:40Z

Implement vt_vbefb to support Vesa Bios Extensions (VBE) framebuffer with VT. vt_vbefb is built based on vt_efifb and is assuming similar data for initialization, use MODINFOMD_VBE_FB to identify the structure vbe_fb in kernel metadata. struct vbe_fb, is populated by boot loader, and is passed to kernel via metadata payload. Differential Revision: https://reviews.freebsd.org/D27373

Hyper-V: hn: Relinquish cpu in HN_LOCK to avoid deadlock

2020-10-15T11:44:28Z

The try lock loop in HN_LOCK put the thread spinning on cpu if the lock is not available. It is possible to cause deadlock if the thread holding the lock is sleeping. Relinquish the cpu to work around this problem even it doesn't completely solve the issue. The priority inversion could cause the livelock no matter how less likely it could happen. A more complete solution may be needed in the future. Reported by: Microsoft, Netapp MFC after: 2 weeks Sponsored by: Microsoft

Hyper-V: pcib: Check revoke status during device attach

2020-10-15T05:57:20Z

It is possible that the vmbus pcib channel is revoked during attach path. The attach path could be waiting for response from host and this response will never arrive since the channel has already been revoked from host point of view. Check this situation during wait complete and return failed if this happens. Reported by: Netapp MFC after: 2 weeks Sponsored by: Microsoft Differential Revision: https://reviews.freebsd.org/D26486

Hyper-V: storvsc: Enhance srb_status code handling.

2020-08-31T09:05:45Z

In hv_storvsc_io_request() when coring, prevent changing of the send channel from the base channel to another one. storvsc_poll always probes on the base channel. Based upon conversations with Microsoft, changed the handling of srb_status codes. Most we should never get, others yes. All are treated as retry-able except for two. We should not get these statuses, but if we ever do, the I/O state is not known. Submitted by: Alexander Sideropoulos Reviewed by: trasz, allanjude, whu MFC after: 1 week Sponsored by: Netapp Inc Differential Revision: https://reviews.freebsd.org/D25756

Prevent framebuffer mmio space from being allocated to other devices on HyperV.

2020-07-30T07:26:11Z

On Gen2 VMs, Hyper-V provides mmio space for framebuffer. This mmio address range is not useable for other PCI devices. Currently only efifb driver is using this range without reserving it from system. Therefore, vmbus driver reserves it before any other PCI device drivers start to request mmio addresses. PR: 222996 Submitted by: weh@microsoft.com Reported by: dmitry_kuleshov@ukr.net Reviewed by: decui@microsoft.com Sponsored by: Microsoft

Socket AF_HYPERV should return failure when it is not running on HyperV

2020-05-22T09:17:07Z

Reported by: pho Sponsored by: Microsoft

Fix i386 build for r361275

2020-05-20T13:51:27Z

kponsored by: The FreeBSD Foundation

HyperV socket implementation for FreeBSD

2020-05-20T11:03:59Z

This change adds Hyper-V socket feature in FreeBSD. New socket address family AF_HYPERV and its kernel support are added. Submitted by: Wei Hu Reviewed by: Dexuan Cui Relnotes: yes Sponsored by: Microsoft Differential Revision: https://reviews.freebsd.org/D24061