LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Avi Kivity <avi@qumranet.com>, mingo <mingo@redhat.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH] [kvm-devel] build #365 issue for v2.6.25-rc2-342-g5d9c4a7 in ./arch/x86/kvm/kvm.ko
Date: Wed, 20 Feb 2008 09:20:08 -0800	[thread overview]
Message-ID: <20080220092008.3f3bd994.randy.dunlap@oracle.com> (raw)
In-Reply-To: <47BC3407.20307@qumranet.com>

On Wed, 20 Feb 2008 16:07:03 +0200 Avi Kivity wrote:

> > Looks like KVM conflicts with CONFIG_VOYAGER...
> >
> 
> Attached patch should fix.
> 
> Subject: x86: disable KVM on Voyager
> 
> Most classic Pentiums don't have hardware virtualization
> extension, and building kvm with voyager generates
> spurious failures.
> 
> Signed-off-by: Avi Kivity <avi@qumranet.com>

Might as well extend it for VISWS & NUMAQ:

---
From: Avi Kivity <avi@qumranet.com>

Most classic Pentiums don't have hardware virtualization extension,
and building kvm with Voyager, Visual Workstation, or NUMAQ
generates spurious failures.

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

--- linux-2.6.25-rc2-git4.orig/arch/x86/Kconfig
+++ linux-2.6.25-rc2-git4/arch/x86/Kconfig
@@ -21,7 +21,7 @@ config X86
 	select HAVE_IDE
 	select HAVE_OPROFILE
 	select HAVE_KPROBES
-	select HAVE_KVM
+	select HAVE_KVM if ((X86_32 && !X86_VOYAGER && !X86_VISWS && !X86_NUMAQ) || X86_64)
 
 
 config GENERIC_LOCKBREAK

  reply	other threads:[~2008-02-20 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-20 13:11 Toralf Förster
2008-02-20 13:54 ` [kvm-devel] " Avi Kivity
2008-02-20 14:07   ` Avi Kivity
2008-02-20 17:20     ` Randy Dunlap [this message]
2008-02-25 23:03       ` [PATCH] " Randy Dunlap

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=20080220092008.3f3bd994.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=toralf.foerster@gmx.de \
    --subject='Re: [PATCH] [kvm-devel] build #365 issue for v2.6.25-rc2-342-g5d9c4a7 in ./arch/x86/kvm/kvm.ko' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).