Skip to content

[CHERRY-PICK]MdeModulePkg: Add platform limit for size in Resizable BAR#1807

Open
AnirudhSrinivasula wants to merge 1 commit into
microsoft:release/202511from
AnirudhSrinivasula:release/cherry-pick
Open

[CHERRY-PICK]MdeModulePkg: Add platform limit for size in Resizable BAR#1807
AnirudhSrinivasula wants to merge 1 commit into
microsoft:release/202511from
AnirudhSrinivasula:release/cherry-pick

Conversation

@AnirudhSrinivasula
Copy link
Copy Markdown

Resizable BAR driver selects max available BAR size to configure for use. It may happen that some PCIe device declare support for size that exceeds processor address width. Platform needs a way to define the max size it can accept. This change introduce PCD called PcdPcieResizableBarMaxSize. It is dynamic PCD where platform can provide its limit for BAR size. Such PCD can be also controlled with a configuration knob.

(cherry picked from commit 24eddc65b34538b397bcacec057a4a1fff7550df)

Description

Added the PcdPcieResizableBarMaxSize PCD

For details on how to complete these options and their meaning refer to CONTRIBUTING.md.

  • Impacts functionality?
  • Impacts security?
  • Breaking change?
  • Includes tests?
  • Includes documentation?

How This Was Tested

It was integreated in new intel Latest BKC

Integration Instructions

<Describe how these changes should be integrated. Use N/A if nothing is required.>
NA

Resizable BAR driver selects max available BAR size to configure for use.
It may happen that some PCIe device declare support for size that exceeds
processor address width. Platform needs a way to define the max size it
can accept. This change introduce PCD called PcdPcieResizableBarMaxSize.
It is dynamic PCD where platform can provide its limit for BAR size.
Such PCD can be also controlled with a configuration knob.

Signed-off-by: Jacek Kolakowski <Jacek.Kolakowski@intel.com>
(cherry picked from commit 24eddc6)
@mu-automation
Copy link
Copy Markdown
Contributor

mu-automation Bot commented May 25, 2026

⌛ QEMU Validation Pending

QEMU validation is pending on successful CI completion.

Note: Any previous results are available in this comment's edit history.

This comment was automatically generated by the Mu QEMU PR Validation workflow.

@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented May 25, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release/202511@5adc5a4). Learn more about missing BASE report.

Additional details and impacted files
@@                Coverage Diff                @@
##             release/202511    #1807   +/-   ##
=================================================
  Coverage                  ?    2.26%           
=================================================
  Files                     ?      517           
  Lines                     ?   144257           
  Branches                  ?     2776           
=================================================
  Hits                      ?     3264           
  Misses                    ?   140952           
  Partials                  ?       41           
Flag Coverage Δ
FmpDevicePkg 9.53% <ø> (?)
NetworkPkg 0.55% <ø> (?)
PolicyServicePkg 30.42% <ø> (?)
SecurityPkg 1.59% <ø> (?)
UefiCpuPkg 4.78% <ø> (?)
UnitTestFrameworkPkg 11.70% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants