[XenPPC] updates on making xen...

2006-08-14 Thread Orran Y Krieger

Building xen, cross compiled from an
x86 box. Couple of things led me astray on web page: 

At lest on my box, you needed 

CROSS_COMPILE=powerpc64-linux- CROSS_COMPILE32=powerpc-linux-
So, CROSS32_COMPILE should be CROSS_COMPILE32
I think.

Also, where you say:
XEN_TARGET_ARCH=powerp64

it should be:
XEN_TARGET_ARCH=powerpc64
i.e., missing a c
___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel

Re: [XenPPC] wiki instructions

2006-08-14 Thread Jimi Xenidis


On Aug 14, 2006, at 12:56 PM, Maria Butrico wrote:


The wiki at http://wiki.xensource.com/xenwiki/XenPPC/Build states

if your cross toolchain is not capable of generating both 64-bit  
and 32-bit code then you will have to add CROSS32_COMPILE=powerpc- 
unknown-linux-gnu- to all you Linux building commands.


I have been iusing CROSS_COMPILE32.  Is this a type or would both  
work?


hmm, WRT to Linux, _only_ CROSS32_COMPILE should work.
If CROSS_COMPILE32 then nothing special will happen and your compiler  
you defined with CROSS_COMPILER can handle both.




Also it states:

make -C ~/xen/xenppc-unstable.hg/xen DOM0_IMAGE=~/xen/linux/xen/ 
arch/powerpc/boot/zImage


Is zImage also supposed to work in this command.  I use vmlinux.strip.


Yes a zImage can now be used (and vmlinux* will also work), it  
results in a much smaller image and can allow you to imbed a ramdisk  
if you wish.


Details:
  http://lists.xensource.com/archives/html/xen-ppc-devel/2006-06/ 
msg00294.html


-JX





___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


Re: [XenPPC] updates on making xen...

2006-08-14 Thread Jimi Xenidis


On Aug 14, 2006, at 2:09 PM, Orran Y Krieger wrote:



Building xen, cross compiled from an x86 box.  Couple of things led  
me astray on web page:


At lest on my box, you needed

CROSS_COMPILE=powerpc64-linux- CROSS_COMPILE32=powerpc-linux-
So, CROSS32_COMPILE should be CROSS_COMPILE32 I think.


hmm I don't think so, Maria had the same issue, defining  
CROSS_COMPILE32 doesn't do anything.

Perhaps your CROSS_COMPILEer can generate both 32 and 64?
M-x grep-find says:


cd /home/jimix/work/xen/linux/linux-2.6/
find . \( -name CVS -o -name SCCS -o -name .hg \) -prune -o \! \( - 
name \*~ -o -name .#\* -o -name cscope.\* \) -type f -print0 |  
xargs -0 -e egrep -n 'CROSS_COMPILE32|CROSS32_COMPILE'

./arch/powerpc/Makefile:18:CROSS32_COMPILE ?=
./arch/powerpc/Makefile:20:CROSS32CC:= $(CROSS32_COMPILE)gcc
./arch/powerpc/Makefile:21:CROSS32AS:= $(CROSS32_COMPILE)as
./arch/powerpc/Makefile:22:CROSS32LD:= $(CROSS32_COMPILE)ld
./arch/powerpc/Makefile:23:CROSS32OBJCOPY		:= $(CROSS32_COMPILE) 
objcopy

./arch/powerpc/Makefile:26:ifeq ($(CROSS32_COMPILE),)
./arch/powerpc/boot/Makefile:20:#	CROSS32_COMPILE is setup as a  
prefix just like CROSS_COMPILE


grep exited abnormally with code 123 at Mon Aug 14 14:36:24






Also, where you say:
XEN_TARGET_ARCH=powerp64
it should be:
XEN_TARGET_ARCH=powerpc64
i.e., missing a c


Thanks for catching this.

-JX

___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


Re: [XenPPC] [xenppc-unstable] [POWERPC] memory cleanup (phase 2), destroy (et. al) now work

2006-08-14 Thread Jimi Xenidis


On Aug 14, 2006, at 6:50 PM, Hollis Blanchard wrote:


On Mon, 2006-08-14 at 17:48 -0400, Jimi Xenidis wrote:

On Aug 14, 2006, at 4:57 PM, Hollis Blanchard wrote:


Why do we free the HTAB in arch_domain_destroy(),

Xen heap

but free the RMA in
domain_relinquish_resources()?

Domheap

everytime you release !xenheap memory, it checks t-tot_pages and if
its zero releases a d-recnt. only when the refcnt = 1 (made zero by
destroy) will destroy get called.


OK, to expand on your answer a bit, the difference is that the HTAB is
allocated from the Xen heap, while the RMA is allocated from the  
domain

heap. We have to free all domain heap memory in
domain_relinquish_resources(), and only then will domain_destroy() be
called.

I think it might make sense to allocate the HTAB from the domain heap
instead, but it's working for now...


maybe, can't see why not. In fact I'd like to see the domain give up  
their own non-RMA memory to make an htab.  This allows for a very  
clean max_domains = (memory - 64M)/memory_per_domain.  Makes  
configuration-management way easier.


/me sees hollis with that look on his face again :)
-JX



___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


[XenPPC] PHDR link failure testcase

2006-08-14 Thread Amos Waterland
Using a `powerpc64-linux-gcc (GCC) 4.1.1 ()' x86-ppc toolchain, if I do this:

diff -r 9563f5c9ab19 xen/include/asm-powerpc/config.h
--- a/xen/include/asm-powerpc/config.h  Mon Aug 14 15:22:22 2006 -0500
+++ b/xen/include/asm-powerpc/config.h  Mon Aug 14 19:13:07 2006 -0400
@@ -51,7 +51,7 @@ extern char __bss_start[];
 #define CONFIG_GDB 1
 #define CONFIG_SMP 1
 #define CONFIG_PCI 1
-#define NR_CPUS 1
+#define NR_CPUS 16
 
 #ifndef ELFSIZE
 #define ELFSIZE 64

I get this:

make CROSS_COMPILE=powerpc64-linux- XEN_TARGET_ARCH=powerpc64 optimize=0 
CMDLINE=console=com2

powerpc64-linux-gcc -m64 -ffreestanding -fno-builtin -fno-common 
-fno-strict-aliasing -iwithprefix include -Wall -Werror -pipe 
-I/home/apw/devel/xen/xen.hg/xen/include 
-I/home/apw/devel/xen/xen.hg/xen/include/asm-powerpc/mach-generic 
-I/home/apw/devel/xen/xen.hg/xen/include/asm-powerpc/mach-default 
-Wpointer-arith -Wredundant-decls -Wpacked -msoft-float -O2 -g -D__XEN__ 
-Wundef -Wmissing-prototypes -Wmissing-declarations -N -nodefaultlibs 
-nostartfiles -Wl,-Ttext,0x400100,-T,xen.lds start.o 
/home/apw/devel/xen/xen.hg/xen/common/built_in.o 
/home/apw/devel/xen/xen.hg/xen/drivers/built_in.o 
/home/apw/devel/xen/xen.hg/xen/arch/powerpc/built_in.o -o 
/home/apw/devel/xen/xen.hg/xen/xen-syms

/usr/powerpc64/lib/gcc/powerpc64-linux/4.1.1/../../../../powerpc64-linux/bin/ld:
 /home/apw/devel/xen/xen.hg/xen/xen-syms: Not enough room for program headers 
(allocated 2, need 3)

/usr/powerpc64/lib/gcc/powerpc64-linux/4.1.1/../../../../powerpc64-linux/bin/ld:
 final link failed: Bad value
collect2: ld returned 1 exit status


___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel


[XenPPC] [xenppc-unstable] [POWERPC] update .hgignore

2006-08-14 Thread Xen patchbot-xenppc-unstable
# HG changeset patch
# User Hollis Blanchard [EMAIL PROTECTED]
# Node ID 41827ce2ccebf927df251ce3024eb10023de7d5b
# Parent  9563f5c9ab19cd93086ab9b0640c741714d009bc
[POWERPC] update .hgignore
Signed-off-by: Hollis Blanchard [EMAIL PROTECTED]
---
 .hgignore |5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff -r 9563f5c9ab19 -r 41827ce2cceb .hgignore
--- a/.hgignore Mon Aug 14 15:22:22 2006 -0500
+++ b/.hgignore Mon Aug 14 19:22:16 2006 -0500
@@ -201,5 +201,6 @@
 ^xen/xen\..*$
 ^xen/arch/powerpc/dom0\.bin$
 ^xen/arch/powerpc/asm-offsets\.s$
-^xen/arch/powerpc/firmware
-^xen/arch/powerpc/firmware_image
+^xen/arch/powerpc/firmware$
+^xen/arch/powerpc/firmware_image$
+^xen/arch/powerpc/xen\.lds$

___
Xen-ppc-devel mailing list
Xen-ppc-devel@lists.xensource.com
http://lists.xensource.com/xen-ppc-devel