xen: Make XEN_BACKEND selectable by DomU
PATCH v2 1/1 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.
---
v2: omit superfluous "y if" per Jan Beulich
--- drivers/xen/Kconfig | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/xen/Kconfig +1 -2
@@ -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.
Signature · 1 line
2.17.1
Quoted 9 lines · Jason Andryuk
XEN_BACKENDdoesn't actually depend onXEN_DOM0. DomUs can serve backends to other DomUs. One example is a service VM providing network backends.The original
Kconfigdefaulted Dom0 to y and it could be disabled. DomU could not select the option. With the newKconfig, we default y for Dom0 and n for DomU. Either can then toggle the selection.Signed-off-by Jason Andryuk <[email protected]>
Applied to for-linus-19d
_______________________________________________
Xen-devel mailing list
[email protected]
https://lists.xenproject.org/mailman/listinfo/xen-devel
Quoted 9 lines · Jason Andryuk
XEN_BACKENDdoesn't actually depend onXEN_DOM0. DomUs can serve backends to other DomUs. One example is a service VM providing network backends.The original
Kconfigdefaulted Dom0 to y and it could be disabled. DomU could not select the option. With the newKconfig, we default y for Dom0 and n for DomU. Either can then toggle the selection.Signed-off-by Jason Andryuk <[email protected]>
Applied to for-linus-19d