search for: dmi_scan

.../2003") - }, - }, - { - .callback = disable_acpi_pci, - .ident = "Acer TravelMate 36x Laptop", - .matches = { - DMI_MATCH(DMI_SYS_VENDOR, "Acer"), - DMI_MATCH(DMI_PRODUCT_NAME, "TravelMate 360"), - }, - }, {} }; --- a/xen/arch/x86/dmi_scan.c +++ b/xen/arch/x86/dmi_scan.c @@ -229,27 +229,6 @@ static __init __attribute__((unused)) in } #endif -#ifdef CONFIG_ACPI_PCI -static __init int disable_acpi_irq(struct dmi_blacklist *d) -{ - if (!acpi_force) { - printk(KERN_NOTICE "%s detected: force use of acpi=noirq\n", -...

Anyone have an idea if it would be a huge effort to get pxelinux to look for config files based on serial number (available in DMI on modern motherboards), much like we currently can use MAC address's. Lots of our hardware comes with the serial number stuck on the chassis but not the mac address. We'd like to move to pxelinux and still use the serial number as the key for figuring which

...ynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE -g -D__XEN__ -c traps.c -o traps.o ld -m elf_x86_64 -r -o built_in.o entry.o mm.o traps.o make[6]: Leaving directory `/home/test1/xen-unstable/xen/arch/x86/x86_64'' ld -m elf_x86_64 -r -o built_in.o apic.o bitops.o compat.o delay.o dmi_scan.o domctl.o domain.o domain_build.o e820.o extable.o flushtlb.o platform_hypercall.o i387.o i8259.o io_apic.o irq.o microcode.o mm.o mpparse.o nmi.o physdev.o rwlock.o setup.o shutdown.o smp.o smpboot.o string.o sysctl.o time.o trampoline.o traps.o usercopy.o x86_emulate.o acpi/built_in.o cpu/built_...

Hi, Is the http://xenbits.xensource.com/linux-2.6-xen.hg tree still being updated? if not, what''s the preferred Linux tree to track that has all of the Xen bits? Thanks, Muli _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

Hi All, I followed the instructions here at http://bderzhavets.wordpress.com/2009/06/10/setup-fedora-11-pv-domu-at-xen-3-4-1-dom0-kernel-2-6-30-rc6-tip-on-top-of-fedora-11/ However, when I do a "make menuconfig", I cannot see any XEN related configuration options. What am I missing? Thank you. Mr. Teo En Ming Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)