search for: first_system_vector

On 06/26/13 01:06, Stephen Rothwell wrote: > Hi all, > > Changes since 20130625: > CONFIG_SMP is not set CONFIG_X86_UP_APIC is not set on i386: drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3cb): undefined reference to `first_system_vector' drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3f5): undefined reference to `first_system_vector' -- ~Randy

On 06/26/13 01:06, Stephen Rothwell wrote: > Hi all, > > Changes since 20130625: > CONFIG_SMP is not set CONFIG_X86_UP_APIC is not set on i386: drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3cb): undefined reference to `first_system_vector' drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3f5): undefined reference to `first_system_vector' -- ~Randy

On 06/26/13 01:06, Stephen Rothwell wrote: > Hi all, > > Changes since 20130625: > CONFIG_SMP is not set CONFIG_X86_UP_APIC is not set on i386: drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3cb): undefined reference to `first_system_vector' drivers/built-in.o: In function `xen_callback_vector': (.text+0x1dc3f5): undefined reference to `first_system_vector' -- ~Randy

Hi, Keir, These patches are rebased version of Yunhong''s original patches, which were sent out before XEN 3.2 was released. These patches enable MSI support and limited MSI-X support in XEN. Here is the original description of the patches from Yunhong''s mail. The basic idea including: 1) Keep vector global resource owned by xen, while split pirq into per-domain

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, These are the patches I'm planning to submit for 2.6.24. Comments gratefully accepted. Along with the usual cleanups and improvements are Jes' de-i386-ification patches, and a new "virtio" mechanism designed to be shared with KVM (and hopefully other hypervisors). Cheers, Rusty. Documentation/lguest/Makefile | 30 Documentation/lguest/lguest.c

Hi all, These are the patches I'm planning to submit for 2.6.24. Comments gratefully accepted. Along with the usual cleanups and improvements are Jes' de-i386-ification patches, and a new "virtio" mechanism designed to be shared with KVM (and hopefully other hypervisors). Cheers, Rusty. Documentation/lguest/Makefile | 30 Documentation/lguest/lguest.c