[PATCH 2/2] automation: Add test jobs to run XTF hypercall xen_version test

Michal Orzel posted 2 patches 1 year, 11 months ago
There is a newer version of this series
[PATCH 2/2] automation: Add test jobs to run XTF hypercall xen_version test
Posted by Michal Orzel 1 year, 11 months ago
Add test jobs in both debug and non-debug versions to run hyp-xen-version
XTF test as a dom0less domU on arm64. The purpose of this test is to
validate the functional behavior of xen_version hypercall.

Signed-off-by: Michal Orzel <michal.orzel@amd.com>
---
 automation/gitlab-ci/test.yaml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
index 2d57f4feb74a..9d4b5315e710 100644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -165,6 +165,22 @@ qemu-smoke-dom0less-arm64-gcc-debug-boot-cpupools:
     - *arm64-test-needs
     - alpine-3.12-gcc-debug-arm64-boot-cpupools
 
+qemu-xtf-dom0less-arm64-gcc-hyp-xen-version:
+    extends: .qemu-arm64
+    script:
+      - ./automation/scripts/qemu-xtf-dom0less-arm64.sh hyp-xen-version 2>&1 | tee ${LOGFILE}
+    needs:
+      - *arm64-test-needs
+      - alpine-3.12-gcc-arm64
+
+qemu-xtf-dom0less-arm64-gcc-debug-hyp-xen-version:
+  extends: .qemu-arm64
+  script:
+    - ./automation/scripts/qemu-xtf-dom0less-arm64.sh hyp-xen-version 2>&1 | tee ${LOGFILE}
+  needs:
+    - *arm64-test-needs
+    - alpine-3.12-gcc-debug-arm64
+
 qemu-smoke-dom0-arm32-gcc:
   extends: .qemu-arm32
   script:
-- 
2.25.1
Re: [PATCH 2/2] automation: Add test jobs to run XTF hypercall xen_version test
Posted by Stefano Stabellini 1 year, 11 months ago
On Thu, 15 Dec 2022, Michal Orzel wrote:
> Add test jobs in both debug and non-debug versions to run hyp-xen-version
> XTF test as a dom0less domU on arm64. The purpose of this test is to
> validate the functional behavior of xen_version hypercall.
> 
> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
> ---
>  automation/gitlab-ci/test.yaml | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)
> 
> diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> index 2d57f4feb74a..9d4b5315e710 100644
> --- a/automation/gitlab-ci/test.yaml
> +++ b/automation/gitlab-ci/test.yaml
> @@ -165,6 +165,22 @@ qemu-smoke-dom0less-arm64-gcc-debug-boot-cpupools:
>      - *arm64-test-needs
>      - alpine-3.12-gcc-debug-arm64-boot-cpupools
>  
> +qemu-xtf-dom0less-arm64-gcc-hyp-xen-version:
> +    extends: .qemu-arm64
> +    script:
> +      - ./automation/scripts/qemu-xtf-dom0less-arm64.sh hyp-xen-version 2>&1 | tee ${LOGFILE}
> +    needs:
> +      - *arm64-test-needs
> +      - alpine-3.12-gcc-arm64

I think this test only needs qemu-system-aarch64-6.0.0-arm64-export


> +qemu-xtf-dom0less-arm64-gcc-debug-hyp-xen-version:
> +  extends: .qemu-arm64
> +  script:
> +    - ./automation/scripts/qemu-xtf-dom0less-arm64.sh hyp-xen-version 2>&1 | tee ${LOGFILE}
> +  needs:
> +    - *arm64-test-needs
> +    - alpine-3.12-gcc-debug-arm64
> +
>  qemu-smoke-dom0-arm32-gcc:
>    extends: .qemu-arm32
>    script:
> -- 
> 2.25.1
>
Re: [PATCH 2/2] automation: Add test jobs to run XTF hypercall xen_version test
Posted by Michal Orzel 1 year, 11 months ago
Hi Stefano,

On 15/12/2022 22:08, Stefano Stabellini wrote:
> 
> 
> On Thu, 15 Dec 2022, Michal Orzel wrote:
>> Add test jobs in both debug and non-debug versions to run hyp-xen-version
>> XTF test as a dom0less domU on arm64. The purpose of this test is to
>> validate the functional behavior of xen_version hypercall.
>>
>> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
>> ---
>>  automation/gitlab-ci/test.yaml | 16 ++++++++++++++++
>>  1 file changed, 16 insertions(+)
>>
>> diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
>> index 2d57f4feb74a..9d4b5315e710 100644
>> --- a/automation/gitlab-ci/test.yaml
>> +++ b/automation/gitlab-ci/test.yaml
>> @@ -165,6 +165,22 @@ qemu-smoke-dom0less-arm64-gcc-debug-boot-cpupools:
>>      - *arm64-test-needs
>>      - alpine-3.12-gcc-debug-arm64-boot-cpupools
>>
>> +qemu-xtf-dom0less-arm64-gcc-hyp-xen-version:
>> +    extends: .qemu-arm64
>> +    script:
>> +      - ./automation/scripts/qemu-xtf-dom0less-arm64.sh hyp-xen-version 2>&1 | tee ${LOGFILE}
>> +    needs:
>> +      - *arm64-test-needs
>> +      - alpine-3.12-gcc-arm64
> 
> I think this test only needs qemu-system-aarch64-6.0.0-arm64-export
In case of pure dom0less configuration - yes.

~Michal
Re: [PATCH 2/2] automation: Add test jobs to run XTF hypercall xen_version test
Posted by Michal Orzel 1 year, 11 months ago

On 16/12/2022 10:33, Michal Orzel wrote:
> 
> 
> Hi Stefano,
> 
> On 15/12/2022 22:08, Stefano Stabellini wrote:
>>
>>
>> On Thu, 15 Dec 2022, Michal Orzel wrote:
>>> Add test jobs in both debug and non-debug versions to run hyp-xen-version
>>> XTF test as a dom0less domU on arm64. The purpose of this test is to
>>> validate the functional behavior of xen_version hypercall.
>>>
>>> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
>>> ---
>>>  automation/gitlab-ci/test.yaml | 16 ++++++++++++++++
>>>  1 file changed, 16 insertions(+)
>>>
>>> diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
>>> index 2d57f4feb74a..9d4b5315e710 100644
>>> --- a/automation/gitlab-ci/test.yaml
>>> +++ b/automation/gitlab-ci/test.yaml
>>> @@ -165,6 +165,22 @@ qemu-smoke-dom0less-arm64-gcc-debug-boot-cpupools:
>>>      - *arm64-test-needs
>>>      - alpine-3.12-gcc-debug-arm64-boot-cpupools
>>>
>>> +qemu-xtf-dom0less-arm64-gcc-hyp-xen-version:
>>> +    extends: .qemu-arm64
>>> +    script:
>>> +      - ./automation/scripts/qemu-xtf-dom0less-arm64.sh hyp-xen-version 2>&1 | tee ${LOGFILE}
>>> +    needs:
>>> +      - *arm64-test-needs
>>> +      - alpine-3.12-gcc-arm64
>>
>> I think this test only needs qemu-system-aarch64-6.0.0-arm64-export
> In case of pure dom0less configuration - yes.
I take back my words. We obviously need Xen binary as well so apart from qemu
we also need alpine-3.12-gcc-arm64 (debug/non-debug). For the pure dom0less, we do not
need toolstack, but these jobs are already being built for other test jobs so we will
not benefit from e.g. adding new build jobs and variable to specify the hypervisor only build.

~Michal