Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [efi] Provide a multiprocessor API for EFI | Michael Brown | 2024-03-15 | 1 | -0/+1 |
| | | | | | | | | | | | | | Provide an implementation of the iPXE multiprocessor API for EFI, based on using EFI_MP_SERVICES to start up a wrapper function on all application processors. Note that the processor numbers used by EFI_MP_SERVICES are opaque integers that bear no relation to the underlying CPU identity (e.g. the APIC ID), and so we must rely on our own (architecture- specific) implementation to determine the relevant CPU identifiers. Signed-off-by: Michael Brown <mcb30@ipxe.org> | ||||
* | [mp] Define an API for multiprocessor functions | Michael Brown | 2024-03-15 | 1 | -0/+154 |
Define an API for executing very limited functions on application processors in a multiprocessor system, along with an x86-only implementation. The normal iPXE runtime environment is effectively non-existent on application processors. There is no ability to make firmware calls (e.g. to write to a console), and there may be no stack space available. Signed-off-by: Michael Brown <mcb30@ipxe.org> |