许海波-Linux RISC-V ACPI support.pdf

1、Linux RISC-V ACPI Support Where We AreHaibo XuRISC-V Software EngineerIntel Confidential2Legal Notices and DisclaimersStatements in this document that refer to future plans or expectations are forward-looking statements.These statements are based on current expectations and involve many risks and un

2、certainties that could cause actual results to differ materially from those expressed or implied in such statements.For more information on the factors that could cause actual results to differ materially,see our most recent earnings release and SEC filings at .All product plans and roadmaps are sub

3、ject to change without notice.Any forecasts of goods and services needed for Intels operations are provided for discussion purposes only.Intel will have no liability to make any purchase in connection with forecasts published in this document.Code names are often used by Intel to identify products,t

4、echnologies,or services that are in development and usage may change over time.No license(express or implied,by estoppel or otherwise)to any intellectual property rights is granted by this document.Intel Corporation.Intel,the Intel logo,and other Intel marks are trademarks of Intel Corporation or it

5、s subsidiaries.Other names and brands may be claimed as the property of others.This document contains information on products and/or processes in development.Intel Confidential3Agenda RISC-V ACPI Why is required ACPI-Recap RISC-V ACPI Which tables are needed Linux RISC-V ACPI Status RISC-V ACPI Plan

6、Intel Confidential4RISC-V ACPI Why is required A unified interface between a platform and an OS is important Allows the platform to encode hardware behavior by AML Well established bindings(RAS)in the industry Mature ecosystems for both HW and OS vendor on x86/Arm ACPI is require