diff options
author | Laszlo Ersek <lersek@redhat.com> | 2015-01-02 12:04:15 +0000 |
---|---|---|
committer | lersek <lersek@Edk2> | 2015-01-02 12:04:15 +0000 |
commit | 6e2543b01d0cbd16b3fbcc6f12f6938d8c12bcc8 (patch) | |
tree | 015b36479f53e7ef98ab54de7989282959473a16 /BaseTools/Source/Python | |
parent | ad652d46941c6a1e0f828cb084fb6829c3abb68d (diff) | |
download | edk2-platforms-6e2543b01d0cbd16b3fbcc6f12f6938d8c12bcc8.tar.xz |
ArmVirtualizationPkg: introduce QemuFwCfgLib instance for DXE drivers
After reviewing OvmfPkg's use of its own QemuFwCfgLib instances, it is
clear that its only pre-DXE fw_cfg dependency concerns S3 support (the
QemuFwCfgS3Enabled() call in "PlatformPei/Platform.c").
For ARM guests, S3 is in the distant future, but we can see several
shorter term applications for fw_cfg that all reside in DXE:
- controlling boot order (to be implemented in PlatformBdsLib for Intel
BDS),
- supporting -kernel / -initrd / -append boot on QEMU (to be implemented
in PlatformBdsLib for Intel BDS, similarly),
- loading and linking ACPI tables,
- installing SMBIOS tables.
Therefore it makes sense to add a simple MMIO-based fw_cfg client library
to ArmVirtualizationPkg that for the moment is only available to
DXE_DRIVER modules.
Because MMIO accesses are costly on KVM/ARM, InternalQemuFwCfgReadBytes()
accesses the fw_cfg data register in full words. This speeds up transfers
almost linearly.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@16567 6f19259b-4bc3-4df7-8a09-765794883524
Diffstat (limited to 'BaseTools/Source/Python')
0 files changed, 0 insertions, 0 deletions