2018-09-25 11:37:54

by Jason Andryuk

Subject: [PATCH v2] xen: Make XEN_BACKEND selectable by DomU

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 <[email protected]>
---
v2: omit superfluous "y if" per Jan Beulich
---
drivers/xen/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index b459edfacff3..692e82fcad1f 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 XEN_DOM0
help
Support for backend device drivers that provide I/O services
to other virtual machines.
--
2.17.1

2018-09-25 21:11:45

by Boris Ostrovsky

Subject: Re: [PATCH v2] xen: Make XEN_BACKEND selectable by DomU

On 9/25/18 7:36 AM, Jason Andryuk wrote:
> 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 <[email protected]>

Reviewed-by: Boris Ostrovsky <[email protected]>

Applied to for-linus-19d