s are specified.
>
> Fixes: 05f4cc219235 ("x86emul: suppress default test harness build with
> incapable compiler")
> Fixes: d5997399b7ad ("x86emul: suppress "not built" warning for test
> harness'es run targets")
> Signed-off-by: Jan Beulich
Acked-by: Andrew Cooper
fault test harness build with
incapable compiler")
Fixes: d5997399b7ad ("x86emul: suppress "not built" warning for test harness'es
run targets")
Signed-off-by: Jan Beulich
--- a/tools/tests/x86_emulator/Makefile
+++ b/tools/tests/x86_emulator/Makefile
@@ -98,7 +
On 12/11/2025 3:00 pm, Jan Beulich wrote:
> Many *.c files are symlinked while building, so along with generated *.h
> files they ought to be removed. Conversely $(TARGET) doesn't need removing
> twice.
>
> Fixes: cb4fcf70b2f3 ("x86emul: parallelize SIMD test code buildi
Many *.c files are symlinked while building, so along with generated *.h
files they ought to be removed. Conversely $(TARGET) doesn't need removing
twice.
Fixes: cb4fcf70b2f3 ("x86emul: parallelize SIMD test code building")
Signed-off-by: Jan Beulich
--- a/tools/tests/x86_em
On Tue, 9 Sep 2025, [email protected] wrote:
> On Tue, Sep 09, 2025 at 06:01:11PM +0100, Andrew Cooper wrote:
> > The container is running as root, but be explicit anyway.
> >
> > No functional change.
> >
> > Signed-off-by: Andrew Cooper
>
> Reviewed-by: Denis Mukhin
Acked-by: Stefano Stabell
ff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
index 95b883b32bb6..1de68a0fe450 100644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -77,7 +77,7 @@
.qemu-riscv64:
extends: .test-jobs-common
variables:
-CONTAINER: debian:
b883b32bb6..1de68a0fe450 100644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -77,7 +77,7 @@
.qemu-riscv64:
extends: .test-jobs-common
variables:
-CONTAINER: debian:12-riscv64
+CONTAINER: debian:13-riscv64
LOGFILE: qemu-smoke-riscv64.log
artifacts:
utomation/gitlab-ci/test.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> index 95b883b32bb6..1de68a0fe450 100644
> --- a/automation/gitlab-ci/test.yaml
> +++ b/automation/gitlab-ci/tes
0644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -77,7 +77,7 @@
.qemu-riscv64:
extends: .test-jobs-common
variables:
-CONTAINER: debian:12-riscv64
+CONTAINER: debian:13-riscv64
LOGFILE: qemu-smoke-riscv64.log
artifacts:
paths:
--
2.39.5
On Tue, Sep 09, 2025 at 06:01:11PM +0100, Andrew Cooper wrote:
> The container is running as root, but be explicit anyway.
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Denis Mukhin
> ---
> CC: Anthony PERARD
> CC: Stefano Stabellini
> CC: Marek Marczykowski-Górec
The container is running as root, but be explicit anyway.
No functional change.
Signed-off-by: Andrew Cooper
---
CC: Anthony PERARD
CC: Stefano Stabellini
CC: Marek Marczykowski-Górecki
---
scripts/alpine-rootfs.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/a
offs )
>> +panic("%s: non-zero offset (%#lx) unexpected\n", expected, offs);
>
> If there's a non-zero offset returned, could you also print the
> returned name? (so use %s+%#lx) there's a change the returned name
> doesn't match what we expect if there's a non-zero offset.
Hmm, perhaps we could, even if that's not the main goal of the test. Note
though that the patch has gone in already, with Jason's R-b.
> The rest LGTM:
>
> Acked-by: Roger Pau Monné
Nevertheless, thanks.
Jan
On Wed, Apr 02, 2025 at 03:57:57PM +0200, Jan Beulich wrote:
> ... before making changes to the involved logic.
>
> Signed-off-by: Jan Beulich
> ---
> While Andrew validly suggests cf_check isn't a requirement for selecting
> which function(s) to use (with the non-upstream gcc patch that we're
>
On 2025-04-02 09:57, Jan Beulich wrote:
... before making changes to the involved logic.
Signed-off-by: Jan Beulich
Reviewed-by: Jason Andryuk
n't try to download the junit file in this case. So we ignore
> > the return value of run-tools-test to always print "$passed" and
> > instead look for failure in the generated junit file. If the junit
> > report is incomplete, this will also result in a failure of t
On Wed, Jul 30, 2025 at 05:26:00PM +0200, Anthony PERARD wrote:
> From: Anthony PERARD
>
> The main script expect to find the string "$passed" or it just timeout
> and doesn't try to download the junit file in this case. So we ignore
> the return value of run-tools
On Fri, Aug 08, 2025 at 04:32:43PM +0200, Marek Marczykowski-Górecki wrote:
> The recent failure affected only glibc-based systems, so do the test on
> Debian too.
>
> Signed-off-by: Marek Marczykowski-Górecki
Just one tiny comment below, otherwise looks good to me!
With or withou
The recent failure affected only glibc-based systems, so do the test on
Debian too.
Signed-off-by: Marek Marczykowski-Górecki
---
Changes in v2:
- use systemd in Debian
I once got the following timeout:
(backend) ==> /var/log/xen/xldevd.log <==
(backend) libxl: error: libxl_aou
ssion.
Requires debian in test-artifacts repo - patch sent separately.
Marek Marczykowski-Górecki (3):
CI: Add driver domains tests
CI: Add configure --enable-systemd for full build
CI: Run driver domains test on Debian too
automation/build/debian/12-x86_64.dockerfile| 1 +-
automation/gitl
n Linux these days.
>
> What would need to be different in tests to avoid OpenRC? If it's only
> the script to start the test running, can't we just declare a name, and
> arrange for both init systems to run it?
In this particular test, probably just that. And convincing
sy
e needed some non-Alpine testing too, but for
a different reason.
We have systemd configuration in Xen, and changes to it, yet no CI of
what is the most common init system in Linux these days.
What would need to be different in tests to avoid OpenRC? If it's only
the script to start the test
The recent failure affected only glibc-based systems, so do the test on
Debian too.
Signed-off-by: Marek Marczykowski-Górecki
---
automation/gitlab-ci/test.yaml | 19 +++
1 file changed, 19 insertions(+)
diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci
ssion.
Requires debian in test-artifacts repo - patch sent separately.
Marek Marczykowski-Górecki (2):
CI: Add driver domains tests
CI: Run driver domains test on Debian too
automation/gitlab-ci/test.yaml | 27 -
automation/scripts/qemu-driverdomains-x86_64.sh
On Thu, Aug 07, 2025 at 02:03:07AM +0200, Marek Marczykowski-Górecki wrote:
> Will be used as dom0/domU in some tests.
>
> Install OpenRC and setup it to start /etc/local.d/ scripts so tests
> don't need different cases for Alpine and Debian.
Looks like this one did not reached the list:
: host
en
> done in a way to support adding new compression algorithms easily. That
> requires generating a new test-pdx- executable that's build with
> the selected PDX compression enabled.
>
> Currently the only generated executable is test-pdx-mask that tests PDX
> mask compre
requires generating a new test-pdx- executable that's build with
the selected PDX compression enabled.
Currently the only generated executable is test-pdx-mask that tests PDX
mask compression.
Signed-off-by: Roger Pau Monné
---
Changes since v2:
- Use set -e when running the tests.
- Drop
From: Anthony PERARD
The main script expect to find the string "$passed" or it just timeout
and doesn't try to download the junit file in this case. So we ignore
the return value of run-tools-test to always print "$passed" and
instead look for failure in the generated
requires generating a new test-pdx- executable that's build with
the selected PDX compression enabled.
Currently the only generated executable is test-pdx-mask that tests PDX
mask compression.
Signed-off-by: Roger Pau Monné
---
Changes since v2:
- Use set -e when running the tests.
- Drop
From: Ard Biesheuvel
The EFI test module covers the get/set wakeup time EFI runtime
services, as well as GetNextHighMonoCount(). In both cases, though, it
just mindlessly exercises the API, without any functional testing.
In case of the get/set wakeup time services, this would involve setting
On Tue, Jun 24, 2025 at 03:37:34PM +0200, Anthony PERARD wrote:
> On Fri, Jun 20, 2025 at 01:11:28PM +0200, Roger Pau Monne wrote:
> > +.PHONY: run
> > +run: $(TARGETS)
> > +ifeq ($(CC),$(HOSTCC))
> > + for test in $? ; do \
> > + ./$$test ; \
> >
On Fri, Jun 20, 2025 at 01:11:28PM +0200, Roger Pau Monne wrote:
> +.PHONY: run
> +run: $(TARGETS)
> +ifeq ($(CC),$(HOSTCC))
> + for test in $? ; do \
> + ./$$test ; \
> + done
You need to add `set -e` or the exit value from the tested binary might
be
work/interfaces.
> > > This allows extracting more logs out of the test system.
> > >
> > > Signed-off-by: Marek Marczykowski-Górecki
> > >
> > > ---
> > > This enables passwordless root login. It's okay for qubes runners, as
> > >
64 / LINUX_JOB_ARM64 ? If so, we would
> need the corresponding jobs in test-artifacts.
See the cover letter (in which I forgot to CC you...).
The idea is to have separate pipelines (via a schedule) to test
different Linux branches, and each of them would select what Linux
branch is tested using
On Mon, 23 Jun 2025, Andrew Cooper wrote:
> On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> > This is necessary for new Zen4 runner.
> > Do not include Argo module in this build, as it isn't compatible with
> > 6.12 yet.
> >
> > Signed-off-by: Marek Marczykowski-Górecki
>
> Acked-by: A
On Mon, 23 Jun 2025, Andrew Cooper wrote:
> On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> > It uses this USB network interface.
> >
> > Signed-off-by: Marek Marczykowski-Górecki
>
> Acked-by: Andrew Cooper
Acked-by: Stefano Stabellini
with different LINUX_JOB_X86_64 / LINUX_JOB_ARM64 ? If so, we would
need the corresponding jobs in test-artifacts.
> Signed-off-by: Marek Marczykowski-Górecki
> ---
> I have considered common LINUX_JOB and then add architecture suffix, but
> even now X86 and ARM use different job
nvenience.
I can also see you are using the two variables in your xen.git patch
series. Is that idea that it would allow for a much wider Linux versions
testing? If we are going to only test one version, this is not required.
> ---
> .gitlab-ci.yml | 22 ++
>
On Mon, 23 Jun 2025, Andrew Cooper wrote:
> On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> > It will be used for fetching some Linux versions.
> >
> > Signed-off-by: Marek Marczykowski-Górecki
>
> Acked-by: Andrew Cooper
Acked-by: Stefano Stabellini
On Mon, Jun 23, 2025 at 02:56:00PM +0100, Andrew Cooper wrote:
> On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> > For this add also bridge package, so xenbr0 can be configured with
> > /etc/network/interfaces.
> > This allows extracting more logs out of the test s
On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> It will be used for fetching some Linux versions.
>
> Signed-off-by: Marek Marczykowski-Górecki
Acked-by: Andrew Cooper
On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> It uses this USB network interface.
>
> Signed-off-by: Marek Marczykowski-Górecki
Acked-by: Andrew Cooper
On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> This is necessary for new Zen4 runner.
> Do not include Argo module in this build, as it isn't compatible with
> 6.12 yet.
>
> Signed-off-by: Marek Marczykowski-Górecki
Acked-by: Andrew Cooper
On 23/06/2025 2:46 pm, Marek Marczykowski-Górecki wrote:
> For this add also bridge package, so xenbr0 can be configured with
> /etc/network/interfaces.
> This allows extracting more logs out of the test system.
>
> Signed-off-by: Marek Marczykowski-Górecki
> ---
> This enab
"Branch in test-artifacts to use for Linux"
+value: master
+ LINUX_JOB_X86_64:
+description: "Job name in test-artifacts to use for Linux x86_64"
+value: linux-6.12.34-x86_64
+ LINUX_JOB_ARM64:
+description: "Job name in test-artifacts to use for Linux ar
This is necessary for new Zen4 runner.
Do not include Argo module in this build, as it isn't compatible with
6.12 yet.
Signed-off-by: Marek Marczykowski-Górecki
---
.gitlab-ci.yml | 6 ++
1 file changed, 6 insertions(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index c698612..ad44fb4 100
gitlab-ci.yml
@@ -1,5 +1,9 @@
variables:
REGISTRY: registry.gitlab.com/xen-project/hardware/test-artifacts
+ LINUX_GIT_VERSION:
+description: "branch/tag/commit for the linux-git jobs"
+ LINUX_GIT_URL:
+description: "git url for the linux-git jobs"
stages:
It uses this USB network interface.
Signed-off-by: Marek Marczykowski-Górecki
---
This was posted before at
https://lore.kernel.org/xen-devel/[email protected]/
---
scripts/build-linux.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/build-lin
For this add also bridge package, so xenbr0 can be configured with
/etc/network/interfaces.
This allows extracting more logs out of the test system.
Signed-off-by: Marek Marczykowski-Górecki
---
This enables passwordless root login. It's okay for qubes runners, as
they are isolated (even
It will be used for fetching some Linux versions.
Signed-off-by: Marek Marczykowski-Górecki
---
images/alpine/3.18-arm64-build.dockerfile | 1 +
1 file changed, 1 insertion(+)
diff --git a/images/alpine/3.18-arm64-build.dockerfile
b/images/alpine/3.18-arm64-build.dockerfile
index 25a8dbd..3846
This series is necessary for the other one sent in a moment.
Technically, the last patch isn't strictly required, but it eases debugging.
Green pipeline:
https://gitlab.com/xen-project/people/marmarek/test-artifacts/-/pipelines/1881057399
Marek Marczykowski-Górecki (5):
Add linux-6.
On 23/6/25 13:59, Philippe Mathieu-Daudé wrote:
On 23/6/25 10:11, Thomas Huth wrote:
On 20/06/2025 15.07, Philippe Mathieu-Daudé wrote:
On macOS this test fails:
qemu-system-aarch64: mach-virt: HVF does not support providing
Virtualization extensions to the guest CPU
Signed-off-by
On 23/6/25 10:11, Thomas Huth wrote:
On 20/06/2025 15.07, Philippe Mathieu-Daudé wrote:
On macOS this test fails:
qemu-system-aarch64: mach-virt: HVF does not support providing
Virtualization extensions to the guest CPU
Signed-off-by: Philippe Mathieu-Daudé
---
tests/functional
requires generating a new test-pdx- executable that's build with
the selected PDX compression enabled.
Currently the only generated executable is test-pdx-mask that tests PDX
mask compression.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version (partially pulled out f
ep 5
> sh /scratch/gitlab-runner/${TEST_BOARD}.sh 1
> sleep 5
> set +e
> -stty -F ${SERIAL_DEV} 57600
> +stty -F ${SERIAL_DEV} 57600 -echo
>
> # Capture test result and power off board before exiting.
> export PASSED="${PASS_MSG}"
> diff --git a/automation/s
/scripts/xilinx-smoke-dom0-x86_64.sh
+++ b/automation/scripts/xilinx-smoke-dom0-x86_64.sh
@@ -165,7 +165,7 @@ sleep 5
sh /scratch/gitlab-runner/${TEST_BOARD}.sh 1
sleep 5
set +e
-stty -F ${SERIAL_DEV} 57600
+stty -F ${SERIAL_DEV} 57600 -echo
# Capture test result and power off board before exiting
s/qubes-x86-64.sh
> > +++ b/automation/scripts/qubes-x86-64.sh
> > @@ -135,10 +135,11 @@ done
> > ### tests: tools-tests-pv, tools-tests-pvh
> > "tools-tests-pv"|"tools-tests-pvh")
> > retrieve_xml=1
> > -pas
10 +135,11 @@ done
> ### tests: tools-tests-pv, tools-tests-pvh
> "tools-tests-pv"|"tools-tests-pvh")
> retrieve_xml=1
> -passed="test passed"
> +passed="run-tools-test over"
> domU_check=""
&g
On 03/06/2025 1:42 pm, Anthony PERARD wrote:
> From: Anthony PERARD
>
> Otherwise, failed tests are ignored by automated test.
Fixes 7bf777b42cad
> Signed-off-by: Anthony PERARD
Reviewed-by: Andrew Cooper
From: Anthony PERARD
The main script expect to find the string "$passed" or it just
timeout. Then, it doesn't try to download the junit file.
So ignore the return value of run-tools-test for now.
This mean the job will not fail, but at least we should have the junit
files
From: Anthony PERARD
Otherwise, failed tests are ignored by automated test.
Signed-off-by: Anthony PERARD
---
tools/tests/rangeset/test-rangeset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/tests/rangeset/test-rangeset.c
b/tools/tests/rangeset/test-rangeset.c
On Wed, May 21, 2025 at 10:18 PM wrote:
> From: Christopher Clark
>
> From: Christopher Clark
>
> Simple test cases for the four Argo operations, register, unregister,
> sendv and notify exercised with a single test domain.
> Add infrastructure to access Argo: a 5-argument
Is there any reason for the deassigning these two GSIs ?
Yes, KVM's rather bizarre ABI is that DEASSIGN is allowed even if the VM doesn't
have a corresponding assigned irqfd. The reason I added these early DEASSIGN
calls is so that there will be an easier-to-debug failure if KVM's
GN);
> > + kvm_irqfd(vm1, 14, READ_ONCE(__eventfd), KVM_IRQFD_FLAG_DEASSIGN);
>
> Hi Sean,
> I dont see any allocation for the GSI 13 and 14..
> Is there any reason for the deassigning these two GSIs ?
Yes, KVM's rather bizarre ABI is that DEASSIGN is allowed even if the V
On 5/23/2025 5:22 AM, Sean Christopherson wrote:
+
+int main(int argc, char *argv[])
+{
+ pthread_t racing_thread;
+ int r, i;
+
+ /* Create "full" VMs, as KVM_IRQFD requires an in-kernel IRQ chip. */
+ vm1 = vm_create(1);
+ vm2 = vm_create(1);
+
+ WRITE_ONCE(
Add a selftest to verify that eventfd+irqfd bindings are globally unique,
i.e. that KVM doesn't allow multiple irqfds to bind to a single eventfd,
even across VMs.
Signed-off-by: Sean Christopherson
---
tools/testing/selftests/kvm/Makefile.kvm | 1 +
tools/testing/selftests/kvm/irqfd_test.c |
Assert that eventfd() succeeds in the Xen shinfo test instead of skipping
the associated testcase. While eventfd() is outside the scope of KVM, KVM
unconditionally selects EVENTFD, i.e. the syscall should always succeed.
Signed-off-by: Sean Christopherson
---
tools/testing/selftests/kvm/x86
The patch series integrates an XTF argo test available at [1].
Patch 1 is the original test.
Patch 2 adds fixups to run the test under QEMU environment in gitlab CI.
[1]
https://github.com/dozylynx/meta-argo/blob/master/recipes-extended/xen/xtf/0001-Add-Argo-test.patch
[2] Link to v1:
https
From: Christopher Clark
From: Christopher Clark
Simple test cases for the four Argo operations, register, unregister,
sendv and notify exercised with a single test domain.
Add infrastructure to access Argo: a 5-argument hypercall, number 39.
Signed-off-by: Christopher Clark
Signed-off-by
On Tue, May 20, 2025 at 09:52:36PM +0100, Andrew Cooper wrote:
> Rearrange tools/tests to be more ameanable to running in CI, and drop the
> special casing holding it together.
>
>
>
> Andrew Cooper (3):
> tools/tests: Drop depriv-fd-checker
> tools/tests: Install tests into $(LIBEXEC)/tests
Rearrange tools/tests to be more ameanable to running in CI, and drop the
special casing holding it together.
Andrew Cooper (3):
tools/tests: Drop depriv-fd-checker
tools/tests: Install tests into $(LIBEXEC)/tests
CI: Drop custom handling of tools/tests
.gitignore
i
> ---
> scripts/alpine-rootfs.sh | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/scripts/alpine-rootfs.sh b/scripts/alpine-rootfs.sh
> index c304e2ebfbd9..c999b89dbcd8 100755
> --- a/scripts/alpine-rootfs.sh
> +++ b/scripts/alpine-rootfs.sh
> @@ -22,6 +22,9
.sh b/scripts/alpine-rootfs.sh
index c304e2ebfbd9..c999b89dbcd8 100755
--- a/scripts/alpine-rootfs.sh
+++ b/scripts/alpine-rootfs.sh
@@ -22,6 +22,9 @@ PKGS=(
xz
yajl
+# Xen Test Framework
+python3
+
# QEMU
glib
libaio
--
2.39.5
On 5/12/25 10:58 AM, Andrew Cooper wrote:
> On 12/05/2025 11:58 am, Jan Beulich wrote:
>> On 08.05.2025 18:03, Andrew Cooper wrote:
>>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>>> stale
>>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>
On 12.05.2025 16:58, Andrew Cooper wrote:
> On 12/05/2025 11:58 am, Jan Beulich wrote:
>> On 08.05.2025 18:03, Andrew Cooper wrote:
>>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>>> stale
>>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>
On 12/05/2025 11:58 am, Jan Beulich wrote:
> On 08.05.2025 18:03, Andrew Cooper wrote:
>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>> stale
>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>> specifically an out-of-line-ing mechansim, and
On 08.05.2025 18:03, Andrew Cooper wrote:
> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already stale
> by the time speculative vulnerabilities hit the headlines in 2018. It is
> specifically an out-of-line-ing mechansim, and repoline is one of several
> safety sequences used.
On Fri, 9 May 2025, Andrew Cooper wrote:
> On 09/05/2025 11:10 pm, Stefano Stabellini wrote:
> > On Fri, 9 May 2025, Andrew Cooper wrote:
> >> The CI improvements have been backported to all Xen branches.
> >>
> >> Remove the transitionary tar/cpio parameter in scripts/alpine-rootfs.sh
> >>
> >> Si
On 09/05/2025 11:10 pm, Stefano Stabellini wrote:
> On Fri, 9 May 2025, Andrew Cooper wrote:
>> The CI improvements have been backported to all Xen branches.
>>
>> Remove the transitionary tar/cpio parameter in scripts/alpine-rootfs.sh
>>
>> Signed-off-by: Andrew Cooper
>> ---
>> CC: Anthony PERAR
etc home init lib mnt opt root sbin usr var"
> -tar cvzf "${COPYDIR}/initrd.tar.gz" $PATHS
> -;;
> -esac
> +# Print the contents for the build log
> +zcat "${COPYDIR}/rootfs.cpio.gz" | cpio -tv
> diff --git a/scripts/x86_64-argo-linux.sh b/
HS
-;;
-esac
+# Print the contents for the build log
+zcat "${COPYDIR}/rootfs.cpio.gz" | cpio -tv
diff --git a/scripts/x86_64-argo-linux.sh b/scripts/x86_64-argo-linux.sh
deleted file mode 100755
index a110a3378192..
--- a/scripts/x86_64-argo-linux.sh
+++ /dev/null
@@ -1
On 09/05/2025 9:14 am, Roger Pau Monné wrote:
> On Thu, May 08, 2025 at 05:03:36PM +0100, Andrew Cooper wrote:
>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>> stale
>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>> specifically an out-of
On Thu, May 08, 2025 at 05:03:36PM +0100, Andrew Cooper wrote:
> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already stale
> by the time speculative vulnerabilities hit the headlines in 2018. It is
> specifically an out-of-line-ing mechansim, and repoline is one of several
> s
The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already stale
by the time speculative vulnerabilities hit the headlines in 2018. It is
specifically an out-of-line-ing mechansim, and repoline is one of several
safety sequences used.
Some of this boilerplate has been copied into al
On 29/04/2025 1:48 pm, Roger Pau Monné wrote:
> On Tue, Apr 29, 2025 at 01:36:43PM +0100, Andrew Cooper wrote:
>> It turns out that QEMU built in staging-4.19 (only) depends on it.
>>
>> But, GCC can emit libgcc calls for arbitrary reasons, so include it
>> unconditionally.
> Is there a fixes tag f
On Tue, Apr 29, 2025 at 01:36:43PM +0100, Andrew Cooper wrote:
> It turns out that QEMU built in staging-4.19 (only) depends on it.
>
> But, GCC can emit libgcc calls for arbitrary reasons, so include it
> unconditionally.
Is there a fixes tag for this, or it has always been this way?
> Signed-o
It turns out that QEMU built in staging-4.19 (only) depends on it.
But, GCC can emit libgcc calls for arbitrary reasons, so include it
unconditionally.
Signed-off-by: Andrew Cooper
---
CC: Marek Marczykowski-Górecki
CC: Anthony PERARD
CC: Jan Beulich
---
scripts/alpine-rootfs.sh | 1 +
1 fil
On Mon, Apr 21, 2025 at 01:39:32PM -0700, Stefano Stabellini wrote:
> On Sat, 19 Apr 2025, [email protected] wrote:
> > From: Denis Mukhin
> >
> > Use qemu-xtf.sh for qemu-smoke-x86-64-gcc-efi job.
> >
> > Lead time is reduced a bit since not all XTF code base is
On Mon, Apr 21, 2025 at 01:39:21PM -0700, Stefano Stabellini wrote:
> On Sat, 19 Apr 2025, [email protected] wrote:
> > From: Denis Mukhin
> >
> > Add test runner script qemu-xtf.sh which is allows any XTF x86 test to be
> > easily executed. Test runner is invoked from th
nfig
@@ -0,0 +1,2 @@
+CONFIG_GICV2=y
+CONFIG_SBSA_UART=y
diff --git a/automation/scripts/include/xtf-arm64
b/automation/scripts/include/xtf-arm64
new file mode 100644
index 00..1a318b7aa0
--- /dev/null
+++ b/automation/scripts/include/xtf-arm64
@@ -0,0 +1,81 @@
+#!/bin/bash
+#
+# XTF test utilities (arm64
From: Denis Mukhin
Introduce new CI job to run x86 XTF argo test under QEMU to smoke test argo
feature functionality in upstream CI.
The new job lead time is ~30s, limit max job duration to 60s.
Signed-off-by: Denis Mukhin
Reviewed-by: Stefano Stabellini
---
Changes v2->v3:
- Added Stefan
From: Denis Mukhin
Use qemu-xtf.sh for qemu-smoke-x86-64-gcc-efi job.
Lead time is reduced a bit since not all XTF code base is built, just the
required test.
Signed-off-by: Denis Mukhin
---
Changes v2->v3:
- use pv64 variant for EFI job
---
automation/gitlab-ci/test.yaml|
From: Denis Mukhin
Add test runner script qemu-xtf.sh which is allows any XTF x86 test to be
easily executed. Test runner is invoked from the qemu-smoke* jobs with the
hardcoded parameters.
Each x86 XTF job lead time is reduced a bit since only the test-related code
is built, not the entire XTF
On Sat, 19 Apr 2025, [email protected] wrote:
> From: Denis Mukhin
>
> Use qemu-xtf.sh for qemu-smoke-x86-64-gcc-efi job.
>
> Lead time is reduced a bit since not all XTF code base is built, just the
> required test.
>
> Signed-off-by: Denis Mukhin
> ---
> Cha
On Sat, 19 Apr 2025, [email protected] wrote:
> From: Denis Mukhin
>
> Introduce new CI job to run x86 XTF argo test under QEMU to smoke test argo
> feature functionality in upstream CI.
>
> The new job lead time is ~30s, limit max job duration to 60s.
>
> Signed-off-by:
On Sat, 19 Apr 2025, [email protected] wrote:
> From: Denis Mukhin
>
> Add test runner script qemu-xtf.sh which is allows any XTF x86 test to be
> easily executed. Test runner is invoked from the qemu-smoke* jobs with the
> hardcoded parameters.
>
> Each x86 XTF job lead
0 +1,81 @@
+#!/bin/bash
+#
+# XTF test utilities (arm64).
+#
+
+# Arch-specific environment overrides.
+function xtf_arch_prepare()
+{
+export FW_PREFIX="${FW_PREFIX:-/usr/lib/u-boot/qemu_arm64/}"
+export QEMU_PREFIX="${QEMU_PREFIX:-${WORKDIR}/}"
+export XEN_BINARY=&q
From: Denis Mukhin
Add test runner script qemu-xtf.sh which is allows any XTF x86 test to be
easily executed. Test runner is invoked from the qemu-smoke* jobs with the
hardcoded parameters.
Each x86 XTF job lead time is reduced a bit since only the test-related code
is built, not the entire XTF
From: Denis Mukhin
Introduce new CI job to run x86 XTF argo test under QEMU to smoke test argo
feature functionality in upstream CI.
The new job lead time is ~30s, limit max job duration to 60s.
Signed-off-by: Denis Mukhin
---
Depends on
https://lore.kernel.org/xen-devel
From: Denis Mukhin
Use qemu-xtf.sh for qemu-smoke-x86-64-gcc-efi job.
Lead time is reduced a bit since not all XTF code base is built, just the
required test.
Signed-off-by: Denis Mukhin
---
Changes since v2:
- removed TOP
- dropped XEN_CONSOLE in favor of XEN_CMDLINE
---
automation/gitlab
tion/scripts/qubes-x86-64.sh
> >> +++ b/automation/scripts/qubes-x86-64.sh
> >> @@ -164,16 +164,13 @@ ${domU_extra_config}
> >> "
> >>
> >> if [ -n "$domU_check" ]; then
> >> -# DomU
> >> +# DomU rootfs
> >&g
1 - 100 of 15358 matches
Mail list logo
