Update xm-test to support new architectures
cover Update xm-test to support new architectures
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus od this endevour is PPC but I believe that IA64 also benifits.
Patch summary:
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.
2: Remove hardcoded references to i386.
3: Rename configs/buildroot -> configs/buildroot-i386
and update Makefiles.
5: Update .hgignore to remove noise from the initrd building process 5: Refactor the XmTestLib and XmTestReport code to encapsulate all
platform variations in one place.
6: FYI: Add powerpc definiations.
This patch is for the xenppc tree but included here for comments and completeness.
With these patches applied I'm still able to build an initrd and run the xm-test on x86 with no regressions.
Feedback appreciated.
---
.hgignore | 9 tools/xm-test/lib/XmTestLib/XenDomain.py | 72 --- tools/xm-test/lib/XmTestLib/arch.py | 133 ++++++ tools/xm-test/lib/XmTestReport/OSReport.py | 10 tools/xm-test/lib/XmTestReport/arch.py | 48 ++ tools/xm-test/ramdisk/Makefile.am | 13 tools/xm-test/ramdisk/configs/buildroot | 330 --------------- tools/xm-test/ramdisk/configs/buildroot-i386 | 330 +++++++++++++++ tools/xm-test/ramdisk/configs/buildroot-powerpc | 334 ++++++++++++++++ 9 files changed, 879 insertions(+), 400 deletions(-)
PATCH 1/6 Update to use uClib buildroot-snapshot
Update to use uClib buildroot-snapshot.
Dated file no longer exists on upstream server.
---
tools/xm-test/ramdisk/Makefile.am | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
tools/xm-test/ramdisk/Makefile.am +1 -2
@@ -2,9 +2,8 @@ INITRD ?= http://xm-test.xensource.com/r EXTRA_DIST = skel configs patches -BR_TAR = buildroot-20060606.tar.bz2 +BR_TAR = buildroot-snapshot.tar.bz2 BR_URL = http://buildroot.uclibc.org/downloads/snapshots/$(BR_TAR) -#BR_URL = http://buildroot.uclibc.org/downloads/snapshots/buildroot-snapshot.tar.bz2 BR_SRC = buildroot BR_IMG = $(BR_SRC)/rootfs.i386.ext2
PATCH 2/6 Remove hard coded reference to i386
In reply to Tony BreedsRemove hard coded reference to i386.
In preperation for other architectures.
---
tools/xm-test/ramdisk/Makefile.am | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
tools/xm-test/ramdisk/Makefile.am +4 -2
@@ -2,12 +2,14 @@ INITRD ?= http://xm-test.xensource.com/r EXTRA_DIST = skel configs patches +BR_ARCH = $(shell uname -m | sed -e s/i.86/i386/) + BR_TAR = buildroot-snapshot.tar.bz2 BR_URL = http://buildroot.uclibc.org/downloads/snapshots/$(BR_TAR) BR_SRC = buildroot -BR_IMG = $(BR_SRC)/rootfs.i386.ext2 +BR_IMG = $(BR_SRC)/rootfs.$(BR_ARCH).ext2 -BR_ROOT = build_i386/root +BR_ROOT = build_$(BR_ARCH)/root HVM_SCRIPT = bin/create_disk_image
PATCH 3/6 rename buildroot -> buildroot-i386
In reply to Tony Breedsrename buildroot -> buildroot-i386.
Also update Makefile.
---
hg mv --after tools/xm-test/ramdisk/configs/buildroot{,-i386}
tools/xm-test/ramdisk/Makefile.am | 2 tools/xm-test/ramdisk/configs/buildroot | 330 ------------------- tools/xm-test/ramdisk/configs/buildroot-i386 | 330 +++++++++++++++++++ 3 files changed, 331 insertions(+), 331 deletions(-)
tools/xm-test/ramdisk/Makefile.am +1 -1
@@ -31,7 +31,7 @@ endif tar xjf $(BR_TAR) $(BR_IMG): $(BR_SRC) - cp configs/buildroot $(BR_SRC)/.config + cp configs/buildroot-$(BR_ARCH) $(BR_SRC)/.config cp configs/busybox $(BR_SRC)/package/busybox/busybox.config cp configs/uClibc $(BR_SRC)/toolchain/uClibc/uClibc.config (for i in patches/buildroot/*.patch; do \
tools/xm-test/ramdisk/configs/buildroot-i386 new file +330 -0
330 lines not on this page · raw message
tools/xm-test/ramdisk/configs/buildroot deleted +0 -330
330 lines not on this page · raw message
PATCH 4/6 Update .hgignore to remove artifacts of ramdisk build
In reply to Tony BreedsUpdate .hgignore to remove artifacts of ramdisk build.
---
.hgignore | 9 +++++++++
1 file changed, 9 insertions(+)
.hgignore +9 -0
@@ -181,6 +181,15 @@ ^tools/xentrace/xenctx$ ^tools/xentrace/xentrace$ ^tools/xm-test/ramdisk/buildroot +^tools/xm-test/aclocal.m4$ +^tools/xm-test/autom4te +^tools/xm-test/install-sh$ +^tools/xm-test/missing$ +^tools/xm-test/config(ure|.log|.status)$ +^tools/xm-test/Makefile(.in)*$ +^tools/xm-test/.*/Makefile(.in)*$ +^tools/xm-test/lib/XmTestLib/config.py$ +^tools/xm-test/lib/XmTestReport/xmtest.py$ ^xen/BLOG$ ^xen/TAGS$ ^xen/arch/x86/asm-offsets\.s$
PATCH 5/6 Refactor code to encapsulate architecture decisions in one place
In reply to Tony BreedsRefactor code to encapsulate architecture decisions in one place.
Also includes some whitespace fixes.
---
tools/xm-test/lib/XmTestLib/XenDomain.py | 72 +++----------- tools/xm-test/lib/XmTestLib/arch.py | 103 +++++++++++++++++++++ tools/xm-test/lib/XmTestReport/OSReport.py | 10 -- tools/xm-test/lib/XmTestReport/arch.py | 42 ++++++++ 4 files changed, 163 insertions(+), 64 deletions(-)
tools/xm-test/lib/XmTestLib/XenDomain.py +16 -56
@@ -20,33 +20,25 @@ import sys import commands -import os import re import time from Xm import * +from arch import * from Test import * from config import * from Console import * from XenDevice import * -BLOCK_ROOT_DEV = "hda" def getDeviceModel(): - """Get the path to the device model based on - the architecture reported in uname""" - arch = os.uname()[4] - if re.search("64", arch): - return "/usr/lib64/xen/bin/qemu-dm" - else: - return "/usr/lib/xen/bin/qemu-dm" + return arch.getDeviceModel() def getDefaultKernel(): - """Get the path to the default DomU kernel""" - dom0Ver = commands.getoutput("uname -r"); - domUVer = dom0Ver.replace("xen0", "xenU"); - - return "/boot/vmlinuz-" + domUVer; + return arch.getDefaultKernel() + +def getRdPath(): + return arch.getRdPath() def getUniqueName(): """Get a uniqueish name for use in a domain"""
@@ -55,43 +47,8 @@ def getUniqueName(): test_name = re.sub("\.test", "", test_name) test_name = re.sub("[\/\.]", "", test_name) name = "%s-%i" % (test_name, unixtime) - + return name - -def getRdPath(): - rdpath = os.environ.get("RD_PATH") - if not rdpath: - rdpath = "../../ramdisk" - rdpath = os.path.abspath(rdpath) - - return rdpath - -ParavirtDefaults = {"memory" : 64, - "vcpus" : 1, - "kernel" : getDefaultKernel(), - "root" : "/dev/ram0", - "ramdisk" : getRdPath() + "/initrd.img" - } -HVMDefaults = {"memory" : 64, - "vcpus" : 1, - "acpi" : 0, - "apic" : 0, - "disk" : ["file:%s/disk.img,ioemu:%s,w!" % - (getRdPath(), BLOCK_ROOT_DEV)], - "kernel" : "/usr/lib/xen/boot/hvmloader", - "builder" : "hvm", - "sdl" : 0, - "vnc" : 0, - "vncviewer" : 0, - "nographic" : 1, - "serial" : "pty", - "device_model" : getDeviceModel() - } - -if ENABLE_HVM_SUPPORT: - configDefaults = HVMDefaults -else: - configDefaults = ParavirtDefaults class XenConfig: """An object to help create a xen-compliant config file"""
@@ -140,7 +97,8 @@ class XenConfig: def setOpt(self, name, value): """Set an option in the config""" - if name in self.opts.keys() and isinstance(self.opts[name], list) and not isinstance(value, list): + if name in self.opts.keys() and isinstance(self.opts[name] , + list) and not isinstance(value, list): self.opts[name] = [value] else: self.opts[name] = value
@@ -177,7 +135,7 @@ class DomainError(Exception): self.errorcode = int(errorcode) except Exception, e: self.errorcode = -1 - + def __str__(self): return str(self.msg)
@@ -199,7 +157,7 @@ class XenDomain: self.devices = {} self.netEnv = "bridge" - # Set domain type, either PV for ParaVirt domU or HVM for + # Set domain type, either PV for ParaVirt domU or HVM for # FullVirt domain if ENABLE_HVM_SUPPORT: self.type = "HVM"
@@ -332,7 +290,8 @@ class XenDomain: class XmTestDomain(XenDomain): - def __init__(self, name=None, extraConfig=None, baseConfig=configDefaults): + def __init__(self, name=None, extraConfig=None, + baseConfig=arch.configDefaults): """Create a new xm-test domain @param name: The requested domain name @param extraConfig: Additional configuration options
@@ -351,11 +310,12 @@ class XmTestDomain(XenDomain): XenDomain.__init__(self, config.getOpt("name"), config=config) def minSafeMem(self): - return 32 + return arch.minSafeMem class XmTestNetDomain(XmTestDomain): - def __init__(self, name=None, extraConfig=None, baseConfig=configDefaults): + def __init__(self, name=None, extraConfig=None, + baseConfig=arch.configDefaults): """Create a new xm-test domain with one network device @param name: The requested domain name @param extraConfig: Additional configuration options
tools/xm-test/lib/XmTestReport/OSReport.py +2 -8
@@ -29,6 +29,7 @@ import os import os import commands import sys +import arch class Machine:
@@ -89,8 +90,6 @@ class Machine: self.values = {} self.errors = 0 - cpuValues = {"model_name" : "Unknown", - "flags" : "Unknown"} xenValues = {"nr_cpus" : "Unknown", "nr_nodes" : "Unknown", "sockets_per_node" : "Unknown",
@@ -100,12 +99,7 @@ class Machine: "total_memory" : "Unknown"} xen = self.__getXenInfo(xenValues) - cpu = self.__getCpuInfo(cpuValues) - - if cpu["model_name"] == "Unknown": - cpuValues={"arch" : "Unknown", - "features": "Unknown"} - cpu=self.__getCpuInfo(cpuValues) + cpu = self.__getCpuInfo(arch.cpuValues) for k in xen.keys(): self.values[k] = xen[k]
tools/xm-test/lib/XmTestLib/arch.py new file +103 -0
103 lines not on this page · raw message
tools/xm-test/lib/XmTestReport/arch.py new file +42 -0
42 lines not on this page · raw message
PATCH 6/6 Add configuration data for powerpc
In reply to Tony BreedsAdd configuration data for powerpc.
Allows for building of initrd, and running of tests.
---
tools/xm-test/lib/XmTestLib/arch.py | 30 + tools/xm-test/lib/XmTestReport/arch.py | 6 tools/xm-test/ramdisk/Makefile.am | 2 tools/xm-test/ramdisk/configs/buildroot-powerpc | 334 ++++++++++++++++ 4 files changed, 371 insertions(+), 1 deletion(-)
tools/xm-test/lib/XmTestLib/arch.py +30 -0
@@ -80,6 +80,29 @@ ia_HVMDefaults = {"memory" : } # End : Intel ia32 and ia64 as well as AMD 32-bit and 64-bit processors +# Begin: PowerPC +def ppc_minSafeMem(): + return 64 + +def ppc_getDeviceModel(): + return "/usr/lib64/xen/bin/qemu-dm" + +def ppc_getDefaultKernel(): + """Get the path to the default DomU kernel""" + dom0Ver = commands.getoutput("uname -r"); + domUVer = dom0Ver.replace("xen0", "xenU"); + + return "/boot/vmlinux-" + domUVer; + +ppc_ParavirtDefaults = {"memory" : 64, + "vcpus" : 1, + "kernel" : ppc_getDefaultKernel(), + "root" : "/dev/ram0", + "ramdisk" : getRdPath() + "/initrd.img", + "extra" : "xencons=tty128 console=tty128", +} +# End : PowerPC + """Convert from uname specification to a more general platform.""" _uanme_to_arch_map = { "i386" : "x86",
@@ -87,6 +110,8 @@ _uanme_to_arch_map = { "i586" : "x86", "i686" : "x86", "ia64" : "ia64", + "ppc" : "powerpc", + "ppc64" : "powerpc", } # Lookup current platform.
@@ -99,5 +124,10 @@ if _arch == "x86" or _arch == "ia64": configDefaults = ia_HVMDefaults else: configDefaults = ia_ParavirtDefaults +elif _arch == "powerpc": + minSafeMem = ppc_minSafeMem + getDeviceModel = ppc_getDeviceModel + getDefaultKernel = ppc_getDefaultKernel + configDefaults = ppc_ParavirtDefaults else: raise ValueError, "Unknown architecture!"
tools/xm-test/lib/XmTestReport/arch.py +6 -0
@@ -29,6 +29,8 @@ _uanme_to_arch_map = { "i586" : "x86", "i686" : "x86", "ia64" : "ia64", + "ppc" : "powerpc", + "ppc64" : "powerpc", } _arch = _uanme_to_arch_map.get(os.uname()[4], "Unknown")
@@ -38,5 +40,9 @@ elif _arch == "ia64": elif _arch == "ia64": cpuValues = {"arch" : "Unknown", "features" : "Unknown"} +elif _arch == "powerpc": + cpuValues = {"cpu" : "Unknown", + "platform" : "Unknown", + "revision" : "Unknown"} else: raise ValueError, "Unknown architecture!"
tools/xm-test/ramdisk/Makefile.am +1 -1
@@ -2,7 +2,7 @@ INITRD ?= http://xm-test.xensource.com/r EXTRA_DIST = skel configs patches -BR_ARCH = $(shell uname -m | sed -e s/i.86/i386/) +BR_ARCH = $(shell uname -m | sed -e s/i.86/i386/ -e 's/ppc\(64\)*/powerpc/') BR_TAR = buildroot-snapshot.tar.bz2 BR_URL = http://buildroot.uclibc.org/downloads/snapshots/$(BR_TAR)
tools/xm-test/ramdisk/configs/buildroot-powerpc new file +334 -0
334 lines not on this page · raw message
Re: [XenPPC] [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc
couple things
Quoted 24 lines · Tony Breeds
Add configuration data for powerpc.
Allows for building of initrd, and running of tests.
Signed-off-by Tony Breeds <[email protected]>---
tools/xm-test/lib/XmTestLib/arch.py | 30 + tools/xm-test/lib/XmTestReport/arch.py | 6 tools/xm-test/ramdisk/Makefile.am | 2 tools/xm-test/ramdisk/configs/buildroot-powerpc | 334 +++++++++++++ +++ 4 files changed, 371 insertions(+), 1 deletion(-)diff -r
989b397808f8-r82402a95e380tools/xm-test/lib/XmTestLib/arch.py
---a/tools/xm-test/lib/XmTestLib/arch.pyFri Sep 29 17:11:31 2006
+1000
+++b/tools/xm-test/lib/XmTestLib/arch.pyFri Sep 29 20:52:32 2006
+1000(quoted diff) +0
-0@@ -80,6 +80,29 @@ ia_HVMDefaults = {"memory" : } # End : Intel ia32 and ia64 as well as AMD 32-bit and 64-bitprocessors
tools/xm-test/lib/XmTestLib/arch.py ia_HVMDefaults = {"memory" : · line 88
Quoted 6 lines
tools/xm-test/lib/XmTestLib/arch.py +6
-0+# Begin: PowerPC +def ppc_minSafeMem(): + return 64 + +def ppc_getDeviceModel(): + return "/usr/lib64/xen/bin/qemu-dm"
This can not be correct, I suppose it should return nothing?
Quoted 21 lines
tools/xm-test/lib/XmTestLib/arch.py +17
-0+ +def ppc_getDefaultKernel(): + """Get the path to the default DomU kernel""" + dom0Ver = commands.getoutput("uname -r"); + domUVer = dom0Ver.replace("xen0", "xenU"); + + return "/boot/vmlinux-" + domUVer; + +ppc_ParavirtDefaults = {"memory" : 64, + "vcpus" : 1, + "kernel" : ppc_getDefaultKernel(), + "root" : "/dev/ram0", + "ramdisk" : getRdPath() + "/initrd.img", + "extra" : "xencons=tty128 console=tty128", +} +# End : PowerPC + """Convert from uname specification to a more general platform.""" _uanme_to_arch_map = { "i386" : "x86",
tools/xm-test/lib/XmTestLib/arch.py _uanme_to_arch_map = { · line 116
Quoted 7 lines
tools/xm-test/lib/XmTestLib/arch.py +2
-0@@ -87,6 +110,8 @@ _uanme_to_arch_map = { "i586" : "x86", "i686" : "x86", "ia64" : "ia64", + "ppc" : "powerpc", + "ppc64" : "powerpc", }
_uanme this must be one pervasive typo
Quoted 18 lines
tools/xm-test/lib/XmTestLib/arch.py +5
-0# Lookup current platform.@@ -99,5 +124,10 @@ if _arch == "x86" or _arch == "ia64": configDefaults = ia_HVMDefaults else: configDefaults = ia_ParavirtDefaults +elif _arch == "powerpc": + minSafeMem = ppc_minSafeMem + getDeviceModel = ppc_getDeviceModel + getDefaultKernel = ppc_getDefaultKernel + configDefaults = ppc_ParavirtDefaults else: raise ValueError, "Unknown architecture!"diff -r
989b397808f8-r82402a95e380tools/xm-test/lib/XmTestReport/arch.py
---a/tools/xm-test/lib/XmTestReport/arch.pyFri Sep 29 17:11:31
2006 +1000
+++b/tools/xm-test/lib/XmTestReport/arch.pyFri Sep 29 20:52:32
2006 +1000
tools/xm-test/lib/XmTestLib/arch.py _uanme_to_arch_map = { · line 34
Quoted 6 lines
tools/xm-test/lib/XmTestLib/arch.py +2
-0@@ -29,6 +29,8 @@ _uanme_to_arch_map = { "i586" : "x86", "i686" : "x86", "ia64" : "ia64", + "ppc" : "powerpc", + "ppc64" : "powerpc", }
_uanme again, even that japanese to english dictionary doesn't know what it is :)
Quoted 371 lines
tools/xm-test/lib/XmTestReport/arch.py +4
-0_arch = _uanme_to_arch_map.get(os.uname()[4], "Unknown")@@ -38,5 +40,9 @@ elif _arch == "ia64": elif _arch == "ia64": cpuValues = {"arch" : "Unknown", "features" : "Unknown"} +elif _arch == "powerpc": + cpuValues = {"cpu" : "Unknown", + "platform" : "Unknown", + "revision" : "Unknown"} else: raise ValueError, "Unknown architecture!"diff -r
989b397808f8-r82402a95e380tools/xm-test/ramdisk/Makefile.amtools/xm-test/ramdisk/Makefile.am +1
-1@@ -2,7 +2,7 @@ INITRD ?= http://xm-test.xensource.com/r EXTRA_DIST = skel configs patches -BR_ARCH = $(shell uname -m | sed -e s/i.86/i386/) +BR_ARCH = $(shell uname -m | sed -e s/i.86/i386/ -e 's/ppc\(64\)*/ powerpc/') BR_TAR = buildroot-snapshot.tar.bz2
BR_URL= http://buildroot.uclibc.org/downloads/snapshots/$(BR_TAR)
diff -r989b397808f8-r82402a95e380tools/xm-test/ramdisk/configs/buildroot-powerpctools/xm-test/ramdisk/configs/buildroot-powerpc new file +0
-020:52:32 2006 +1000
tools/xm-test/ramdisk/configs/buildroot-powerpc new file +334
-0@@ -0,0 +1,334 @@ +# +# Automatically generated make config: don't edit +# +BR2_HAVE_DOT_CONFIG=y +# BR2_alpha is not set +# BR2_arm is not set +# BR2_armeb is not set +# BR2_cris is not set +# BR2_i386 is not set +# BR2_m68k is not set +# BR2_mips is not set +# BR2_mipsel is not set +# BR2_nios2 is not set +BR2_powerpc=y +# BR2_sh is not set +# BR2_sh64 is not set +# BR2_sparc is not set +# BR2_x86_64 is not set +# BR2_x86_i386 is not set +# BR2_x86_i486 is not set +# BR2_x86_i586 is not set +# BR2_x86_i686 is not set +BR2_ARCH="powerpc" +BR2_ENDIAN="BIG" + +# +# Build options +# +BR2_WGET="wget --passive-ftp" +BR2_SVN="svn co" +BR2_TAR_OPTIONS="" +BR2_DL_DIR="$(BASE_DIR)/dl" +BR2_SOURCEFORGE_MIRROR="easynews" +BR2_STAGING_DIR="$(BUILD_DIR)/staging_dir" +BR2_TOPDIR_PREFIX="" +BR2_TOPDIR_SUFFIX="" +BR2_GNU_BUILD_SUFFIX="pc-linux-gnu" +BR2_GNU_TARGET_SUFFIX="linux-uclibc" +BR2_JLEVEL=1 + +# +# Toolchain Options +# + +# +# Kernel Header Options +# +# BR2_KERNEL_HEADERS_2_4_25 is not set +# BR2_KERNEL_HEADERS_2_4_27 is not set +# BR2_KERNEL_HEADERS_2_4_29 is not set +# BR2_KERNEL_HEADERS_2_4_31 is not set +# BR2_KERNEL_HEADERS_2_6_9 is not set +# BR2_KERNEL_HEADERS_2_6_11 is not set +BR2_KERNEL_HEADERS_2_6_12=y +BR2_DEFAULT_KERNEL_HEADERS="2.6.12" + +# +# uClibc Options +# +# BR2_UCLIBC_VERSION_SNAPSHOT is not set +# BR2_ENABLE_LOCALE is not set +# BR2_PTHREADS_NONE is not set +# BR2_PTHREADS is not set +BR2_PTHREADS_OLD=y +# BR2_PTHREADS_NATIVE is not set + +# +# Binutils Options +# +# BR2_BINUTILS_VERSION_2_14_90_0_8 is not set +# BR2_BINUTILS_VERSION_2_15 is not set +# BR2_BINUTILS_VERSION_2_15_94_0_2_2 is not set +# BR2_BINUTILS_VERSION_2_16_1 is not set +# BR2_BINUTILS_VERSION_2_16_90_0_3 is not set +# BR2_BINUTILS_VERSION_2_16_91_0_5 is not set +# BR2_BINUTILS_VERSION_2_16_91_0_6 is not set +# BR2_BINUTILS_VERSION_2_16_91_0_7 is not set +BR2_BINUTILS_VERSION_2_17=y +# BR2_BINUTILS_VERSION_2_17_50_0_2 is not set +# BR2_BINUTILS_VERSION_2_17_50_0_3 is not set +BR2_BINUTILS_VERSION="2.17" +BR2_EXTRA_BINUTILS_CONFIG_OPTIONS="" + +# +# Gcc Options +# +# BR2_GCC_VERSION_3_3_5 is not set +# BR2_GCC_VERSION_3_3_6 is not set +BR2_GCC_VERSION_3_4_2=y +# BR2_GCC_VERSION_3_4_3 is not set +# BR2_GCC_VERSION_3_4_4 is not set +# BR2_GCC_VERSION_3_4_5 is not set +# BR2_GCC_VERSION_3_4_6 is not set +# BR2_GCC_VERSION_4_0_0 is not set +# BR2_GCC_VERSION_4_0_1 is not set +# BR2_GCC_VERSION_4_0_2 is not set +# BR2_GCC_VERSION_4_0_3 is not set +# BR2_GCC_VERSION_4_1_0 is not set +# BR2_GCC_VERSION_4_1_1 is not set +# BR2_GCC_VERSION_4_2 is not set +# BR2_GCC_IS_SNAP is not set +BR2_GCC_VERSION="3.4.2" +# BR2_GCC_USE_SJLJ_EXCEPTIONS is not set +BR2_EXTRA_GCC_CONFIG_OPTIONS="" +# BR2_INSTALL_LIBSTDCPP is not set +# BR2_INSTALL_OBJC is not set + +# +# Ccache Options +# +BR2_CCACHE=y + +# +# Gdb Options +# +# BR2_PACKAGE_GDB is not set +# BR2_PACKAGE_GDB_SERVER is not set +# BR2_PACKAGE_GDB_HOST is not set + +# +# elf2flt +# +# BR2_ELF2FLT is not set +# BR2_MKLIBS is not set + +# +# Common Toolchain Options +# +# BR2_PACKAGE_SSTRIP_TARGET is not set +# BR2_PACKAGE_SSTRIP_HOST is not set +BR2_ENABLE_MULTILIB=y +BR2_LARGEFILE=y +# BR2_SOFT_FLOAT is not set +BR2_TARGET_OPTIMIZATION="-Os -pipe" +BR2_CROSS_TOOLCHAIN_TARGET_UTILS=y + +# +# Package Selection for the target +# + +# +# The default minimal system +# +BR2_PACKAGE_BUSYBOX=y +# BR2_PACKAGE_BUSYBOX_SNAPSHOT is not set +BR2_PACKAGE_BUSYBOX_INSTALL_SYMLINKS=y +BR2_PACKAGE_BUSYBOX_CONFIG="package/busybox/busybox.config" + +# +# The minimum needed to build a uClibc development system +# +# BR2_PACKAGE_BASH is not set +# BR2_PACKAGE_BZIP2 is not set +# BR2_PACKAGE_COREUTILS is not set +# BR2_PACKAGE_DIFFUTILS is not set +# BR2_PACKAGE_ED is not set +# BR2_PACKAGE_FINDUTILS is not set +# BR2_PACKAGE_FLEX is not set +# BR2_PACKAGE_GAWK is not set +# BR2_PACKAGE_GCC_TARGET is not set +# BR2_PACKAGE_CCACHE_TARGET is not set +# BR2_PACKAGE_GREP is not set +# BR2_PACKAGE_MAKE is not set +# BR2_PACKAGE_PATCH is not set +# BR2_PACKAGE_SED is not set +# BR2_PACKAGE_TAR is not set + +# +# Other stuff +# +# BR2_PACKAGE_ACPID is not set +# BR2_PACKAGE_ASTERISK is not set +# BR2_PACKAGE_AT is not set +# BR2_PACKAGE_AUTOCONF is not set +# BR2_PACKAGE_AUTOMAKE is not set +# BR2_PACKAGE_BERKELEYDB is not set +# BR2_PACKAGE_BIND is not set +# BR2_PACKAGE_BISON is not set +# BR2_PACKAGE_BOA is not set +# BR2_PACKAGE_BRIDGE is not set +# BR2_PACKAGE_CUSTOMIZE is not set +# BR2_PACKAGE_ISC_DHCP is not set +# BR2_PACKAGE_DIALOG is not set +# BR2_PACKAGE_DIRECTFB is not set +# BR2_PACKAGE_DISTCC is not set +# BR2_PACKAGE_DM is not set +# BR2_PACKAGE_DMRAID is not set +# BR2_PACKAGE_DNSMASQ is not set +# BR2_PACKAGE_DROPBEAR is not set +# BR2_PACKAGE_ETHTOOL is not set +# BR2_PACKAGE_EXPAT is not set +# BR2_PACKAGE_E2FSPROGS is not set +# BR2_PACKAGE_FAKEROOT is not set +# BR2_PACKAGE_FILE is not set +# BR2_PACKAGE_FREETYPE is not set +# BR2_PACKAGE_GETTEXT is not set +# BR2_PACKAGE_LIBINTL is not set +# BR2_PACKAGE_GZIP is not set +# BR2_PACKAGE_HASERL is not set +# BR2_PACKAGE_HDPARM is not set +# BR2_PACKAGE_HOSTAP is not set +# BR2_PACKAGE_HOTPLUG is not set +# BR2_PACKAGE_IOSTAT is not set +# BR2_PACKAGE_IPROUTE2 is not set +# BR2_PACKAGE_IPSEC_TOOLS is not set +# BR2_PACKAGE_IPTABLES is not set +# BR2_PACKAGE_JPEG is not set +# BR2_PACKAGE_LESS is not set +# BR2_PACKAGE_LIBCGI is not set +# BR2_PACKAGE_LIBCGICC is not set +# BR2_PACKAGE_LIBELF is not set +# BR2_PACKAGE_LIBFLOAT is not set +# BR2_PACKAGE_LIBGLIB12 is not set +# BR2_PACKAGE_LIBMAD is not set +# BR2_PACKAGE_LIBPCAP is not set +# BR2_PACKAGE_LIBPNG is not set +# BR2_PACKAGE_LIBSYSFS is not set +# BR2_PACKAGE_LIBTOOL is not set +# BR2_PACKAGE_LIBUSB is not set +# BR2_PACKAGE_LIGHTTPD is not set +# BR2_PACKAGE_LINKS is not set +# BR2_PACKAGE_LRZSZ is not set +# BR2_PACKAGE_LSOF is not set +# BR2_PACKAGE_LTP-TESTSUITE is not set +# BR2_PACKAGE_LTT is not set +# BR2_PACKAGE_LVM2 is not set +# BR2_PACKAGE_LZO is not set +# BR2_PACKAGE_LZMA is not set +# BR2_PACKAGE_M4 is not set +# BR2_PACKAGE_MDADM is not set +# BR2_PACKAGE_MEMTESTER is not set +# BR2_PACKAGE_MICROCOM is not set +# BR2_PACKAGE_MICROPERL is not set +# BR2_PACKAGE_MICROWIN is not set +# BR2_PACKAGE_MKDOSFS is not set +# BR2_PACKAGE_MODULE_INIT_TOOLS is not set +# BR2_PACKAGE_MODUTILS is not set +# BR2_PACKAGE_MPG123 is not set +# BR2_PACKAGE_MROUTED is not set +# BR2_PACKAGE_MTD is not set +# BR2_PACKAGE_NANO is not set +# BR2_PACKAGE_NCURSES is not set +# BR2_PACKAGE_NETKITBASE is not set +# BR2_PACKAGE_NETKITTELNET is not set +# BR2_PACKAGE_NETSNMP is not set +# BR2_PACKAGE_NEWT is not set +# BR2_PACKAGE_NTP is not set +# BR2_PACKAGE_OPENNTPD is not set +# BR2_PACKAGE_OPENSSH is not set +# BR2_PACKAGE_OPENSSL is not set +# BR2_PACKAGE_OPENVPN is not set +# BR2_PACKAGE_PCIUTILS is not set +# BR2_PACKAGE_PKGCONFIG is not set +# BR2_PACKAGE_PORTAGE is not set +# BR2_PACKAGE_PORTMAP is not set +# BR2_PACKAGE_PPPD is not set +# BR2_PACKAGE_PROCPS is not set +# BR2_PACKAGE_PSMISC is not set +# BR2_PACKAGE_PYTHON is not set +# BR2_PACKAGE_QTE is not set +BR2_QTE_TMAKE_VERSION="1.13" +# BR2_PACKAGE_RAIDTOOLS is not set +# BR2_READLINE is not set +# BR2_PACKAGE_RSYNC is not set +# BR2_PACKAGE_RUBY is not set +# BR2_PACKAGE_RXVT is not set +# BR2_PACKAGE_SDL is not set +# BR2_PACKAGE_SFDISK is not set +# BR2_PACKAGE_SLANG is not set +# BR2_PACKAGE_SMARTMONTOOLS is not set +# BR2_PACKAGE_SOCAT is not set +# BR2_PACKAGE_STRACE is not set +# BR2_PACKAGE_SUDO is not set +# BR2_PACKAGE_SYSKLOGD is not set +# BR2_PACKAGE_SYSVINIT is not set +# BR2_PACKAGE_TCL is not set +# BR2_PACKAGE_TCPDUMP is not set +# BR2_PACKAGE_TFTPD is not set +# BR2_PACKAGE_THTTPD is not set +# BR2_PACKAGE_TINYLOGIN is not set +# BR2_PACKAGE_TINYX is not set +# BR2_PACKAGE_TN5250 is not set +# BR2_PACKAGE_TTCP is not set +# BR2_PACKAGE_UDEV is not set +# BR2_PACKAGE_UDHCP is not set +# BR2_PACKAGE_UEMACS is not set +# BR2_PACKAGE_USBUTILS is not set +# BR2_PACKAGE_UTIL-LINUX is not set +# BR2_PACKAGE_VALGRIND is not set +# BR2_PACKAGE_VTUN is not set +# BR2_PACKAGE_WGET is not set +# BR2_PACKAGE_WHICH is not set +# BR2_PACKAGE_WIPE is not set +# BR2_PACKAGE_WIRELESS_TOOLS is not set +# BR2_PACKAGE_XFSPROGS is not set +# BR2_PACKAGE_ZLIB is not set +BR2_PACKAGE_HPING=y + +# +# Target Options +# + +# +# filesystem for target device +# +# BR2_TARGET_ROOTFS_CRAMFS is not set +# BR2_TARGET_ROOTFS_CLOOP is not set +BR2_TARGET_ROOTFS_EXT2=y +BR2_TARGET_ROOTFS_EXT2_BLOCKS=0 +BR2_TARGET_ROOTFS_EXT2_INODES=0 +BR2_TARGET_ROOTFS_EXT2_RESBLKS=0 +BR2_TARGET_ROOTFS_EXT2_SQUASH=y +BR2_TARGET_ROOTFS_EXT2_OUTPUT="$(IMAGE).ext2" +# BR2_TARGET_ROOTFS_EXT2_GZ is not set +BR2_TARGET_ROOTFS_EXT2_COPYTO="" +# BR2_TARGET_ROOTFS_JFFS2 is not set +# BR2_TARGET_ROOTFS_SQUASHFS is not set +# BR2_TARGET_ROOTFS_TAR is not set + +# +# bootloader for target device +# +# BR2_TARGET_YABOOT is not set + +# +# Board Support Options +# + +# +# Generic System Support +# +# BR2_TARGET_GENERIC_ACCESS_POINT is not set +# BR2_TARGET_GENERIC_FIREWALL is not set +# BR2_TARGET_GENERIC_DEV_SYSTEM is not set_______________________________________________
Xen-ppc-devel mailing list
[email protected]
http://lists.xensource.com/xen-ppc-devel
Re: [XenPPC] [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc
Quoted 1 line · Jimi Xenidis
This can not be correct, I suppose it should return nothing?
okay. Looking at the callers for getDeviceModel, it's only needed for HVM domains and the method/function is only used inside arch.py so I've pruned it from XenDomain and consequently it's unneeded at all in PPC.
Quoted 1 line
_uanmethis must be one pervasive typo
Hmm, typo x 1, copy-n-paste x lots.
Quoted 2 lines
_uanmeagain, even that japanese to english dictionary doesn't know what it is :)
It's a horse. http://www.pedigreequery.com/uanme ;P
I'll post an updated set of patches shortly.
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2007.linux.org.au/
Jan 15-20 2007 The Australian Linux Technical Conference!
Re: [XenPPC] [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc
Quoted 8 lines · Tony Breeds
Quoted 1 line · Jimi Xenidis
This can not be correct, I suppose it should return nothing?
okay. Looking at the callers for getDeviceModel, it's only needed for HVM domains and the method/function is only used inside
arch.pyso I've pruned it from XenDomain and consequently it's unneeded at all in PPC.
I cannot actually find any callers?!
Dan,Sean, that makes sense?
-JX
Re: [XenPPC] [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc
JX> I cannot actually find any callers?! Dan,Sean, that makes sense?
Actually, Dan Stekloff did most of the HVM work for xm-test, so he would know better than I.
I would guess that the function is cruft leftover from before we moved to the larger domain abstraction.
Signature · 4 lines
Dan Smith IBM Linux Technology Center Open Hypervisor Team email: [email protected]
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Re: [XenPPC] [PATCH 6/6][TOOLS][XM-TEST] Add configuration data for powerpc
Quoted 7 lines · Dan Smith
JX> I cannot actually find any callers?! Dan,Sean, that makes sense?
Actually, Dan Stekloff did most of the HVM work for xm-test, so he would know better than I.
I would guess that the function is cruft leftover from before we moved to the larger domain abstraction.
There is only one caller - HVMDefaults/ia_HVMDefaults, the default config for creating HVM domains. It's only useful for HVM domains and defines where the device model is.
Thanks,
Dan
Keir, I whole heartedly ACK these patches.
If you plan to wait until the flood gates open again, then please advise and we'll integrate into xenppc-unstable and deal with the merge later.
Thanks,
-JX
Quoted 56 lines · Tony Breeds
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus of this endeavor is PPC but I believe that IA64 also benefits.Patch summary:
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.
2: Remove hardcoded references to i386.
3: Rename configs/buildroot -> configs/buildroot-i386
and update Makefiles.
5: Update .hgignore to remove noise from the initrd building process 5: Refactor the XmTestLib and XmTestReport code to encapsulate all
platform variations in one place.
6: FYI: Add powerpc definitions.
This patch is for the XenPPC tree but included here for
comments and
completeness.With these patches applied I'm still able to build an initrd and run the xm-test on x86 with no regressions.
Updated to address feedback from Jimi Xenidis.
Feedback appreciated.Signed-off-by Tony Breeds <[email protected]>---
.hgignore | 9 tools/xm-test/lib/XmTestLib/XenDomain.py | 73 --- tools/xm-test/lib/XmTestLib/arch.py | 128 ++++++ tools/xm-test/lib/XmTestReport/OSReport.py | 10 tools/xm-test/lib/XmTestReport/arch.py | 48 ++ tools/xm-test/ramdisk/Makefile.am | 11 tools/xm-test/ramdisk/configs/buildroot | 330 --------------- tools/xm-test/ramdisk/configs/buildroot-i386 | 330 ++++++++++++ +++ tools/xm-test/ramdisk/configs/buildroot-powerpc | 334 ++++++++++++ ++++ 9 files changed, 872 insertions(+), 401 deletions(-)Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2007.linux.org.au/
Jan 15-20 2007 The Australian Linux Technical Conference!_______________________________________________
Xen-ppc-devel mailing list
[email protected]
http://lists.xensource.com/xen-ppc-devel
Quoted 9 lines · Tony Breeds
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus of this endeavor is PPC but I believe that IA64 also benefits.Patch summary:
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.
The last time I built a xm-test ramdisk, the buildroot-snapshot was broken, and I had to go back a few days to find a working one. I'm wary of using buildroot-snapshot for that reason. Does anyone work within the buildroot community? Perhaps we could persuade them to keep "released" versions around, rather than just the expiring, daily snapshots?
Ewan.
Quoted 9 lines · Ewan Mellor
Quoted 7 lines · Tony Breeds
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus of this endeavor is PPC but I believe that IA64 also benefits.Patch summary:
Quoted 8 lines
Quoted 2 lines
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.The last time I built a xm-test ramdisk, the buildroot-snapshot was broken, and I had to go back a few days to find a working one. I'm wary of using buildroot-snapshot for that reason. Does anyone work within the buildroot community? Perhaps we could persuade them to keep "released" versions around, rather than just the expiring, daily snapshots?
If the Xen community will be "blessing" a known version perhaps we should keep it somewhere independent of the buildroot community? Maybe hang it off http://wiki.xensource.com/xenwiki/XmTest as an attachment?
-JX
EM> The last time I built a xm-test ramdisk, the buildroot-snapshot EM> was broken, and I had to go back a few days to find a working one. EM> I'm wary of using buildroot-snapshot for that reason.
Yes, we had this discussion last year sometime and agreed to use a known-good daily snapshot for that reason. I think it's still a good idea, as most people are not (or should not be) building ramdisks anymore (now that Xensource hosts a binary for download).
Signature · 4 lines
Dan Smith IBM Linux Technology Center Open Hypervisor Team email: [email protected]
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 8 lines · Dan Smith
EM> The last time I built a xm-test ramdisk, the buildroot-snapshot EM> was broken, and I had to go back a few days to find a working one. EM> I'm wary of using buildroot-snapshot for that reason.
Yes, we had this discussion last year sometime and agreed to use a known-good daily snapshot for that reason. I think it's still a good idea, as most people are not (or should not be) building ramdisks anymore (now that Xensource hosts a binary for download).
Yes, I think that the best thing to do would be as Jimi suggests, and for us to pick one known-good snapshot, and host it ourselves. That way, the source for the XenSource ramdisks will always be available and we don't have to rely upon the upstream buildroot archive.
The next time I build a ramdisk I'll put the buildroot tar on xm-test.xensource.com, and change the Makefile to refer to that instead.
Ewan.
Quoted 11 lines · Ewan Mellor
Quoted 8 lines · Dan Smith
EM> The last time I built a xm-test ramdisk, the buildroot-snapshot EM> was broken, and I had to go back a few days to find a working one. EM> I'm wary of using buildroot-snapshot for that reason.
Yes, we had this discussion last year sometime and agreed to use a known-good daily snapshot for that reason. I think it's still a good idea, as most people are not (or should not be) building ramdisks anymore (now that Xensource hosts a binary for download).
Quoted 7 lines
Yes, I think that the best thing to do would be as Jimi suggests, and for us to pick one known-good snapshot, and host it ourselves. That way, the source for the XenSource ramdisks will always be available and we don't have to rely upon the upstream buildroot archive.
The next time I build a ramdisk I'll put the buildroot tar on xm-test.xensource.com, and change the
Makefileto refer to that instead.
Thanks Ewan,
Could you also make sure that the Arch maintainers have the ability to upload images as well? -JX
Quoted 2 lines · Jimi Xenidis
Could you also make sure that the Arch maintainers have the ability to upload images as well?
Um, I don't know, I'll have to check.
XenSource started hosting these images rather than IBM (as the primary xm-test authors) because of the difficulty you guys tend to have shipping binaries of GPL'd software. Are you sure that you would be able to upload images anyway? And if so, couldn't you just host them at your end?
Ewan.
Quoted 7 lines · Ewan Mellor
Yes, I think that the best thing to do would be as Jimi suggests, and for us to pick one known-good snapshot, and host it ourselves. That way, the source for the XenSource ramdisks will always be available and we don't have to rely upon the upstream buildroot archive.
The next time I build a ramdisk I'll put the buildroot tar on xm-test.xensource.com, and change the
Makefileto refer to that instead.
What about adding seomthing like:
BT_FILE=buildroot-snapshot
ifdef UCLIB
BT_SITE="... uclib ..."
else
BT_SITE="... xensource ..."endif
BT_URL="$(BT_SITE)/(BT_FILE)"
then have a buildroot-snapshot in xensource somewhere, this allows easy testing or the upstream snapshots make vs make UCLIB=1, and brace users automagically end up with a working buildroot if they trying to build there own ramdisks.
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2007.linux.org.au/
Jan 15-20 2007 The Australian Linux Technical Conference!
Quoted 9 lines · Ewan Mellor
Quoted 7 lines · Tony Breeds
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus of this endeavor is PPC but I believe that IA64 also benefits.Patch summary:
Quoted 8 lines
Quoted 2 lines
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.The last time I built a xm-test ramdisk, the buildroot-snapshot was broken, and I had to go back a few days to find a working one. I'm wary of using buildroot-snapshot for that reason. Does anyone work within the buildroot community? Perhaps we could persuade them to keep "released" versions around, rather than just the expiring, daily snapshots?
Ewan, if you have some problem with patch 1/6, could you still apply the rest to xen-unstable? 2/6 wouldn't apply cleanly, but should be easy to do by hand.
Signature · 2 lines
Hollis Blanchard IBM Linux Technology Center
Quoted 19 lines · Hollis Blanchard
Quoted 9 lines · Ewan Mellor
Quoted 7 lines · Tony Breeds
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus of this endeavor is PPC but I believe that IA64 also benefits.Patch summary:
Quoted 8 lines
Quoted 2 lines
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.The last time I built a xm-test ramdisk, the buildroot-snapshot was broken, and I had to go back a few days to find a working one. I'm wary of using buildroot-snapshot for that reason. Does anyone work within the buildroot community? Perhaps we could persuade them to keep "released" versions around, rather than just the expiring, daily snapshots?
Quoted 3 lines
Ewan, if you have some problem with patch 1/6, could you still apply the rest to xen-unstable? 2/6 wouldn't apply cleanly, but should be easy to do by hand.
I've got no particular problem with these patches (we'll host the buildroot tar on xenbits, which was the only query). The tree's feature-frozen now though -- we're at RC2 -- so these will drop in immediately after the release.
Ewan.
Quoted 11 lines · Ewan Mellor
Quoted 2 lines
Ewan, if you have some problem with patch 1/6, could you still apply
the
Quoted 1 line
rest to xen-unstable? 2/6 wouldn't apply cleanly, but should be easy
to
Quoted 1 line
do by hand.
I've got no particular problem with these patches (we'll host the buildroot tar on xenbits, which was the only query). The tree's feature-frozen now though -- we're at RC2 -- so these will drop in immediately after the release.
Which tree, xen-3.0.3-testing? I was asking about xen-unstable...
Signature · 2 lines
Hollis Blanchard IBM Linux Technology Center
Quoted 6 lines · Hollis Blanchard
Quoted 4 lines
I've got no particular problem with these patches (we'll host the buildroot tar on xenbits, which was the only query). The tree's feature-frozen now though -- we're at RC2 -- so these will drop in immediately after the release.
Which tree, xen-3.0.3-testing? I was asking about xen-unstable...
Xen-unstable is currently a staging tree for xen-3.0.3-testing. Development is frozen until 3.0.3-0 is released.
-- Keir
Keir Fraser wrote: [Tue Oct 03 2006, 11:59:28AM EDT]
Quoted 2 lines
Xen-unstable is currently a staging tree for xen-3.0.3-testing. Development is frozen until 3.0.3-0 is released.
Hi Keir,
Why are you doing it this way? I thought a staging tree was somewhere you could test builds prior to moving changesets to the live tree, so you could yank the changesets, reset the staging tree, etc. without affecting anybody. Shouldn't there be a separate staging tree for xen-3.0.3-testing? Plus if xen-unstable is staging for xen-3.0.3-testing, then it seems like branching was pointless.
Aron
Quoted 4 lines · Aron Griffis
Keir Fraser wrote: [Tue Oct 03 2006, 11:59:28AM EDT]
Quoted 2 lines
Xen-unstable is currently a staging tree for xen-3.0.3-testing. Development is frozen until 3.0.3-0 is released.
Quoted 8 lines
Hi Keir,
Why are you doing it this way? I thought a staging tree was somewhere you could test builds prior to moving changesets to the live tree, so you could yank the changesets, reset the staging tree, etc. without affecting anybody. Shouldn't there be a separate staging tree for xen-3.0.3-testing? Plus if xen-unstable is staging for xen-3.0.3-testing, then it seems like branching was pointless.
Since development is frozen to concentrate on bug fixing, we may as well use xen-unstable as the staging point for candidate patches rather than creating an entirely new tree. Creating an explicit xen-3.0.3-testing tree and announcing official release candidates encourages a broader range of people to test the code (many will not touch xen-unstable at all).
Development is not frozen because we are using xen-unstable as a staging tree. It is frozen simply because we are at the bug-fixing stage in the release cycle.
-- Keir
Quoted 19 lines · Tony Breeds
Hi All,
These patches update the xm-test code to be more easily portable
to new architecture. This focus od this endevour is PPC but I believe that IA64 also benifits.Patch summary:
1: Instead of using a dated snapshot (which no longer exists)
use buildroot-snapshot.
2: Remove hardcoded references to i386.
3: Rename configs/buildroot -> configs/buildroot-i386
and update Makefiles.
5: Update .hgignore to remove noise from the initrd building process 5: Refactor the XmTestLib and XmTestReport code to encapsulate all
platform variations in one place.
6: FYI: Add powerpc definiations.
This patch is for the xenppc tree but included here for comments and completeness.
Quoted 2 lines
With these patches applied I'm still able to build an initrd and run the xm-test on x86 with no regressions.
Have you run with HVM guests as well? Not that I think there's a problem...
Thanks,
Dan
Quoted 2 lines · Daniel Stekloff
Have you run with HVM guests as well? Not that I think there's a problem...
I don't have access to HVM hardware so I haven't been able to run those tests. Likewise I haven't tested it on ia64 and x86_64. I think for those platforms it just a code re-org.
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2007.linux.org.au/
Jan 15-20 2007 The Australian Linux Technical Conference!