| Carl van Schaik | 6d7b2ff | 2018-07-06 22:00:55 +1000 | [diff] [blame] | 1 | # |
| 2 | # OKL4 Virtual Services framework |
| 3 | # |
| 4 | |
| 5 | menuconfig VSERVICES_SUPPORT |
| 6 | tristate "OKL4 Virtual Services support" |
| 7 | default OKL4_GUEST || OKL4_VIRTUALISATION |
| 8 | select HOTPLUG |
| 9 | help |
| 10 | This option adds core support for OKL4 Virtual Services. The Virtual |
| 11 | Services framework is an inter-OS device/service sharing |
| 12 | protocol which is supported on OKL4 Microvisor virtualization |
| 13 | platforms. You will also need drivers from the following menu in |
| 14 | order to make use of it. |
| 15 | |
| 16 | if VSERVICES_SUPPORT |
| 17 | |
| 18 | config VSERVICES_CHAR_DEV |
| 19 | bool "Virtual Services user-space service API" |
| 20 | default y |
| 21 | help |
| 22 | Select this if you want to use user-space service drivers. You will |
| 23 | also need udev rules that create device nodes, and protocol code |
| 24 | generated by the OK Mill tool. |
| 25 | |
| 26 | config VSERVICES_DEBUG |
| 27 | bool "Virtual Services debugging support" |
| 28 | help |
| 29 | Select this if you want to enable Virtual Services core framework |
| 30 | debugging. The debug messages for various components of the Virtual |
| 31 | Services core framework can be toggled at runtime on a per-session |
| 32 | basis via sysfs. When Virtual Services debugging is enabled here, |
| 33 | but disabled at runtime it has a minimal performance impact. |
| 34 | |
| 35 | config VSERVICES_LOCK_DEBUG |
| 36 | bool "Debug Virtual Services state locks" |
| 37 | default DEBUG_KERNEL |
| 38 | help |
| 39 | This option enables some runtime checks that Virtual Services |
| 40 | state lock functions are used correctly in service drivers. |
| 41 | |
| 42 | config VSERVICES_SERVER |
| 43 | tristate "Virtual Services server support" |
| 44 | depends on SYSFS |
| 45 | default y |
| 46 | help |
| 47 | This option adds support for Virtual Services servers, which allows |
| 48 | exporting of services from this Linux to other environments. Servers |
| 49 | are created at runtime by writing to files in |
| 50 | /sys/bus/vservices-server. |
| 51 | |
| 52 | config VSERVICES_CLIENT |
| 53 | tristate "Virtual Services client support" |
| 54 | default y |
| 55 | help |
| 56 | This option adds support for Virtual Services clients, which allows |
| 57 | connecting to services exported from other environments. |
| 58 | |
| 59 | config VSERVICES_SKELETON_DRIVER |
| 60 | tristate "Virtual Services skeleton driver" |
| 61 | depends on VSERVICES_SERVER || VSERVICES_CLIENT |
| 62 | default n |
| 63 | help |
| 64 | This option adds support for a skeleton virtual service driver. This |
| 65 | driver can be used for templating or testing of virtual service |
| 66 | drivers. If unsure say N. |
| 67 | |
| 68 | config VSERVICES_NAMED_DEVICE |
| 69 | bool "Virtual Services use named device node in /dev" |
| 70 | default n |
| 71 | help |
| 72 | Select this if you want to use a named device name over a numeric |
| 73 | device name in /dev |
| 74 | |
| 75 | source "drivers/vservices/transport/Kconfig" |
| 76 | |
| 77 | source "drivers/vservices/protocol/Kconfig" |
| 78 | |
| 79 | source "drivers/vservices/Kconfig.stacks" |
| 80 | |
| 81 | endif # VSERVICES_SUPPORT |