All of lore.kernel.org
 help / color / mirror / Atom feed
From: ehrhardt@linux.vnet.ibm.com
To: kvm-ppc@vger.kernel.org
Subject: [kvm-ppc-devel] [PATCH] kvmppc_relay: select required relay in
Date: Thu, 20 Mar 2008 10:17:27 +0000	[thread overview]
Message-ID: <12060082483612-git-send-email-ehrhardt@linux.vnet.ibm.com> (raw)

Subject: [PATCH] kvmppc_relay: select required relay in config

From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>

When using the kvmppc_relay patch we need CONFIG_RELAY to compile.
The simple solution to fold into our relay patch is in here which
selects RELAY for us. If preferred we might implement as well a
CONFIG_KVMPPC_TLBDEBUG which selects RELAY and ifdef's our code
using relay elements.

Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
---

 Kconfig |    1 +
 1 files changed, 1 insertion(+)

diff --git a/arch/powerpc/kvm/Kconfig b/arch/powerpc/kvm/Kconfig
--- a/arch/powerpc/kvm/Kconfig
+++ b/arch/powerpc/kvm/Kconfig
@@ -38,6 +38,7 @@ config KVM_POWERPC_440
 	tristate "KVM guest support for PowerPC 440"
 	depends on KVM && 44x
 	select KVM_POWERPC
+	select RELAY 
 	---help---
 	  Provides support for KVM on 440 processors.
 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel

             reply	other threads:[~2008-03-20 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 10:17 ehrhardt [this message]
2008-03-21 20:32 ` [kvm-ppc-devel] [PATCH] kvmppc_relay: select required relay Hollis Blanchard

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=12060082483612-git-send-email-ehrhardt@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.