feat: Add vendor test infrastructure framework

[ashishsingha]

• Add vendor test numbering scheme in acs_common.h (10000+ range)
• Add vendor test template and documentation in test_pool/vendor/
• Add verify_vendor_inf.sh script to check vendor INFs are in sync
• Update acsbuild.sh to support vendor builds with two-argument syntax
• Vendor builds auto-verify upstream sync before building

[ashishsingha]

@chetan-rathore @SrikarJosyula Please review this as well. As mentioned in the commit message, this adds framework for silicon vendors to add tests and build as part of the general ACS framework.

[chetan-rathore]

Thanks @ashishsingha for the PR—vendor-specific test addition looks like an interesting feature; we’ll review it and share feedback.

ACS follows a Test Pool → VAL → PAL layered structure (methodology: https://github.com/ARM-software/sysarch-acs/blob/main/docs/bsa/arm_bsa_architecture_compliance_validation_methodology.pdf). If new tests are being added into ACS, we expect there may also be corresponding updates needed in VAL/PAL. Could you please share whether you’ve already built and run the additional tests with the current ACS, and whether any required VAL/PAL changes were integrated into the existing VAL/PAL or compiled separately and linked as external libraries?

[ashishsingha]

Thanks @ashishsingha for the PR—vendor-specific test addition looks like an interesting feature; we’ll review it and share feedback.

ACS follows a Test Pool → VAL → PAL layered structure (methodology: https://github.com/ARM-software/sysarch-acs/blob/main/docs/bsa/arm_bsa_architecture_compliance_validation_methodology.pdf). If new tests are being added into ACS, we expect there may also be corresponding updates needed in VAL/PAL. Could you please share whether you’ve already built and run the additional tests with the current ACS, and whether any required VAL/PAL changes were integrated into the existing VAL/PAL or compiled separately and linked as external libraries?

Vendors can use this in 2 ways. They may have tests related to their IP that they choose to keep downstream, thus not requiring any modification to the VAL/PAL layers. For cases where someone makes enhancements, I expect users to upstream those changes if they choose not maintain them. I have locally validated both approaches, and I see them working seamlessly.

[ashishsingha]

Thanks @ashishsingha for the PR—vendor-specific test addition looks like an interesting feature; we’ll review it and share feedback.
ACS follows a Test Pool → VAL → PAL layered structure (methodology: https://github.com/ARM-software/sysarch-acs/blob/main/docs/bsa/arm_bsa_architecture_compliance_validation_methodology.pdf). If new tests are being added into ACS, we expect there may also be corresponding updates needed in VAL/PAL. Could you please share whether you’ve already built and run the additional tests with the current ACS, and whether any required VAL/PAL changes were integrated into the existing VAL/PAL or compiled separately and linked as external libraries?

Vendors can use this in 2 ways. They may have tests related to their IP that they choose to keep downstream, thus not requiring any modification to the VAL/PAL layers. For cases where someone makes enhancements, I expect users to upstream those changes if they choose not maintain them. I have locally validated both approaches, and I see them working seamlessly.

@chetan-rathore Any update on this?

[chetan-rathore]

Hi @ashishsingha,
This will require some time for conclusion, as the PR adds a mechanism to have some tests build as part of xBSA which are not in scope of the xBSA specification. I will keep you updated.