You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ES/README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ This section contains the build scripts and the live-images for the SystemReady
34
34
- The prebuilt images are archived after compression to the .xz format. On Linux, use the xz utility to uncompress the image `xz -d es_acs_live_image.img.xz`. On Windows, use the 7zip or a similar utility.
35
35
- If you choose to use the prebuilt image, skip the build steps, and navigate to the "Verification" section below.
36
36
37
+
Note: The latest pre-built image contains Linux kernel version 5.13. To build a image with a different Linux kernel version, update the `LINUX_KERNEL_VERSION` in the configuration file `<path to arm-systemready>/common/config/common_config.cfg` before the build (after step 3 below). To see the list of kernel versions for which Linux BSA patches are available, see the [folder](https://gitlab.arm.com/linux-arm/linux-acs/-/tree/master/kernel/src)
38
+
37
39
### Prerequisites
38
40
Before starting the ACS build, ensure that the following requirements are met:
39
41
- Ubuntu 18.04 or 20.04 LTS with at least 32GB of free disk space.
@@ -153,5 +155,5 @@ System Ready ACS is distributed under Apache v2.0 License.
153
155
154
156
--------------
155
157
156
-
*Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.*
158
+
*Copyright (c) 2021-2022, Arm Limited and Contributors. All rights reserved.*
Copy file name to clipboardExpand all lines: IR/README.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,8 @@ This section of the repository contains the build scripts and the live-images fo
34
34
- The prebuilt images are archived after compression to the .xz format. On Linux, use the xz utility to uncompress the image `xz -d es_acs_live_image.img.xz`. On Windows, use the 7zip or a similar utility.
35
35
- If you choose to use the prebuilt image, skip the build steps, and navigate to the "Verification" section below.
36
36
37
+
Note: The latest pre-built image contains Linux kernel version 5.13. To build a image with a different Linux kernel version, update the `LINUX_KERNEL_VERSION` in the configuration file `<path to arm-systemready>/common/config/common_config.cfg` before the build (after step 3 below). To see the list of kernel versions for which Linux BSA patches are available, see the [folder](https://gitlab.arm.com/linux-arm/linux-acs/-/tree/master/kernel/src)
38
+
37
39
### Prerequisites
38
40
Before starting the ACS build, ensure that the following requirements are met:
39
41
- Ubuntu 18.04 or 20.04 LTS with at least 32GB of free disk space.
@@ -138,5 +140,5 @@ System Ready ACS is distributed under Apache v2.0 License.
138
140
139
141
--------------
140
142
141
-
*Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.*
143
+
*Copyright (c) 2021-2022, Arm Limited and Contributors. All rights reserved.*
Copy file name to clipboardExpand all lines: README.md
+30-7Lines changed: 30 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
## Introduction to Arm SystemReady
4
4
Systems that are designed to just work for the end user with the ability to install and run generic, off-the-shelf operating systems out of the box, must follow a set of minimum hardware and firmware requirements.
5
5
6
-
For the Arm ecosystem, this requirement first surfaced in the server segment. The Arm ServerReady compliance certification program provides this “just works” solution for servers, allowing you to deploy Arm servers with confidence. The program is based on industry standards and is accompanied by a compliance test suite, and a process for certification.
6
+
For the Arm ecosystem, this requirement first surfaced in the server segment. The Arm ServerReady compliance certification program provides this 'just works' solution for servers, allowing you to deploy Arm servers with confidence. The program is based on industry standards and is accompanied by a compliance test suite, and a process for certification.
7
7
8
8
The Arm SystemReady program is a natural extension of the Arm ServerReady program. Different market segments may target different sets of operating systems and hypervisors with different hardware and firmware requirements. We use the term band to identify these differences, with a shorthand notation for each band. The bands are:
@@ -13,15 +13,16 @@ The Arm SystemReady program is a natural extension of the Arm ServerReady progra
13
13
14
14
For more information, visit: [Arm SystemReady](https://developer.arm.com/architectures/system-architectures/arm-systemready)
15
15
16
-
This repository contains the infrastructure to build the Architecture Compliance Suite and the bootable prebuilt images to be used for the certifications of various bands of SystemReady.
17
-
Note: Currently SystemReady ESand IR bands are supported in this repository
16
+
This repository contains the infrastructure to build the Architecture Compliance Suite (ACS) and the bootable prebuilt images to be used for the certifications of various bands of SystemReady.<br />
17
+
Note: Currently SystemReady ES, IR and SR bands are supported in this repository
18
18
19
-
For SystemReady SR, refer to the [Arm Enterprise ACS repository](https://github.com/ARM-software/arm-enterprise-acs)
19
+
For the legacy SystemReady SR ACS, refer to the [Arm Enterprise ACS repository](https://github.com/ARM-software/arm-enterprise-acs)
20
20
21
-
## System Ready bands:
22
-
Navigate to the ESor IR band for further details on specific scripts and prebuilt images, through the directories below:
21
+
## SystemReady bands:
22
+
Navigate to the ES, IR, or SR band for further details on specific scripts and prebuilt images through the directories below:
23
23
*[ES](./ES)
24
24
*[IR](./IR)
25
+
*[SR](./SR)
25
26
26
27
## SystemReady Security Interface Extension:
27
28
The SystemReady Security Interface Extension certifies that firmware meets the requirements specified by the Arm [Base Boot Security Requirements specification](https://developer.arm.com/documentation/den0107/latest) (BBSR). The Security Interface Extension is optionally applicable to SystemReady SR, ES and IR bands, but not the LS band.
@@ -30,11 +31,33 @@ Further details on Security Interface Extension, including pre-built images, are
30
31
31
32
## Limitations
32
33
34
+
### BSA
33
35
Validating the compliance of certain PCIe rules defined in the BSA specification require the PCIe end-point generate specific stimulus during the runtime of the test. Examples of such stimulus are P2P, PASID, ATC, etc. The tests that requires these stimuli are grouped together in the exerciser module. The exerciser layer is an abstraction layer that enables the integration of hardware capable of generating such stimuli to the test framework.
34
36
The details of the hardware or Verification IP which enable these exerciser tests platform specific and are beyond the scope of this document.
35
37
36
38
The Live image does not allow customizations, hence, the exerciser module is not included in the Live image. To enable exerciser tests for greater coverage of PCIe rules, please refer to [BSA](https://github.com/ARM-software/bsa-acs) Or contact your Arm representative for details.
37
39
40
+
### SBSA
41
+
Validating the compliance of certain PCIe rules defined in the SBSA specification requires the PCIe end-point to generate specific stimulus during the runtime of the test. Examples of such stimulus are P2P, PASID, ATC, etc. The tests that requires these stimuli are grouped together in the exerciser module. The exerciser layer is an abstraction layer that enables the integration of hardware capable of generating such stimuli to the test framework.
42
+
The details of the hardware or Verification IP which enable these exerciser tests are platform specific and are beyond the scope of this document.
43
+
44
+
- Some PCIe and Exerciser test are dependent on PCIe features supported by the test system.
45
+
Please fill the required API's with test system information.
|pal_pcie_p2p_support |Return 0 if the test system PCIe supports peer to peer transaction, else 1 |453, 454, 456, 812, 813 |
50
+
|pal_pcie_is_cache_present |Return 1 if the test system supports PCIe address translation cache, else 0 |452 |
51
+
|pal_pcie_get_legacy_irq_map |Return 0 if system legacy irq map is filled, else 1 |412, 450, 806 |
52
+
53
+
Below exerciser capabilities are required by exerciser test.
54
+
- MSI-X interrupt generation.
55
+
- Incoming Transaction Monitoring(order, type).
56
+
- Initiating transacions from and to the exerciser.
57
+
- Ability to check on BDF and register address seen for each configuration address along with access type.
58
+
59
+
- SBSA Test 403 (Check ECAM Memory accessibility) execution time depends on the system PCIe hierarchy. For systems with multiple ECAMs the time taken to complete can be long which is normal. Please wait until the test completes.
60
+
38
61
## License
39
62
40
63
Arm SystemReady ACS is distributed under Apache v2.0 License.
@@ -48,5 +71,5 @@ Arm SystemReady ACS is distributed under Apache v2.0 License.
48
71
49
72
--------------
50
73
51
-
*Copyright (c) 2021, Arm Limited and Contributors. All rights reserved.*
74
+
*Copyright (c) 2021-2022, Arm Limited and Contributors. All rights reserved.*
0 commit comments