|
|
|
|
|
|
|
|
|
|
xen-devel
RE: [Xen-devel] Daily Xen Build
This problem has been fixed by the changeset 6395, and all the
processors are up on x86_64 SMP xenlinux. Thanks a lot for the cleanups,
Keir.
Jun
---
Intel Open Source Technology Center
Nakajima, Jun wrote:
>>
>> I'm also seeing SMP dom0 broken, and only 1 CPU is up:
>>
>> Booting processor 1/1 rip ffffffff80100014 rsp ffff8801ee715f58
>> (XEN) DOM0: (file=mm.c, line=1455) Bad type (saw 00000000f0000001!=
>> exp 00000000a0000000) for mfn 9d000 (pfn 0)
>> Booting processor 2/2 rip ffffffff80100014 rsp ffff8801ee71ff58
>> (XEN) DOM0: (file=mm.c, line=1455) Bad type (saw 00000000f0000001!=
>> exp 00000000a0000000) for mfn 9d002 (pfn 2)
>> ...
>>
>>
>> Jun
>> ---
>> Intel Open Source Technology Center
>>
> If I revert the changeset 6379, they are back.
>
> --- a/linux-2.6-xen-sparse/arch/xen/x86_64/kernel/setup.c Wed Aug
> 24 15:22:44 2005
> +++ b/linux-2.6-xen-sparse/arch/xen/x86_64/kernel/setup.c Wed Aug
> 24 15:46:33 2005
> @@ -428,8 +428,9 @@
> {
> unsigned long bootmap_size = init_bootmem(start_pfn,
> end_pfn); free_bootmem(0, end_pfn << PAGE_SHIFT);
> - /* XXX KAF: Why can't we leave low 1MB of memory free? */
> - reserve_bootmem(0, (PFN_PHYS(start_pfn) + bootmap_size +
> PAGE_SIZE-1));
> + reserve_bootmem(HIGH_MEMORY,
> + (PFN_PHYS(start_pfn) + bootmap_size +
> PAGE_SIZE-1)
> + - HIGH_MEMORY);
> }
> #else
> static void __init contig_initmem_init(void)
>
>
> Jun
> ---
> Intel Open Source Technology Center
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|