VirtualBox

Ignore:
Timestamp:
Apr 13, 2021 5:50:44 AM (4 years ago)
Author:
vboxsync
Message:

Intel IOMMU: bugref:9967 Main: Use the same I/O APIC PCI address reservation as we do on AMD, as it keeps things simpler than moving PCI devices/slots around again.
Also for now don't opt out of x2APIC (seems Linux VMs are configured with x2APIC by default, so let's try get things working with x2APIC).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/VBox/Main/src-client/BusAssignmentManager.cpp

    r88333 r88484  
    255255 * Intel IOMMU.
    256256 * The VT-d misc, address remapping, system management device is
    257  * located at BDF 00:5:0 on real hardware so we mimick the same.
    258  * LSI logic remains at 0:20:0.
     257 * located at BDF 0:5:0 on real hardware but we use 0:1:0 since that
     258 * slot isn't used for anything else.
     259 *
     260 * While we could place the I/O APIC anywhere, we keep it consistent
     261 * with the AMD IOMMU and we assign the LSI Logic controller to
     262 * device number 23 (and I/O APIC at device 20).
    259263 */
    260264static const DeviceAssignmentRule g_aIch9IommuIntelRules[] =
    261265{
    262266    /* Intel IOMMU. */
    263     {"iommu-intel",   0,  5,  0, 0},
     267    {"iommu-intel",   0,  1,  0, 0},
     268    /* Intel IOMMU: Reserved for I/O APIC. */
     269    {"sb-ioapic",     0, 20,  0, 0},
    264270
    265271    /* Storage controller */
    266     {"lsilogic",      0, 20,  0, 1},
     272    {"lsilogic",      0, 23,  0, 1},
    267273    { NULL,          -1, -1, -1, 0}
    268274};
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette