The Null scheduler has been in the tree long enough to be marked
supported.
Signed-off-by: Stefano Stabellini <sstabell...@kernel.org>
CC: george.dun...@eu.citrix.com
CC: ian.jack...@eu.citrix.com
CC: jbeul...@suse.com
CC: andrew.coop...@citrix.com
CC: dfaggi...@suse.com
---
SUPPORT.md | 2 +-
xen/common/Kconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/SUPPORT.md b/SUPPORT.md
index 264b23f..f96c38c 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -284,7 +284,7 @@ Currently only single-vcpu domains are supported.
### Null Scheduler
- Status: Experimental
+ Status: Supported
A very simple, very static scheduling policy
that always schedules the same vCPU(s) on the same pCPU(s).
diff --git a/xen/common/Kconfig b/xen/common/Kconfig
index db6bb2d..bb1e831 100644
--- a/xen/common/Kconfig
+++ b/xen/common/Kconfig
@@ -203,7 +203,7 @@ config SCHED_ARINC653
cores, targeted for avionics, drones, and medical devices.
config SCHED_NULL
- bool "Null scheduler support (EXPERIMENTAL)"
+ bool "Null scheduler support"
default y
---help---
The null scheduler is a static, zero overhead scheduler,
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
