src/sys/dev/vmd, branch releng/14.2 FreeBSD source tree vmd: Use bus_read/write_* instead of bus_space_read/write_* 2024-04-08T17:57:24+00:00 John Baldwin jhb@FreeBSD.org 2024-02-15T20:26:19+00:00 00907525212d3cbac7f0ad7ea1ed6f65ce0e05aa Using an explicit bus space tag and handle is deprecated. Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D43885 (cherry picked from commit 76c678688634e9e2ea5f6369fb979aabddbfe426) 
Using an explicit bus space tag and handle is deprecated.

Reviewed by:	emaste
Differential Revision:	https://reviews.freebsd.org/D43885

(cherry picked from commit 76c678688634e9e2ea5f6369fb979aabddbfe426)
vmd(4): Fix typos in source code comments 2024-01-25T06:44:55+00:00 Gordon Bergling gbe@FreeBSD.org 2024-01-22T20:55:33+00:00 a499baff3955b9edacd56c44cf30386e26822e17 - s/harwdare/hardware/ (cherry picked from commit b2c48aa4d19268610191a0b7d7b76d01d28b0a13) 
- s/harwdare/hardware/

(cherry picked from commit b2c48aa4d19268610191a0b7d7b76d01d28b0a13)
sys: Remove $FreeBSD$: one-line .c pattern 2023-08-16T17:54:36+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:54:36+00:00 685dc743dc3b5645e34836464128e1c0558b404b Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ 
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
sys: Remove $FreeBSD$: two-line .h pattern 2023-08-16T17:54:11+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:54:11+00:00 95ee2897e98f5d444f26ed2334cc7c439f9c16c6 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ 
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
vmd: Add DID 8086:7D0B and 8086:AD0B for Intel MTL SKUs 2022-10-06T16:44:59+00:00 Alexander Motin mav@FreeBSD.org 2022-10-06T16:44:59+00:00 9bce11410645f4e84521c2ee44d3082aad8ae1e9 MFC after: 2 weeks 
MFC after:	2 weeks
vmd: Bypass MSI/MSI-X remapping when possible. 2022-10-06T16:15:25+00:00 Alexander Motin mav@FreeBSD.org 2022-10-06T16:15:25+00:00 c28220d8661ee1928bff7d2c6bcd3e64c25f927b By default all VMD devices remap children MSI/MSI-X interrupts into their own. It creates additional isolation, but also complicates things due to sharing, etc. Fortunately some VMD devices can bypass the remapping. Add tunable to control it for remap testing or if something go wrong. MFC after: 2 weeks 
By default all VMD devices remap children MSI/MSI-X interrupts into their
own.  It creates additional isolation, but also complicates things due to
sharing, etc.  Fortunately some VMD devices can bypass the remapping.
Add tunable to control it for remap testing or if something go wrong.

MFC after:	2 weeks
vmd: Add 8086:A77F PCI ID for all Intel Raptor Lake SKUs 2022-07-29T18:17:20+00:00 Neel Chauhan nc@FreeBSD.org 2022-07-29T18:06:06+00:00 b07a48d4f3a175db53ba21a40f27ef0c1a6d0a11 Summary: This is based on the Linux kernel commit 922bfd001d1ac02111ebbe0524aaab6ca7925521. Reviewed by: mav (src) MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D35996 
Summary:
This is based on the Linux kernel commit
922bfd001d1ac02111ebbe0524aaab6ca7925521.

Reviewed by:		mav (src)
MFC after:		3 days
Differential Revision:	https://reviews.freebsd.org/D35996
vmd: Remove unused devclass argument to DRIVER_MODULE. 2022-05-06T22:46:59+00:00 John Baldwin jhb@FreeBSD.org 2022-05-06T22:46:59+00:00 44031900628a72b330bd6616f1dda5bc57927983 






Missed line from 7af4475a6e31.
2021-09-03T02:25:16+00:00

Alexander Motin
mav@FreeBSD.org

2021-09-03T02:25:16+00:00

5d9e5a7edfb5a2256be1c6433aaef32433cdd14e

MFC after:	2 weeks





MFC after:	2 weeks







vmd(4): Major driver refactoring
2021-09-03T00:58:02+00:00

Alexander Motin
mav@FreeBSD.org

2021-09-03T00:58:02+00:00

7af4475a6e31202a865b1dd3727018659b44470f

 - Re-implement pcib interface to use standard pci bus driver on top of
vmd(4) instead of custom one.
 - Re-implement memory/bus resource allocation to properly handle even
complicated configurations.
 - Re-implement interrupt handling to evenly distribute children's MSI/
MSI-X interrupts between available vmd(4) MSI-X vectors and setup them
to be handled by standard OS mechanisms with minimal overhead, except
sharing when unavoidable.

Successfully tested on Dell XPS 13 laptop with Core i7-1185G7 CPU (VMD
device ID 0x9a0b) and single NVMe SSD, dual-booting with Windows 10.

Successfully tested on Supermicro X11DPI-NT motherboard with Xeon(R)
Gold 6242R CPUs (VMD device ID 0x201d), simultaneously handling NVMe
SSD on one PCIe port and PLX bridge with 3 NVMe and 1 AHCI SSDs on
another.  Handles SSD hot-plug (except Optane 905p for some reason,
which are not detected until manual bus rescan) and enabled IOMMU
(directly connected SSDs work, but ones connected to the PLX fail
without errors from IOMMU).

MFC after:	2 weeks
Sponsored by:	iXsystems, Inc.
Differential revision:	https://reviews.freebsd.org/D31762





 - Re-implement pcib interface to use standard pci bus driver on top of
vmd(4) instead of custom one.
 - Re-implement memory/bus resource allocation to properly handle even
complicated configurations.
 - Re-implement interrupt handling to evenly distribute children's MSI/
MSI-X interrupts between available vmd(4) MSI-X vectors and setup them
to be handled by standard OS mechanisms with minimal overhead, except
sharing when unavoidable.

Successfully tested on Dell XPS 13 laptop with Core i7-1185G7 CPU (VMD
device ID 0x9a0b) and single NVMe SSD, dual-booting with Windows 10.

Successfully tested on Supermicro X11DPI-NT motherboard with Xeon(R)
Gold 6242R CPUs (VMD device ID 0x201d), simultaneously handling NVMe
SSD on one PCIe port and PLX bridge with 3 NVMe and 1 AHCI SSDs on
another.  Handles SSD hot-plug (except Optane 905p for some reason,
which are not detected until manual bus rescan) and enabled IOMMU
(directly connected SSDs work, but ones connected to the PLX fail
without errors from IOMMU).

MFC after:	2 weeks
Sponsored by:	iXsystems, Inc.
Differential revision:	https://reviews.freebsd.org/D31762