[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] X86_64 and 4GB RAM using Flat Memory Model?
What does the start of a native Linux dmesg output look like (i.e, the bits where it prints out the memory map)? Yes, it's quite different. Now that you mention it, xen sees the memory which are marked as (usable), but not the ones marked as (reserved). Whereas debian etch kernel sees the (reserved) ones as well. Below if the dmesg output from the debian etch bootup. Bootdata ok (command line is root=/dev/md0 ro ) Linux version 2.6.18-3-amd64 (Debian 2.6.18-7) (waldi@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 17:04:37 CET 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009dc00 (usable) BIOS-e820: 000000000009dc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable) BIOS-e820: 00000000bfff0000 - 00000000bfffe000 (ACPI data) BIOS-e820: 00000000bfffe000 - 00000000c0000000 (ACPI NVS) BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved) BIOS-e820: 00000000ff700000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 0000000140000000 (usable) DMI present. ACPI: RSDP (v002 ACPIAM ) @ 0x00000000000f9480 ACPI: XSDT (v001 A M I OEMXSDT 0x12000614 MSFT 0x00000097) @ 0x00000000bfff0100 ACPI: FADT (v003 A M I OEMFACP 0x12000614 MSFT 0x00000097) @ 0x00000000bfff0290 ACPI: MADT (v001 A M I OEMAPIC 0x12000614 MSFT 0x00000097) @ 0x00000000bfff0390 ACPI: SPCR (v001 A M I OEMSPCR 0x12000614 MSFT 0x00000097) @ 0x00000000bfff0410 ACPI: SLIT (v001 A M I OEMSLIT 0x12000614 MSFT 0x00000097) @ 0x00000000bfff04a0 ACPI: OEMB (v001 A M I AMI_OEM 0x12000614 MSFT 0x00000097) @ 0x00000000bfffe040 ACPI: HPET (v001 A M I OEMHPET0 0x12000614 MSFT 0x00000097) @ 0x00000000bfff54d0 ACPI: SRAT (v001 AMD HAMMER 0x00000001 AMD 0x00000001) @ 0x00000000bfff5510 ACPI: SSDT (v001 A M I POWERNOW 0x00000001 AMD 0x00000001) @ 0x00000000bfff5620 ACPI: DSDT (v001 DATER DATER111 0x00000111 INTL 0x20051117) @ 0x0000000000000000 SRAT: PXM 0 -> APIC 0 -> Node 0 SRAT: PXM 0 -> APIC 1 -> Node 0 SRAT: PXM 1 -> APIC 2 -> Node 1 SRAT: PXM 1 -> APIC 3 -> Node 1 SRAT: Node 0 PXM 0 0-a0000 SRAT: Node 0 PXM 0 0-80000000 SRAT: Node 1 PXM 1 80000000-c0000000 SRAT: Node 1 PXM 1 80000000-140000000 NUMA: Using 31 for the hash shift. Bootmem setup node 0 0000000000000000-0000000080000000 Bootmem setup node 1 0000000080000000-0000000140000000 On node 0 totalpages: 516134 DMA zone: 3054 pages, LIFO batch:0 DMA32 zone: 513080 pages, LIFO batch:31 On node 1 totalpages: 513520 DMA32 zone: 254960 pages, LIFO batch:31 Normal zone: 258560 pages, LIFO batch:31 ACPI: PM-Timer IO Port: 0x2008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:1 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:1 APIC version 16 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled) Processor #2 15:1 APIC version 16 ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled) Processor #3 15:1 APIC version 16 ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to physical flat ACPI: HPET id: 0x10de8201 base: 0xfed00000 Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at c2000000 (gap: c0000000:20000000) SMP: Allowing 4 CPUs, 0 hotplug CPUs Built 2 zonelists. Total pages: 1029654 Kernel command line: root=/dev/md0 ro Initializing CPU#0 -- John _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |