[PATCH v2] x86: don't allow KVM_CLOCK on Voyager or Visual WS

Randy Dunlap
2008-03-25T23:08:46Z

From: Randy Dunlap <randy.dunlap@oracle.com>

Prevent failed randconfig builds with KVM_CLOCK being enabled
on Voyager or VISWS.

build-rand9.out: Using /local/linsrc/next-20080325 as source for kernel
build-rand9.out: from /local/linsrc/next-20080325/include/linux/irqflags.h:46,
build-rand9.out: from include2/asm/system.h:11,
build-rand9.out: from include2/asm/processor.h:21,
build-rand9.out: from include2/asm/atomic_32.h:5,
build-rand9.out: from include2/asm/atomic.h:2,
build-rand9.out: from /local/linsrc/next-20080325/include/linux/crypto.h:20,
build-rand9.out: from /local/linsrc/next-20080325/arch/x86/kernel/asm-offsets_32.c:7,
build-rand9.out: from /local/linsrc/next-20080325/arch/x86/kernel/asm-offsets.c:2:
build-rand9.out:include2/asm/paravirt.h:856: error: 'struct pv_apic_ops' has no member named 'startup_ipi_hook'
build-rand9.out:include2/asm/paravirt.h:856: error: 'struct pv_apic_ops' has no member named 'startup_ipi_hook'
build-rand9.out:include2/asm/paravirt.h:856: error: memory input 4 is not directly addressable
build-rand9.out:make[2]: *** [arch/x86/kernel/asm-offsets.s] Error 1

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
arch/x86/Kconfig | 1 +
1 file changed, 1 insertion(+)

--- next-20080325.orig/arch/x86/Kconfig
+++ next-20080325/arch/x86/Kconfig
@@ -370,6 +370,7 @@ config VMI
config KVM_CLOCK
bool "KVM paravirtualized clock"
select PARAVIRT
+ depends on !(X86_VISWS || X86_VOYAGER)
help
Turning on this option will allow you to run a paravirtualized clock
when running over the KVM hypervisor. Instead of relying on a PIT

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.