Enable a bunch of new Xen options, primarily blktap, PCI passthrough
and platform PCI device (PVHVM).
Also set default for a bunch of non-Xen options which are not covered
by the defconfig.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
XEN_GIT_ORIGIN to set the name of the remote origin; the default is
still "xen".
XEN_LINUX_GIT_LOCALBRANCH allows the name of the local branch to be
set. The default is the same as the remote branch.
XEN_LINUX_GITREV allows a specific GIT revision to be checked out,
rather than a branch. By default it is the remote branch name.
This change should result in no change in behaviour in the normal
case.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
When cloning kernel repo:
1. make remote called "xen" rather than the default "origin"
2. directly checkout the desired branch, rather than the default
then the desired one
Git 1.5 doesn't support -b on git clone, and seems to do something odd
with the checkout branch argument, so avoid using the newer
commandline options.
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
When cloning the kernel repo:
1. make remote called "xen" rather than the default "origin"
2. directly checkout the desired branch in one step
Signed-off-by: Jeremy Fitzhardinge<jeremy.fitzhardinge@citrix.com>
Enables a couple of SCSI host controllers which are found in our test
farm but not enabled in the default upstream kernel. The new drivers
are compiled as modules which is pretty harmless so this should be
safe.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
The unnecessary 'used greatest stack depth' messages on the console
breaks xm-test cases by random. Typically a testcase reads input from
the console and parses it. When DEBUG_STACK_USAGE is enabled, these
stack usage messages are printed by random - the test case reads this
message, cannot handle it and fails.
Signed-off-by: Andreas Florath <xen@flonatel.org>
This one-liner adds bridge support to the Linux kernel
(CONFIG_BRIDGE=y). It is a precondition for some xm-tests that
bridge is enabled. Also IMHO it makes sense to configure a dom0 with
bridge capabilities.
Signed-off-by: Andreas Florath <xen@flonatel.org>
ports from build integration
Both distros now include Xen support from their respective upstreams
and these kernels are very out of date wrt both the upstream distro
kernel and the upstream Xen kernel.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
git 1.4.x (which is on even some moderately recent systems) doesn't
have the `git remote' command. This is what caused the most recent
patchman build failure.
The machinery in buildconfigs/src.git-clone was rather more
complicated than needed, too. In this patch I replace this with a
similar set of runes to those used for ioemu-remote (almost identical
except that the QEMU_TAG feature is not supported in this instance).
I have done a successful test build with this change.
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
This has finally bugged me enough to do something about it:
make prints `***' when it stops due to an error. With make -j, and/or
with automated build systems, this error marker can be in the middle
of a large logfile. It is useful to be able to search for it.
Therefore change occurrences of `*' to `=' for information and warning
messages. `***' is reserved for cases where the build stops.
A corresponding change is being applied to qemu-xen-unstable.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
I have copied the tarballs that the xen-unstable build downloads to
xenbits.xensource.com (which also hosts our hg and git). This patch
changes the download URLs to use that location.
That way the build will depend on only one external machine, under one
administration, rather than many. Also it means that the build won't
break if these sites become permanently unavailable or are rearranged
and we don't run a risk of having to panic and beg if a file should go
missing.
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
If this option is enabled then the Xen mercurial version ID gets
tacked onto the kernel version (e.g. 2.6.24-git22-hg2593b69b183b)
which is unlikely to be useful or desirable. All the trees which we
build using this method already have uniquely identifying versions
(e.g. 2.6.24-git22 or 2.6.24-mm1).
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
In particular:
- support merged x86 architecture. To facilitate this it made sense
to encode some existing logic in shell scripts rather than
increasing complicated make conditionals.
- set CONFIG_PARAVIRT_GUEST=y which is required for newer kernels.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
This is useful for the non 2.6.18-xen builds where the defconfig at
any particular momement may require additional questions to be
answered.
Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
When building a linux kernel, if the modules build fails, then
the build carries on regardless.
The problem is simple - the "make modules" failure is not seen
by the calling make since its return value is not what is
returned.
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
Changing LINUX_VER causes us to clone the wrong repository so instead
use the kernel's "kernelrelease" target to figure out the correct
Linux version.
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
(/sbin/installkernel) to be called since linux-2.6.18-xen.hg
211:c1f5d027adf7.
Unfortunately on some distros this script is broken for non-root
use. Our needs are pretty simple anyway so just open code the
installation of the kernel.
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
* Merge the guts of the various upstream branch buildconfigs into a
single mk.linux-2.6 which they include.
* Add support for the -git snapshot branch.
* Update .hgignore to ignore all these new trees.
* Update buildconfigs/enable-xen-config to make the upstream defconfig
compile without questions.
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
(note that not all of those contains Xen support just yet and that a
native kernel will be silently built in that case.)
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
prepared. This is to support upstream sources which do not enable Xen in their
default configurations.
Signed-off-by: Ian Campbell <ian.campbell@xensource.com>
Keir Fraser
Ian Campbell
Keir Fraser
kfraser@localhost.localdomain