#
3f0289ea |
| 25-Oct-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
dmar: set acpi ivar domain on identify()
Reviewed by: jhb Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.fre
dmar: set acpi ivar domain on identify()
Reviewed by: jhb Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D47291
show more ...
|
#
d97838b7 |
| 03-Nov-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
iommu: eliminate iommu_free_ctx()
iommu_free_ctx_locked() alone is enough
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
705090cb |
| 22-Oct-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
DMAR: handle affinity for in-memory data structures
Reviewed and tested by: markj Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revis
DMAR: handle affinity for in-memory data structures
Reviewed and tested by: markj Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D47254
show more ...
|
#
b08d332d |
| 13-Oct-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
devices: report iommu data for the device in the dev. sysctl tree
Show the iommu unit' device name/unit which translates the device' requests, if any, as parsed out from the BIOS tables. Also show t
devices: report iommu data for the device in the dev. sysctl tree
Show the iommu unit' device name/unit which translates the device' requests, if any, as parsed out from the BIOS tables. Also show the rid value for the device.
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D47098
show more ...
|
#
c9e22c74 |
| 12-Oct-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
iommu: extract driver-independent ddb context and mapping reporting
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
e9d948cf |
| 12-Oct-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
iommu: move context link and ref count into device-independent parts
This also allows to move some bits of ddb print routines into iommu_utils.c common for x86 iommu drivers.
Sponsored by: Advanced
iommu: move context link and ref count into device-independent parts
This also allows to move some bits of ddb print routines into iommu_utils.c common for x86 iommu drivers.
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
show more ...
|
#
d50403a6 |
| 27-Sep-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
iommu: add per-unit sysctls reporting the state of DMA and interrupt remapping
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
Revision tags: release/13.4.0 |
|
#
ba33e74c |
| 27-Jul-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
busdma_iommu: indirect dmar-specific method calls in iommu_get_dev_ctx()
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
5967352a |
| 09-Jun-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
x86 iommu: move DMAR-independent parts of the interrupt setup code into common
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
fc8da73b |
| 09-Jun-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
x86 iommu x86_unit_common: expand hw completion write-out area to 8 bytes
in preparation to share it with AMD IOMMU. AMD writes out 8 bytes. We use 32-bit completion sequence numbers, and CPUs are l
x86 iommu x86_unit_common: expand hw completion write-out area to 8 bytes
in preparation to share it with AMD IOMMU. AMD writes out 8 bytes. We use 32-bit completion sequence numbers, and CPUs are little-endian. So the expansion is acceptable on Intel.
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
show more ...
|
#
ad794e6d |
| 06-Jun-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
x86 iommu: move DMAR-independent parts of the qi code into common
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
Revision tags: release/14.1.0 |
|
#
65b133e5 |
| 29-May-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
x86: allow to have more than one kind of IOMMU
Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
45543d34 |
| 20-Aug-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
DMAR: clear dmar_devs[unit] if attach failed
This should stop attempts to use a unit which was not completely initialized, but referenced by ACPI DMAR table during scoped devices operions.
PR: 2808
DMAR: clear dmar_devs[unit] if attach failed
This should stop attempts to use a unit which was not completely initialized, but referenced by ACPI DMAR table during scoped devices operions.
PR: 280817 Sponsored by: Advanced Micro Devices (AMD) Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D46382
show more ...
|
#
0875f3cd |
| 20-Aug-2024 |
Ed Maste <emaste@FreeBSD.org> |
Revert "x86: Enable Intel DMAR by default"
A number of people have reported panics with it enabled by default, possibly due to broken ACPI tables, which we do not handle well. D46382 is a potential
Revert "x86: Enable Intel DMAR by default"
A number of people have reported panics with it enabled by default, possibly due to broken ACPI tables, which we do not handle well. D46382 is a potential fix for this issue.
Additionally DMAR is currently not compatible with bhyve passthrough (see comment #10 in PR280817), with a draft patch to address that in D25672.
Revert to disabling DMAR by default pending the resolution of those two issues.
This reverts commit 3192fc30230ae432b80cca783abc2dbea9d3f383.
PR: 280817 Sponsored by: The FreeBSD Foundation
show more ...
|
Revision tags: release/13.3.0, release/14.0.0, release/13.2.0, release/12.4.0 |
|
#
3192fc30 |
| 30-Sep-2022 |
Ed Maste <emaste@FreeBSD.org> |
x86: Enable Intel DMAR by default
APIC ID 255 and above require x2APIC and DMAR interrupt remapping. FreeBSD is starting to be tested on high core count Intel systems that meet this criteria.
Revie
x86: Enable Intel DMAR by default
APIC ID 255 and above require x2APIC and DMAR interrupt remapping. FreeBSD is starting to be tested on high core count Intel systems that meet this criteria.
Reviewed by: kib, jhb Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D42435
show more ...
|
#
164fdee1 |
| 30-May-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
Intel DMAR: remove the 'dev' member
It duplicates iommu.dev, and was forgotten when struct iommu was split out from dmar.
Sponsored by: The FreeBSD Foundation Sponsored by: AMD dvanced Micro Device
Intel DMAR: remove the 'dev' member
It duplicates iommu.dev, and was forgotten when struct iommu was split out from dmar.
Sponsored by: The FreeBSD Foundation Sponsored by: AMD dvanced Micro Devices (AMD) MFC after: 1 week
show more ...
|
#
40d951bc |
| 25-May-2024 |
Konstantin Belousov <kib@FreeBSD.org> |
x86/iommu: extract useful utilities into x86_iommu.c
related to the page tables page allocation and mapping.
Sponsored by: The FreeBSD Foundation Sponsored by: Advanced Micro Devices (AMD) MFC afte
x86/iommu: extract useful utilities into x86_iommu.c
related to the page tables page allocation and mapping.
Sponsored by: The FreeBSD Foundation Sponsored by: Advanced Micro Devices (AMD) MFC after: 1 week
show more ...
|
#
24e38af6 |
| 23-Dec-2023 |
Konstantin Belousov <kib@FreeBSD.org> |
DMAR: add knob to disable RMRR entries installation into domains
Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
7153d5e4 |
| 15-Dec-2023 |
Konstantin Belousov <kib@FreeBSD.org> |
dmar(9): style, fix indent
Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
6afa2333 |
| 24-Dec-2023 |
Konstantin Belousov <kib@FreeBSD.org> |
iommu: remove leftover sys/cdefs.h includes
Sponsored by: The FreeBSD Foundation MFC after: 1 week
|
#
1587a9db |
| 29-Nov-2023 |
John Baldwin <jhb@FreeBSD.org> |
pci_cfgreg: Add a PCI domain argument to the low-level register API
This commit changes the API of pci_cfgreg(read|write) to add a domain argument (referred to as a segment in ACPI parlance) (note t
pci_cfgreg: Add a PCI domain argument to the low-level register API
This commit changes the API of pci_cfgreg(read|write) to add a domain argument (referred to as a segment in ACPI parlance) (note that this is not the same as a NUMA domain, but something PCI-specific). This does not yet enable access to domains other than 0, but updates the API to support domains.
Places that use hard-coded bus/slot/function addresses have been updated to hardcode a domain of 0. A few places that have the PCI domain (segment) available such as the acpi_pcib_acpi.c Host-PCI bridge driver pass the PCI domain.
The hpt27xx(4) and hptnr(4) drivers fail to attach to a device not on domain 0 since they provide APIs to their binary blobs that only permit bus/slot/function addressing.
The x86 non-ACPI PCI bus drivers all hardcode a domain of 0 as they do not support multiple domains.
Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D42827
show more ...
|
#
12cce599 |
| 17-Oct-2023 |
Zhenlei Huang <zlei@FreeBSD.org> |
x86: Prefer consistent naming for loader tunables
The following loader tunables do have corresponding sysctl MIBs but with inconsistent naming. That may be historical reason. Let's prefer consistent
x86: Prefer consistent naming for loader tunables
The following loader tunables do have corresponding sysctl MIBs but with inconsistent naming. That may be historical reason. Let's prefer consistent naming for them so that it will be easier to maintain.
1. hw.dmar.timeout -> hw.iommu.dmar.timeout 2. hw.lapic_eoi_suppression -> hw.apic.eoi_suppression 3. hw.lapic_tsc_deadline -> hw.apic.timer_tsc_deadline 4. hw.x2apic_enable -> hw.apic.x2apic_mode
Those tunables are for field debugging, no need to keep old names for compatibility.
Reviewed by: kib MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D42248
show more ...
|
#
685dc743 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
#
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
#
db0110a5 |
| 11-Jul-2022 |
Alan Cox <alc@FreeBSD.org> |
iommu: Shrink the iommu map entry structure
Eliminate the unroll_entry field from struct iommu_map_entry, shrinking the struct by 16 bytes on 64-bit architectures.
Reviewed by: kib MFC after: 2 wee
iommu: Shrink the iommu map entry structure
Eliminate the unroll_entry field from struct iommu_map_entry, shrinking the struct by 16 bytes on 64-bit architectures.
Reviewed by: kib MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D35769
show more ...
|