Lines Matching refs:space

57     - For DMA we then provide an entire address space for each PE that can
63     - For MSIs, we have two windows in the address space (one at the top of
64       the 32-bit space and one much higher) which, via a combination of the
75     from the CPU address space to the PCI address space.  There is one M32
78     the CPU address space to the PCIe bus and must be naturally aligned
89 	portion of address space from the CPU to PCIe
93 	ignores that however and will forward in that space if we try).
96 	maps each segment to a PE#.  That allows portions of the MMIO space
102     onto a segment alignment/granularity so that the space behind a bridge
127     for large BARs in 64-bit space:
129     We configure an M64 window to cover the entire region of address space
130     that has been assigned by FW for the PHB (about 64GB, ignore the space
139     - We do the PE# allocation *after* the 64-bit space has been assigned
170     PCI devices, but the BARs in VF config space headers are unusual.  For
171     a non-VF device, software uses BARs in the config space header to
174     discover sizes and assign addresses.  The BARs in the VF's config space
244                            VF(n) BAR space
253 		Figure 1.0 Direct map VF(n) BAR space
256   space doesn't need that much, as shown in Figure 1.1::
263                            VF(n) BAR space + extra
272 		Figure 1.1 Map VF(n) BAR space + extra
274   Allocating the extra space ensures that the entire M64 window will be
275   assigned to this one SR-IOV device and none of the space will be
276   available for other devices.  Note that this only expands the space
284 The PCIe SR-IOV spec requires that the base of the VF(n) BAR space be
294 of the VF(n) BAR space in the VF BAR.  If the PCI core allocates the exact
295 amount of space required for the VF(n) BAR space, the VF BAR value is fixed
298 On the other hand, if the PCI core allocates additional space, the VF BAR
299 value can be changed as long as the entire VF(n) BAR space remains inside
300 the space allocated by the core.
311 space will consume (numVFs * n) segments.  That means there aren't as many
312 available segments for adjusting base of the VF(n) BAR space.