search for: visws

From: Randy Dunlap <randy.dunlap@oracle.com> Since Voyager and Visual WS already define ARCH_SETUP, it looks like PARAVIRT shouldn't be offered for them. In file included from arch/i386/kernel/setup.c:63: include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefined In file included from include/asm/msr.h:5, from include/asm/processor.h:17, from include/asm/thread_info.h:16, from include/linux/thread_info.h:21, from include/linux/pree...

From: Randy Dunlap <randy.dunlap@oracle.com> Since Voyager and Visual WS already define ARCH_SETUP, it looks like PARAVIRT shouldn't be offered for them. In file included from arch/i386/kernel/setup.c:63: include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefined In file included from include/asm/msr.h:5, from include/asm/processor.h:17, from include/asm/thread_info.h:16, from include/linux/thread_info.h:21, from include/linux/pree...

...emulates + * a PC in any way. **/ void __init intr_init_hook(void) { -#ifdef CONFIG_X86_LOCAL_APIC - apic_intr_init(); -#endif - - if (!acpi_ioapic) - setup_irq(2, &irq2); + init_ISA_irqs(); } /** =================================================================== --- a/arch/i386/mach-visws/setup.c +++ b/arch/i386/mach-visws/setup.c @@ -96,16 +96,9 @@ void __init visws_get_board_type_and_rev "unknown")), visws_board_rev); } -void __init pre_intr_init_hook(void) +void __init intr_init_hook(void) { init_VISWS_APIC_irqs(); -} - -void __init intr_init_hook(void) -{ -#if...

...emulates + * a PC in any way. **/ void __init intr_init_hook(void) { -#ifdef CONFIG_X86_LOCAL_APIC - apic_intr_init(); -#endif - - if (!acpi_ioapic) - setup_irq(2, &irq2); + init_ISA_irqs(); } /** =================================================================== --- a/arch/i386/mach-visws/setup.c +++ b/arch/i386/mach-visws/setup.c @@ -96,16 +96,9 @@ void __init visws_get_board_type_and_rev "unknown")), visws_board_rev); } -void __init pre_intr_init_hook(void) +void __init intr_init_hook(void) { init_VISWS_APIC_irqs(); -} - -void __init intr_init_hook(void) -{ -#if...

...en added in f0f32fccbffa to avoid a conflict arising from the long deceased ARCH_SETUP() macro and subsequently pushed down to the XEN option. As far as I can tell the conflict is no longer present and by dropping the dependency I was able to build a kernel which has both CONFIG_XEN and CONFIG_X86_VISWS enabled and boot it on Xen. I didn't try it on the VISWS platform. Signed-off-by: Ian Campbell <ian.campbell at citrix.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Cc: konrad.wilk at oracle.com Cc: xen-devel at lists.xensource.com Cc: Randy Dunlap <randy.dunlap at oracle.co...

...en added in f0f32fccbffa to avoid a conflict arising from the long deceased ARCH_SETUP() macro and subsequently pushed down to the XEN option. As far as I can tell the conflict is no longer present and by dropping the dependency I was able to build a kernel which has both CONFIG_XEN and CONFIG_X86_VISWS enabled and boot it on Xen. I didn't try it on the VISWS platform. Signed-off-by: Ian Campbell <ian.campbell at citrix.com> Cc: Jeremy Fitzhardinge <jeremy at goop.org> Cc: konrad.wilk at oracle.com Cc: xen-devel at lists.xensource.com Cc: Randy Dunlap <randy.dunlap at oracle.co...

OK, I need to do something like this to io_apic.c - split the hardware specific parts out under mach-default, so we can override them for other subarchitectures. It's not finished, needs header file and makefile work. Would you be willing to take this if I do it? I'm not going to bother if you're not, such refactorings are a pig to maintain out of tree. Frankly, io_apic.c needs a

OK, I need to do something like this to io_apic.c - split the hardware specific parts out under mach-default, so we can override them for other subarchitectures. It's not finished, needs header file and makefile work. Would you be willing to take this if I do it? I'm not going to bother if you're not, such refactorings are a pig to maintain out of tree. Frankly, io_apic.c needs a

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