Re: [staging/apei]: New branch request for APEI work

[Laszlo Ersek <lersek@redhat.com>]

On 05/25/17 14:29, Achin Gupta wrote:
> Hi All,
> 
> I would like to create a branch for implementing support for APEI in EDK2. The
> intent is to upstream modules that are capable of creating the HEST, BERT, ERST
> and EINJ after gathering error and error source information from the platform
> and other sources. The work is still very nascent and the branch will be first
> populated with some workarounds. These will be used as the basis for further
> development.
> 
> Could you please do the needful. The attached readme has been populated with
> some basic information.

(

Side remark:

For running the ArmVirtQemu edk2 platform on QEMU at least, the approach
being taken is to generate all APEI related stuff in QEMU, and to keep
the virtual firmware fully un-enlightened about APEI. This is consistent
with how QEMU and ArmVirtQemu handle other ACPI tables, through the QEMU
linker/loader interface.

References to sub-threads:

http://mid.mail-archive.com/5b7352f4-4965-3ed5-3879-db871797be47@huawei.com

http://mid.mail-archive.com/1493530506-26833-1-git-send-email-gengdongjiu@huawei.com

This is not to say that I "oppose" the branch -- that would make zero
sense, as physical platforms need to create their APEI-related tables in
their firmwares, like they create all other ACPI tables. I'd just like
to highlight that with QEMU (hence with ArmVirtQemu and OVMF), all
hardware-related ACPI tables are generated on the QEMU side, and that
the APEI tables should be no different. In fact this closely matches
Achin's virt-oriented design, visible in the first above-referenced thread.

)

Thanks
Laszlo