All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Andryuk <jandryuk@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>
Cc: Jason Andryuk <jandryuk@gmail.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: [PATCH] xen: Make XEN_BACKEND selectable by DomU
Date: Thu, 20 Sep 2018 10:32:36 -0400	[thread overview]
Message-ID: <20180920143237.10000-1-jandryuk@gmail.com> (raw)

XEN_BACKEND doesn't actually depend on XEN_DOM0.  DomUs can serve
backends to other DomUs.  One example is a service VM providing network
backends.

The original Kconfig defaulted Dom0 to y and it could be disabled.  DomU
could not select the option.  With the new Kconfig, we default y for
Dom0 and n for DomU.  Either can then toggle the selection.

Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
---
OpenXT runs network backends in a network service DomU that shares out
PCI NICs.

 drivers/xen/Kconfig | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index b459edfacff3..af1bf99318c6 100644
--- a/drivers/xen/Kconfig
+++ b/drivers/xen/Kconfig
@@ -101,8 +101,7 @@ config XEN_DEV_EVTCHN
 
 config XEN_BACKEND
 	bool "Backend driver support"
-	depends on XEN_DOM0
-	default y
+	default y if XEN_DOM0
 	help
 	  Support for backend device drivers that provide I/O services
 	  to other virtual machines.
-- 
2.17.1


             reply	other threads:[~2018-09-20 14:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 14:32 Jason Andryuk [this message]
2018-09-20 14:54 ` [Xen-devel] [PATCH] xen: Make XEN_BACKEND selectable by DomU Jan Beulich
2018-09-20 15:30   ` Jason Andryuk
2018-09-20 15:30   ` Jason Andryuk
2018-09-20 14:54 ` Jan Beulich
  -- strict thread matches above, loose matches on Subject: below --
2018-09-20 14:32 Jason Andryuk

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=20180920143237.10000-1-jandryuk@gmail.com \
    --to=jandryuk@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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.