<feed xmlns='http://www.w3.org/2005/Atom'>
<title>Tianocore/edk2.git/MdeModulePkg/Bus, branch dependabot/github_actions/github/codeql-action-4.39.3</title>
<subtitle>EDK II (mirror)</subtitle>
<id>https://git.radix-linux.su/Tianocore/edk2.git/atom?h=dependabot%2Fgithub_actions%2Fgithub%2Fcodeql-action-4.39.3</id>
<link rel='self' href='https://git.radix-linux.su/Tianocore/edk2.git/atom?h=dependabot%2Fgithub_actions%2Fgithub%2Fcodeql-action-4.39.3'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/'/>
<updated>2026-11-05T04:06:27+00:00</updated>
<entry>
<title>Revert "MdeModulePkg/PciBusDxe: Preserve physical BAR numbering"</title>
<updated>2026-11-05T04:06:27+00:00</updated>
<author>
<name>Aaron Pop</name>
<email>aaronpop@microsoft.com</email>
</author>
<published>2026-10-23T22:34:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=087a07536de8b8561c7ae5ed974e60c80a9ed4ae'/>
<id>urn:sha1:087a07536de8b8561c7ae5ed974e60c80a9ed4ae</id>
<content type='text'>
This reverts commit 0e7dad44bae663193b580adeb9d942c2559166f6.

Signed-off-by: Aaron Pop &lt;aaronpop@microsoft.com&gt;
</content>
</entry>
<entry>
<title>Revert "MdeModulePkg/PciBusDxe: Add Google Tests for BAR parsing"</title>
<updated>2026-11-05T04:06:27+00:00</updated>
<author>
<name>Aaron Pop</name>
<email>aaronpop@microsoft.com</email>
</author>
<published>2026-10-23T22:31:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=f4e2af190443b116a327ba017f8b2612b01fbb08'/>
<id>urn:sha1:f4e2af190443b116a327ba017f8b2612b01fbb08</id>
<content type='text'>
This reverts commit 0d61209231b2ec50ca6f6b96825baaa07c280854.

Signed-off-by: Aaron Pop &lt;aaronpop@microsoft.com&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciBusDxe: Honour fixed bus numbers of EA bridges</title>
<updated>2026-10-27T11:59:48+00:00</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2026-09-24T15:32:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=447c415c2678a2bab107d5d529b879e3d7713830'/>
<id>urn:sha1:447c415c2678a2bab107d5d529b879e3d7713830</id>
<content type='text'>
The Enhanced Allocation capability of a PCI-PCI bridge carries an
additional DWORD describing the fixed secondary and subordinate bus
numbers used by the bridge, if it does not rely on its bus number
registers. Such a bridge only forwards configuration transactions for
its fixed bus numbers, and so they must be assigned to it during bus
enumeration.

Record the fixed bus numbers when parsing the EA capability, and assign
them in PciScanBus () instead of allocating the next available bus
number. The buses below the bridge are numbered from its fixed secondary
bus number onwards, and the entire fixed range is consumed, regardless
of how many buses are actually in use below the bridge. Hot plug bus
padding does not apply to such bridges.

As bus numbers are assigned in ascending order, the fixed bus numbers
cannot be honoured if they have already been assigned to another
bridge, if they are not covered by a single bus number range of the root
bridge, or if they are not nested inside the fixed bus numbers of an
upstream bridge. In this case, do not scan behind the bridge, and set
its primary bus number to an invalid value, so that the device info
collector pass does not scan behind it either: its bus number registers
are likely hardwired, and so the hierarchy behind it may remain visible
on buses that are assigned to other bridges.

Report an error if buses below a bridge with fixed bus numbers end up
outside of its fixed range, as those will be unreachable.

Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciBusDxe: Support EA fixed bridge windows</title>
<updated>2026-10-27T11:59:48+00:00</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2026-09-24T14:41:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=c6ee316435166b74d98b6a72edf916dc2f7f327a'/>
<id>urn:sha1:c6ee316435166b74d98b6a72edf916dc2f7f327a</id>
<content type='text'>
A PCI-PCI bridge that implements the Enhanced Allocation (EA) capability
may use entries with BEI 6 to describe fixed I/O, memory and prefetchable
memory ranges that it forwards to its secondary side, regardless of the
contents of its Base/Limit registers.

So record such windows when parsing the EA capability of a bridge, and
treat the corresponding decodes as supported so that resources are not
degraded to a different type on account of the Base/Limit registers not
being implemented.

When calculating the aperture of such a bridge window, pin it to the fixed
range. Fixed resources below the bridge must reside inside that range, and
are dropped otherwise. Relocatable resources are placed inside the range at
the offsets calculated for them, provided that the window does not hold any
fixed resources, and is large enough, suitably aligned and, if it resides
above 4 GB, only covers resources that may be placed above 4 GB. Otherwise,
they are dropped.

Pinned EA windows are not programmed into the Base/Limit registers, and
propagate upwards as fixed resources, like any other pinned bridge window.

The on-chip bridges of some SoCs (e.g., Cavium/Marvell ThunderX family)
implement the EA capability only to describe their fixed bus numbers, and
carry no BEI 6 entries at all. The fixed BARs below such bridges are 64-bit
non-prefetchable ranges above 4 GB, and those below different bridges are
interleaved, as each device has BARs in multiple distinct regions. Covering
them with pinned windows does not work: the 32-bit non-prefetchable window
cannot describe them, and the pinned windows of sibling bridges overlap.
Evidently, such bridges forward the fixed ranges below them regardless of
their Base/Limit registers.

So assume that a bridge that implements the EA capability but has no BEI 6
entry for a certain type of window passes through the fixed resources of
that type below it: move them to the resource nodes of the upstream bus,
restoring the original BAR type of fixed device resources, and leave the
bridge window to the relocatable resources below it, if any. Bridges that
do not implement the EA capability are unaffected.

Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciBusDxe: Submit fixed ranges to the host bridge</title>
<updated>2026-10-27T11:59:48+00:00</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2026-09-24T14:32:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=f531283dee7df7e6a53f17704be217fb5f7096ce'/>
<id>urn:sha1:f531283dee7df7e6a53f17704be217fb5f7096ce</id>
<content type='text'>
After submitting the resource requirements for a root bridge, pass the
fixed ranges below it to the host bridge driver via the EDKII PCI Host
Bridge Fixed Resource protocol, if it is implemented. These are the fixed
BARs of devices on the root bus, and the pinned windows of PCI-PCI bridges
that cover fixed BARs further down the hierarchy.

If the protocol is not implemented, log the fixed ranges, as they need to
be reserved by the platform in that case.

Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciHostBridgeDxe: Implement the Fixed Resource protocol</title>
<updated>2026-10-27T11:59:48+00:00</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2026-09-24T14:32:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=c91bedce833efc472ac78ac5cfd7866a86576141'/>
<id>urn:sha1:c91bedce833efc472ac78ac5cfd7866a86576141</id>
<content type='text'>
Implement the EDKII PCI Host Bridge Fixed Resource protocol, and install
it alongside the resource allocation protocol.

Fixed ranges submitted for a root bridge are validated against its
apertures, and claimed in GCD at their host address before any of the
root bridge windows are allocated, so that the allocator will steer clear
of them. Failure to claim a range is not treated as an error, given that
the platform may have reserved it already. The claimed ranges are released
again when the resources are freed or the enumeration is restarted.

The fixed ranges are appended to the resource descriptors returned by the
root bridge's Configuration () method, which permits the PCI bus driver to
resolve the translation offset for BARs that decode a fixed range.

Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciBusDxe: Honour fixed BARs in the resource allocator</title>
<updated>2026-10-27T11:59:48+00:00</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2026-09-24T14:32:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=fe00f5464caa773d578426307980f869b0f011a3'/>
<id>urn:sha1:fe00f5464caa773d578426307980f869b0f011a3</id>
<content type='text'>
BARs described by an Enhanced Allocation capability decode a fixed address
range, and so they must be excluded from the ordinary resource allocation,
which assigns relocatable ranges by packing BARs at offsets from the base
of the enclosing window.

So represent such BARs as fixed resource nodes, which are not taken into
account when calculating the size of the enclosing window, and which are
not programmed into the BAR registers.

A PCI-PCI bridge window that covers fixed resource nodes must itself be
pinned to a range that covers all of them. Relocatable resources of the
same type below such a bridge cannot be accommodated, and are dropped with
an error. The pinned windows are programmed before the rest of the
hierarchy, and are propagated upwards as fixed nodes.

Finally, permit PciIo to fall back to a translation offset of 0 for fixed
BARs that are not covered by any of the root bridge's resource windows,
given that the platform may have reserved these ranges by other means.

Fixed resources don't occupy any of the relocatable aperture of the
enclosing window, and so a window or root bridge resource pool that only
holds fixed resources does not request any resources. So don't submit a
resource request for it, and don't treat the absence of an allocated base
as an error when programming the resources below it. This is the case,
e.g., for root bridges whose devices only have fixed BARs.

Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciBusDxe: Parse the Enhanced Allocation capability</title>
<updated>2026-10-27T11:59:48+00:00</updated>
<author>
<name>Ard Biesheuvel</name>
<email>ardb@kernel.org</email>
</author>
<published>2026-09-24T14:31:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=d293b1e9d9051def25e0fa7b6eb17fa8601f38d4'/>
<id>urn:sha1:d293b1e9d9051def25e0fa7b6eb17fa8601f38d4</id>
<content type='text'>
Devices that implement the PCI Enhanced Allocation (EA) capability may
have BARs that are hardwired to a fixed address range, and that cannot be
sized or relocated via the ordinary BAR registers.

So when gathering device and PCI-PCI bridge information, parse the EA
capability if it exists, and use each enabled entry for BEI 0-5 (0-1 for
bridges) to override the information obtained from the corresponding BAR:
record the fixed base address and size, and mark the BAR as having a fixed
address, so that the resource allocator can take this into account.

Do the same after resizable BARs have been adjusted, as this re-parses the
BAR registers, and ensure that UpdatePciInfo () leaves such BARs alone.

Signed-off-by: Ard Biesheuvel &lt;ardb@kernel.org&gt;
</content>
</entry>
<entry>
<title>MdeModulePkg/PciBusDxe: Avoid redundant PCI register and bridge accesses</title>
<updated>2026-10-26T20:45:42+00:00</updated>
<author>
<name>Kevin Loughlin</name>
<email>kevinloughlin@google.com</email>
</author>
<published>2026-10-21T15:31:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=520f764655158e70ea7d165aec315ad653e8b41f'/>
<id>urn:sha1:520f764655158e70ea7d165aec315ad653e8b41f</id>
<content type='text'>
Currently, PciOperateRegister() unconditionally writes to the target PCI
configuration register (Command or Bridge Control) on
EFI_ENABLE_REGISTER and EFI_DISABLE_REGISTER operations even when the
requested bits are already in the target state or when Command is 0.

Similarly, PciIoAttributes() unconditionally invokes
PCI_ENABLE_COMMAND_REGISTER() and PCI_DISABLE_COMMAND_REGISTER() even
when Command is 0 (unlike BridgeControl, which is guarded by
BridgeControl != 0), and unconditionally recurses into
UpStreamBridge-&gt;PciIo.Attributes() even when UpStreamAttributes is 0
(such as when enabling IO, MEMORY, or BUS_MASTER on an endpoint).

Under virtualization (especially confidential computing environments
such as AMD SEV-SNP and Intel TDX), every PCI configuration space read
or write traps to the hypervisor. Update PciOperateRegister() to skip
no-op register reads/writes when Command is 0 or when the register value
is unchanged, and update PciIoAttributes() to guard Command register
updates and upstream bridge recursion on non-zero masks.

Suggested-by: Ard Biesheuvel &lt;ardb+tianocore@kernel.org&gt;
Signed-off-by: Kevin Loughlin &lt;kevinloughlin@google.com&gt;
</content>
</entry>
<entry>
<title>MdePkg,MdeModulePkg: Introduce Enter4Byte/Exit4Byte In SpiNorFlashJedecSfdp</title>
<updated>2026-10-23T18:55:11+00:00</updated>
<author>
<name>Vincent Ke</name>
<email>vincentke@ami.com</email>
</author>
<published>2026-10-02T07:54:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/Tianocore/edk2.git/commit/?id=3c890c11dfdb5908dcbc84f977dddc6c6d43789f'/>
<id>urn:sha1:3c890c11dfdb5908dcbc84f977dddc6c6d43789f</id>
<content type='text'>
Follow JESD216H 6.4.19, DWORD 16
Introduce Enter4Byte/Exit4Byte In SpiNorFlashJedecSfdp And SpiNorFlash
Fixes: #13171

Continuous-integration-options: PatchCheck.ignore-multi-package
Signed-off-by: Vincent Ke &lt;vincentke@ami.com&gt;
</content>
</entry>
</feed>
