Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ACPI APEI requirements for RAS #31

Open
andreiw opened this issue Jan 23, 2025 · 0 comments
Open

ACPI APEI requirements for RAS #31

andreiw opened this issue Jan 23, 2025 · 0 comments

Comments

@andreiw
Copy link
Collaborator

andreiw commented Jan 23, 2025

The original draft of the BRS document (https://docs.google.com/document/d/1X0TSbheEJjRGWhG2nzUnfIl_QcHWSuvd/edit, section 9.3) had this:

For the ACPI Platform Error Interface (APEI):

  • One event for non-fatal error signaling [ACPI § 18.3.2.7.2]
  • XXX NMI-equivalent signal for use in fatal errors.

...which mirrored the BBR text. None of this made the BRS since RAS was a stretch as was considered out of scope.

We now have the SDEI-equivalent SSE for the NMI and RAS is definitely not a stretch or out of scope for a server :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant