search for: copy_e820_map

...vmid=1 Using config file "./xenclient1". Started domain centos5.2 Linux version 2.6.21-2950.fc8xen (kojibuilder@xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) #1 SMP Tue Oct 23 12:24:34 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000008800000 end: 0000000008800000 type: 1  Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges:   DMA             0 ->    34816   Normal      34816 ->    3...

...osta <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/e820.c =================================================================== --- clean-start.orig/arch/x86_64/kernel/e820.c +++ clean-start/arch/x86_64/kernel/e820.c @@ -567,7 +567,7 @@ void __init setup_memory_region(void) if (copy_e820_map(E820_MAP, E820_MAP_NR) < 0) early_panic("Cannot find a valid memory map"); printk(KERN_INFO "BIOS-provided physical RAM map:\n"); - e820_print_map("BIOS-e820"); + e820_print_map(MAP_TYPE_STR); } static int __init parse_memopt(char *p) Index: clean-start/inc...

...up.c Thu Jun 22 20:20:31 2006 -0400 > > @@ -458,6 +458,7 @@ static void __init print_memory_map(char > > } > > } > > > > +#ifndef HAVE_ARCH_E820_SANITIZE > > /* > > * Sanitize the BIOS e820 map. > > * > > @@ -677,6 +678,7 @@ int __init copy_e820_map(struct e820entr > > } while (biosmap++,--nr_map); > > return 0; > > } > > +#endif > > > Hi, > > what is this for? Isn't this 1) undocumented and 2) unclear and 3) > ugly ? (I'm pretty sure the HAVE_ARCH_* stuff is highly deprecated for >...

...osta <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/e820.c =================================================================== --- clean-start.orig/arch/x86_64/kernel/e820.c +++ clean-start/arch/x86_64/kernel/e820.c @@ -567,7 +567,7 @@ void __init setup_memory_region(void) if (copy_e820_map(E820_MAP, E820_MAP_NR) < 0) early_panic("Cannot find a valid memory map"); printk(KERN_INFO "BIOS-provided physical RAM map:\n"); - e820_print_map("BIOS-e820"); + e820_print_map(MAP_TYPE_STR); } static int __init parse_memopt(char *p) Index: clean-start/inc...

...ora.fc8.xen3.cfg". Started domain fedora.fc8 Linux version 2.6.21-2950.fc8xen ( kojibuilder@xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) #1 SMP Tue Oct 23 12:24:34 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 000000001b400000 end: 000000001b400000 type: 1 Xen: 0000000000000000 - 000000001b400000 (usable) 0MB HIGHMEM available. 436MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 111616 Normal 111616 -> 11...

...tput of the failed boot is like this: Using config file "./ubuntu". Started domain ubuntu Linux version 2.6.21-xen (root@localhost) (gcc version 4.1.2 (Gentoo 4.1.2 p1.1)) #3 Mon Oct 13 16:05:59 CEST 2008 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000040800000 end: 0000000040800000 type: 1 Xen: 0000000000000000 - 0000000040800000 (usable) 304MB HIGHMEM available. 727MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 186366 Normal 186366 ->...

The following patches introduce the core infrastructure needed to paravirtualize the 32-bit x86 Linux kernel. This is done by moving virtualization sensitive insn's or code paths to a function table, paravirt_ops. This structure can be populated with hypervisor specific calls or native stubs and currently support running on bare metal, VMI, Xen, or Lhype. These patches apply to

The following patches introduce the core infrastructure needed to paravirtualize the 32-bit x86 Linux kernel. This is done by moving virtualization sensitive insn's or code paths to a function table, paravirt_ops. This structure can be populated with hypervisor specific calls or native stubs and currently support running on bare metal, VMI, Xen, or Lhype. These patches apply to

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths