Issues observed when small (<4k) BARs are not 4k aligned are:
1. Devices to be passed through (to e.g. a Xen HVM guest) with small
(<4k) BARs require each memory BAR to be page aligned. Currently, the
only way to guarantee this alignment from a user perspective is to fake
the size of the BARs using the pci=resource_alignment= option. This is a
bad user experience, and faking the BAR size is not always desirable.
For example, pcitest is a tool that is useful for PCI passthrough
validation with Xen, but pcitest fails with a fake BAR size.
2. Devices with multiple small (<4k) BARs could have the MSI-X tables
located in one of its small (<4k) BARs. This may lead to the MSI-X
tables being mapped in the same 4k region as other data. The PCIe 6.1
specification (section 7.7.2 MSI-X Capability and Table Structure) says
we probably shouldn't do that.
To improve the user experience (i.e. don't require the user to specify
pci=resource_alignment=), and increase conformance to PCIe spec, set the
default minimum resource alignment of memory BARs to the greater of 4k
or PAGE_SIZE.
Quoting the comment in
drivers/pci/pci.c:pci_request_resource_alignment(), there are two ways
we can increase the resource alignment:
1) Increase the size of the resource. BARs are aligned on their
size, so when we reallocate space for this resource, we'll
allocate it with the larger alignment. This also prevents
assignment of any other BARs inside the alignment region, so
if we're requesting page alignment, this means no other BARs
will share the page.
The disadvantage is that this makes the resource larger than
the hardware BAR, which may break drivers that compute things
based on the resource size, e.g., to find registers at a
fixed offset before the end of the BAR.
2) Retain the resource size, but use IORESOURCE_STARTALIGN and
set r->start to the desired alignment. By itself this
doesn't prevent other BARs being put inside the alignment
region, but if we realign *every* resource of every device in
the system, none of them will share an alignment region.
When the user has requested alignment for only some devices via
the "pci=resource_alignment" argument, "resize" is true and we
use the first method. Otherwise we assume we're aligning all
devices and we use the second.
Changing pcibios_default_alignment() results in the second method of
alignment with IORESOURCE_STARTALIGN.
The new default alignment may be overridden by arches by implementing
pcibios_default_alignment(), or by the user on a per-device basis with
the pci=resource_alignment= option (although this reverts to using
IORESOURCE_SIZEALIGN).
Signed-off-by: Stewart Hildebrand <stewart.hildebrand@xxxxxxx>
---
Preparatory patches in this series are prerequisites to this patch.
v1->v2:
* capitalize subject text
* s/4 * 1024/SZ_4K/
* #include <linux/sizes.h>
* update commit message
* use max(SZ_4K, PAGE_SIZE) for alignment value
---
drivers/pci/pci.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 6df318beff37..6b85a204ec4e 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -31,6 +31,7 @@
#include <asm/dma.h>
#include <linux/aer.h>
#include <linux/bitfield.h>
+#include <linux/sizes.h>
#include "pci.h"
DEFINE_MUTEX(pci_slot_mutex);
@@ -6485,7 +6486,12 @@ struct pci_dev __weak *pci_real_dma_dev(struct pci_dev *dev)
resource_size_t __weak pcibios_default_alignment(void)
{
- return 0;
+ /*
+ * Avoid MSI-X tables being mapped in the same 4k region as other data
+ * according to PCIe 6.1 specification section 7.7.2 MSI-X Capability
+ * and Table Structure.
+ */
+ return max(SZ_4K, PAGE_SIZE);
}
/*
--
2.45.2
