From 185233427b3834086a9050336113f9e22176fa3b Mon Sep 17 00:00:00 2001 From: Michael Pratt Date: Tue, 1 May 2018 21:14:24 -0700 Subject: [PATCH] Note that the KVM platform is experimental PiperOrigin-RevId: 195043285 Change-Id: Ie76112eff61062e1a54894b3707201fd284be377 --- README.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 01830eb3a..dc500d445 100644 --- a/README.md +++ b/README.md @@ -142,12 +142,13 @@ mapping functionality. Today, gVisor supports two platforms: executing host system calls. This platform can run anywhere that `ptrace` works (even VMs without nested virtualization). -* The **KVM** platform allows the Sentry to act as both guest OS and VMM, - switching back and forth between the two worlds seamlessly. The KVM platform - can run on bare-metal or on a VM with nested virtualization enabled. While - there is no virtualized hardware layer -- the sandbox retains a process model - -- gVisor leverages virtualization extensions available on modern processors - in order to improve isolation and performance of address space switches. +* The **KVM** platform (experimental) allows the Sentry to act as both guest OS + and VMM, switching back and forth between the two worlds seamlessly. The KVM + platform can run on bare-metal or on a VM with nested virtualization enabled. + While there is no virtualized hardware layer -- the sandbox retains a process + model -- gVisor leverages virtualization extensions available on modern + processors in order to improve isolation and performance of address space + switches. ### Performance