Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APCB configuration should support 1 TiB RAM #51

Open
wesolows opened this issue Feb 27, 2023 · 1 comment
Open

APCB configuration should support 1 TiB RAM #51

wesolows opened this issue Feb 27, 2023 · 1 comment
Assignees
Milestone

Comments

@wesolows
Copy link
Contributor

There are a handful of configuration parameters that need to be set in the APCB to support the full 1 TiB of RAM on machines that have it. There is a 12 GiB region of physical address space immediately below 0x100_0000_0000 that is used in some very poorly specified manner by the IOMMU, possibly even if it's disabled. It is possible, at least sometimes, to remap the DRAM that would otherwise land in this region above that hole, just as is done for the normal MMIO hole below 4 GiB. The AMD AGESA manual explains the tokens that are involved and the limitations (which depend in turn on DRAM interleave settings). We should make sure that we're at least trying to do this remapping; if we also have to change interleave settings to make it work, we will need to do a performance evaluation to see whether it's better for the customer to lose 12 GiB of DRAM or use a suboptimal interleave.

@wesolows wesolows added this to the MVP+1 milestone Feb 27, 2023
@dancrossnyc dancrossnyc assigned dancrossnyc and daym and unassigned dancrossnyc May 1, 2023
daym pushed a commit that referenced this issue May 9, 2023
#51 APCB configuration should support 1 TiB RAM
daym pushed a commit that referenced this issue May 9, 2023
#51 APCB configuration should support 1 TiB RAM
@wesolows wesolows modified the milestones: MVP+1, MVP Aug 29, 2023
@wesolows
Copy link
Contributor Author

I've moved this to MVP, as MVP+1 no longer makes sense given the decision to ship something nonviable.

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

No branches or pull requests

3 participants