<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/sys/dev/hyperv/vmbus, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/'/>
<updated>2020-12-10T13:11:52Z</updated>
<entry>
<title>hyperv/vmbus: avoid crash, panic if vbe fb info is missing</title>
<updated>2020-12-10T13:11:52Z</updated>
<author>
<name>Bradley T. Hughes</name>
<email>bhughes@FreeBSD.org</email>
</author>
<published>2020-12-10T13:11:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=c05b5848f11b4b551b104a183231409ed4874c66'/>
<id>urn:sha1:c05b5848f11b4b551b104a183231409ed4874c66</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>fix vmbus_fb_mmio_res after r368168</title>
<updated>2020-11-30T08:31:41Z</updated>
<author>
<name>Toomas Soome</name>
<email>tsoome@FreeBSD.org</email>
</author>
<published>2020-11-30T08:31:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=cb794182660ddf2ea5dd5479abfce2ec0bb8c01f'/>
<id>urn:sha1:cb794182660ddf2ea5dd5479abfce2ec0bb8c01f</id>
<content type='text'>
mixed efifb versus vbefb struct use did slip in by mistake.
</content>
</entry>
<entry>
<title>Add VT driver for VBE framebuffer device</title>
<updated>2020-11-30T08:22:40Z</updated>
<author>
<name>Toomas Soome</name>
<email>tsoome@FreeBSD.org</email>
</author>
<published>2020-11-30T08:22:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=a4a10b37d422dcdff2b0d700ab073b3078627a08'/>
<id>urn:sha1:a4a10b37d422dcdff2b0d700ab073b3078627a08</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Prevent framebuffer mmio space from being allocated to other devices on HyperV.</title>
<updated>2020-07-30T07:26:11Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2020-07-30T07:26:11Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=c565776195f2f2b62427af07f6b1a9b7670cbc1f'/>
<id>urn:sha1:c565776195f2f2b62427af07f6b1a9b7670cbc1f</id>
<content type='text'>
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
</content>
</entry>
<entry>
<title>Fix i386 build for r361275</title>
<updated>2020-05-20T13:51:27Z</updated>
<author>
<name>Li-Wen Hsu</name>
<email>lwhsu@FreeBSD.org</email>
</author>
<published>2020-05-20T13:51:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=db7ec3c3e66b29aa1aee328d77a9a32dd3f8e812'/>
<id>urn:sha1:db7ec3c3e66b29aa1aee328d77a9a32dd3f8e812</id>
<content type='text'>
kponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>HyperV socket implementation for FreeBSD</title>
<updated>2020-05-20T11:03:59Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2020-05-20T11:03:59Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=a560f3ebd77733208fa8371a5f2d09523e847c0d'/>
<id>urn:sha1:a560f3ebd77733208fa8371a5f2d09523e847c0d</id>
<content type='text'>
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 &lt;weh@microsoft.com&gt;
Reviewed by:	Dexuan Cui &lt;decui@microsoft.com&gt;
Relnotes:	yes
Sponsored by:	Microsoft
Differential Revision:	https://reviews.freebsd.org/D24061
</content>
</entry>
<entry>
<title>hyperv: Add Hygon Dhyana support.</title>
<updated>2020-02-13T19:12:07Z</updated>
<author>
<name>Konstantin Belousov</name>
<email>kib@FreeBSD.org</email>
</author>
<published>2020-02-13T19:12:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=4e012582d35afc1d896bd0abb74572f257d2c364'/>
<id>urn:sha1:4e012582d35afc1d896bd0abb74572f257d2c364</id>
<content type='text'>
Submitted by:	Pu Wen &lt;puwen@hygon.cn&gt;
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D23563
</content>
</entry>
<entry>
<title>hyperv/vmbus: Update VMBus version 4.0 and 5.0 support.</title>
<updated>2019-07-09T07:24:18Z</updated>
<author>
<name>Wei Hu</name>
<email>whu@FreeBSD.org</email>
</author>
<published>2019-07-09T07:24:18Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=ace5ce7e701e5a98c23f820d4f126e5c265aa667'/>
<id>urn:sha1:ace5ce7e701e5a98c23f820d4f126e5c265aa667</id>
<content type='text'>
Add VMBus protocol version 4.0. and 5.0 to support Windows 10 and newer HyperV hosts.

For VMBus 4.0 and newer HyperV, the netvsc gpadl teardown must be done after vmbus close.

Submitted by:	whu
MFC after:	2 weeks
Sponsored by:	Microsoft
</content>
</entry>
<entry>
<title>Distinguish _CID match and _HID match and make lower priority probe</title>
<updated>2018-10-26T00:05:46Z</updated>
<author>
<name>Takanori Watanabe</name>
<email>takawata@FreeBSD.org</email>
</author>
<published>2018-10-26T00:05:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=5efca36fbda65afe7726d685dcc43a707ef76447'/>
<id>urn:sha1:5efca36fbda65afe7726d685dcc43a707ef76447</id>
<content type='text'>
when _CID match.

Reviewed by: jhb, imp
Differential Revision:https://reviews.freebsd.org/D16468
</content>
</entry>
<entry>
<title>Eliminate the arena parameter to kmem_free().  Implicitly this corrects an</title>
<updated>2018-08-25T19:38:08Z</updated>
<author>
<name>Alan Cox</name>
<email>alc@FreeBSD.org</email>
</author>
<published>2018-08-25T19:38:08Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=49bfa624ac861d7fafc87f06dc2cdf4972aed854'/>
<id>urn:sha1:49bfa624ac861d7fafc87f06dc2cdf4972aed854</id>
<content type='text'>
error in the function hypercall_memfree(), where the wrong arena was being
passed to kmem_free().

Introduce a per-page flag, VPO_KMEM_EXEC, to mark physical pages that are
mapped in kmem with execute permissions.  Use this flag to determine which
arena the kmem virtual addresses are returned to.

Eliminate UMA_SLAB_KRWX.  The introduction of VPO_KMEM_EXEC makes it
redundant.

Update the nearby comment for UMA_SLAB_KERNEL.

Reviewed by:	kib, markj
Discussed with:	jeff
Approved by:	re (marius)
Differential Revision:	https://reviews.freebsd.org/D16845
</content>
</entry>
</feed>
