search for: have_arch_e820_sanit

...0 arch/i386/kernel/setup.c > > --- a/arch/i386/kernel/setup.c Thu Jun 22 16:02:54 2006 -0400 > > +++ b/arch/i386/kernel/setup.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...

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