FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F14.3.0 2025-02-27T13:09:23Z 2025-02-27T13:09:23Z John Baldwin jhb@FreeBSD.org 2024-06-04T23:50:56Z urn:sha1:1c3996e87f09a5e67ebbd4e7e73a38848127c99e Some bus drivers use rmans to suballocate resources to child devices. When the driver for a child device requests a mapping for a suballocated resource, the bus driver translates this into a mapping request for a suitable subrange of the original resource the bus driver allocated from its parent. This nested mapping request should look like any other resource mapping request being made by the bus device (i.e. as if the bus device had called bus_map_resource() or bus_alloc_resource() with RF_ACTIVE). I had slightly flubbed this last bit though since the direct use of bus_generic_map/unmap_resource passed up the original child device (second argument to the underlying kobj interface). While this is currently harmless, it is not strictly correct as the resource being mapped is owned by the bus device, not the child and can break for other bus drivers in the future. Instead, use bus_map/unmap_resource for the nested request where the requesting device is now the bus device that owns the parent resource. Reviewed by: imp Fixes: 0e1246e33461 acpi: Cleanup handling of suballocated resources Fixes: b377ff8110e3 pcib: Refine handling of resources allocated from bridge windows Fixes: d79b6b8ec267 pci_host_generic: Don't rewrite resource start address for translation Fixes: d714e73f7895 vmd: Use bus_generic_rman_* for PCI bus and memory resources Differential Revision: https://reviews.freebsd.org/D45433 (cherry picked from commit 98056127ddfa36720bcf46edc09843c867784bcb) 2025-02-27T13:09:21Z John Baldwin jhb@FreeBSD.org 2024-02-15T20:26:40Z urn:sha1:e5936d602858378e649b49fdef8b909b3a20695b While here, add custom bus_map/unmap_resource methods to request mappings via the window memory resources allocated from the parent bus. Tested by: emaste Differential Revision: https://reviews.freebsd.org/D43886 (cherry picked from commit d714e73f789515963a22fe64417bf3883cdb599c) 2024-04-08T17:57:24Z John Baldwin jhb@FreeBSD.org 2024-02-15T20:26:19Z urn:sha1: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) 2024-01-25T06:44:55Z Gordon Bergling gbe@FreeBSD.org 2024-01-22T20:55:33Z urn:sha1:a499baff3955b9edacd56c44cf30386e26822e17 - s/harwdare/hardware/ (cherry picked from commit b2c48aa4d19268610191a0b7d7b76d01d28b0a13) 2023-08-16T17:54:36Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:36Z urn:sha1:685dc743dc3b5645e34836464128e1c0558b404b Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ 2023-08-16T17:54:11Z Warner Losh imp@FreeBSD.org 2023-08-16T17:54:11Z urn:sha1:95ee2897e98f5d444f26ed2334cc7c439f9c16c6 Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/ 2022-10-06T16:44:59Z Alexander Motin mav@FreeBSD.org 2022-10-06T16:44:59Z urn:sha1:9bce11410645f4e84521c2ee44d3082aad8ae1e9 MFC after: 2 weeks 2022-10-06T16:15:25Z Alexander Motin mav@FreeBSD.org 2022-10-06T16:15:25Z urn:sha1: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 2022-07-29T18:17:20Z Neel Chauhan nc@FreeBSD.org 2022-07-29T18:06:06Z urn:sha1: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 2022-05-06T22:46:59Z John Baldwin jhb@FreeBSD.org 2022-05-06T22:46:59Z urn:sha1:44031900628a72b330bd6616f1dda5bc57927983