@@ -167,18 +167,12 @@ create_build_jobs () {
if [ "x$REVISION_LINUX_OLD" != xdisable ]; then
- ./cs-job-create $flight build-$arch-oldkern build \
- arch=$arch \
- tree_qemu=$TREE_QEMU \
- tree_qemuu=$TREE_QEMU_UPSTREAM \
- tree_xen=$TREE_XEN \
+ ./cs-job-create $flight build-$arch-oldkern build-kern \
+ arch=$arch kconfighow=create-config-sh \
+ kimagefile=vmlinux \
$RUNVARS $BUILD_RUNVARS $BUILD_LINUX_OLD_RUNVARS \
$arch_runvars $suite_runvars \
host_hostflags=$build_hostflags \
- xen_kernels=linux-2.6-xen \
- revision_xen=$REVISION_XEN \
- revision_qemu=$REVISION_QEMU \
- revision_qemuu=$REVISION_QEMU_UPSTREAM \
tree_linux=http://xenbits.xen.org/linux-2.6.18-xen.hg \
revision_linux=$REVISION_LINUX_OLD
@@ -265,6 +265,22 @@ END
# /;
}
+sub config_create_config_sh () {
+ die "only x86" unless $r{arch} =~ m/^amd64|i386$/;
+
+ my $xta = $r{arch} eq "amd64" ? "x86_64" : "x86_32";
+
+ target_cmd_build($ho, 1000, $builddir, <<END);
+ cd linux
+ sh buildconfigs/create_config.sh .config "-xen" $xta
+ if [ x$xta = xx86_32 ] ; then
+ sed -i.bak -e 's!^CONFIG_HIGHMEM4G=y\$!\# CONFIG_HIGHMEM4G is not set!;s!^\# CONFIG_HIGHMEM64G is not set\$!CONFIG_HIGHMEM64G=y!' .config
+ fi
+ yes '' | make oldconfig
+END
+ # /;
+}
+
sub config () {
my $confighow= $r{kconfighow};
$confighow =~ s/\W/_/g;
instead of using the kernel build integration in xen.git, which is going away. There is no difference to the .config produced. No test jobs seem to rely on these kernels so I have not worried about making the contents of dist be identical (specifically the filenames under /boot have lost their -xen suffix) Remove the now unused xen and qemu(u) tree/revision stuff from the jobs' runvars. Add the appropriate kconfighow and kimagefile runvars and implement an appropriate kconfighow handler to use the create_config.sh present in this tree (the xen.git intergration called the same script) If the 2.6.18 build starts to fail, xen-unstable pushes will be broken until they are fixed, as before. Previously such a build failure might be due to changes in xen.git so that was slightly justifiable. But in practice this is quite rare. This situation, while anomalous, is tolerable. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- v2: stole some of your words for the commit message, I hope I am grasping the correct end of the stick. --- mfi-common | 12 +++--------- ts-kernel-build | 16 ++++++++++++++++ 2 files changed, 19 insertions(+), 9 deletions(-)