Hi, Looking at the hardcoded limitation provided by PcdPciMmio64Size (32GiB), I was wondering what would be the best approach to make this a bit more dynamic?
I know that for QEMU, the fw_cfg mechanism can be used to override the value of PcdPciMmio64Size, but this isn't something Cloud Hypervisor or other VMMs can implement given they don't support fw_cfg at all. Would it be acceptable to dynamically compute PcdPciMmio64Size from the physical address space? Given the reason why PcdPciMmio64Size can't be increased is to make sure it can support host with small address space (such as 36 bits), we could introduce a very simple function that would determine the available address space and consider PcdPciMmio64Size being half the size. I'm not sure if PcdPciMmio64Size should still be provided or not, as a default value to fallback on. Please let me know your thoughts on this and I can start preparing a patch. Thanks, Sebastien --------------------------------------------------------------------- Intel Corporation SAS (French simplified joint stock company) Registered headquarters: "Les Montalets"- 2, rue de Paris, 92196 Meudon Cedex, France Registration Number: 302 456 199 R.C.S. NANTERRE Capital: 5 208 026.16 Euros This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#98695): https://edk2.groups.io/g/devel/message/98695 Mute This Topic: https://groups.io/mt/96330209/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
