WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] fedora-xen-ia64 first pass

Hi, Aron

Thank you for your help.
I can make RPMS/ia64/xen-3.0.2-4.ia64.rpm.

fedora-xen-ia64/RPMS/ia64/xen-3.0.2-4.ia64.rpm includes all tools of xen.
(don't includes xen(hypervisor) and domain's kernel)

But I cannot make fedora-kernel-ia64 yet.

=======================
  gcc -Wp,-MD,arch/ia64/kernel/.irq_lsapic.o.d  -nostdinc -isystem 
/usr/lib/gcc/ia64-redhat-linux/4.1.0/include -D__KERNEL__ -Iinclude  -include 
include/linux/autoconf.h -DHAVE_W
ORKING_TEXT_ALIGN -DHAVE_MODEL_SMALL_ATTRIBUTE -DHAVE_SERIALIZE_DIRECTIVE  
-Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing 
-fno-common -Os -fomit-frame-poin
ter -g -pipe  -ffixed-r13 -mfixed-range=f12-f15,f32-f127 -falign-functions=32 
-frename-registers -fno-optimize-sibling-calls -Wdeclaration-after-statement 
-Wno-pointer-sign   -mc
onstant-gp -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(irq_lsapic)"  
-D"KBUILD_MODNAME=KBUILD_STR(irq_lsapic)" -c -o 
arch/ia64/kernel/.tmp_irq_lsapic.o arch/ia64/kernel/ir
q_lsapic.c
mm/page_alloc.c: In function 'alloc_node_mem_map':
mm/page_alloc.c:2143: error: 'MAX_ORDER_NR_PAGES' undeclared (first use in this 
function)
mm/page_alloc.c:2143: error: (Each undeclared identifier is reported only once
mm/page_alloc.c:2143: error: for each function it appears in.)
make[1]: *** [mm/page_alloc.o] Error 1
make: *** [mm] Error 2
make: *** Waiting for unfinished jobs....
=======================

This error is caused by SOURCES/linux-2.6-xen-ia64-10022.patch
MAX_ORDER_NR_PAGES is not defined.
What does this patch mean?
=======================
@@ -2124,14 +2127,22 @@ static void __init alloc_node_mem_map(st
 #ifdef CONFIG_FLAT_NODE_MEM_MAP
        /* ia64 gets its own node_mem_map, before this, without bootmem */
        if (!pgdat->node_mem_map) {
-               unsigned long size;
+               unsigned long size, start, end;
                struct page *map;
 
-               size = (pgdat->node_spanned_pages + 1) * sizeof(struct page);
+               /*
+                * The zone's endpoints aren't required to be MAX_ORDER
+                * aligned but the node_mem_map endpoints must be in order
+                * for the buddy allocator to function correctly.
+                */
+               start = pgdat->node_start_pfn & ~(MAX_ORDER_NR_PAGES - 1);
+               end = pgdat->node_start_pfn + pgdat->node_spanned_pages;
+               end = ALIGN(end, MAX_ORDER_NR_PAGES);
+               size =  (end - start) * sizeof(struct page);
                map = alloc_remap(pgdat->node_id, size);
                if (!map)
                        map = alloc_bootmem_node(pgdat, size);
-               pgdat->node_mem_map = map;
+               pgdat->node_mem_map = map + (pgdat->node_start_pfn - start);
        }
 #ifdef CONFIG_FLATMEM
        /*
===================================

I'm not clear about directory construction.
What do each directory mean?
I want to know the following directory's meaning.

# ls -F fedora-kernel-ia64/BUILD/kernel-2.6.16/
Config.mk  extract.pub  kernel.pub  kernel.sec  linux-2.6.16.ia64/  
pubring.gpg  random_seed  secring.gpg  vanilla/  xen/  xen-10022/

Are kernels of domain0/domainU made at linux-2.6.16.ia64?
If so, each linux-2.6.16.ia64 must be remade at each building time.
Am I right?

Best Regards,

Akio Takebe


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

<Prev in Thread] Current Thread [Next in Thread>