On 16/04/2025 12:48 am, Stefano Stabellini wrote: > On Mon, 14 Apr 2025, Andrew Cooper wrote: >> Right now, the argo artefacts are a pile of files which the test has to turn >> back into something which resembles a filesystem. Furthermore, because we do >> not build modules for the main kernel, it is extra important to make sure >> that >> xen-argo.ko doesn't get out of sync. >> >> Build argo conditionally as part of the linux artefact. It's ~100kb all >> together, compared to ~14M for the kernel. >> >> Produce a single argo.cpio.gz with xen-argo.ko in the standard location. >> Prune userspace down to just the executables and libraries. >> >> This is cribbed from the existing scripts/x86_64-linux-argo.sh, which stays >> in >> place in the short term until Xen can be updated to use the new scheme. >> >> Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> > Do we need to remove x86_64-argo-linux.sh?
Yes, but 4.20 still uses it. One thing I'm not sure about is whether "keep latest artefact" is just artefacts from the latest run, or the latest of each named artefact. Now is as good a time to experiment as any. ~Andrew
