[Solved] Is UEFI supposed to reserve AHCI memory regions?
Posted: Sun Apr 10, 2022 4:48 pm
Hi!
I see that an AHCI descriptor block's location is given by the corresponding PCI device's BAR. However, I do not see this same memory range being reserved in the UEFI memory map (in QEMU).
Since UEFI performs some initialization of SATA drives, I would have hoped that it would reserve the appropriate memory regions. I haven't found the documentation declaring whether this is UEFI's remit, but perhaps I've missed it in the UEFI spec.
If I am intended to preserve this memory region, I am concerned that I am clobbering other device's memory without realizing. I am also concerned that my driver might not come up fast enough to prevent this memory being handed out, though this seems like a theoretical worry only for the moment.
If anyone could shed info or insight, I would be grateful. Thanks!
I see that an AHCI descriptor block's location is given by the corresponding PCI device's BAR. However, I do not see this same memory range being reserved in the UEFI memory map (in QEMU).
Since UEFI performs some initialization of SATA drives, I would have hoped that it would reserve the appropriate memory regions. I haven't found the documentation declaring whether this is UEFI's remit, but perhaps I've missed it in the UEFI spec.
If I am intended to preserve this memory region, I am concerned that I am clobbering other device's memory without realizing. I am also concerned that my driver might not come up fast enough to prevent this memory being handed out, though this seems like a theoretical worry only for the moment.
If anyone could shed info or insight, I would be grateful. Thanks!