From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: kvm-devel@lists.sourceforge.net, avi@qumranet.com,
linux-next@vger.kernel.org, hpa <hpa@zytor.com>,
mingo <mingo@redhat.com>
Subject: [PATCH v2] x86: don't allow KVM_CLOCK on Voyager or Visual WS
Date: Tue, 25 Mar 2008 16:08:46 -0700 [thread overview]
Message-ID: <20080325160846.d02b0209.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080314104444.ca80e434.randy.dunlap@oracle.com>
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.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
next prev parent reply other threads:[~2008-03-25 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 17:44 [PATCH] x86: don't allow KVM_CLOCK without HAVE_KVM Randy Dunlap
2008-03-16 11:13 ` Avi Kivity
2008-03-17 15:55 ` Randy Dunlap
2008-03-17 17:01 ` Avi Kivity
2008-03-25 23:08 ` Randy Dunlap [this message]
2008-03-27 8:25 ` [kvm-devel] [PATCH v2] x86: don't allow KVM_CLOCK on Voyager or Visual WS Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080325160846.d02b0209.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=avi@qumranet.com \
--cc=hpa@zytor.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox