Commit 34aae15c authored Aug 15, 2018 by Salvatore Bonaccorso Committed by Greg Kroah-Hartman May 14, 2019

Documentation/l1tf: Fix small spelling typo



commit 60ca05c3b44566b70d64fbb8e87a6e0c67725468 upstream

Fix small typo (wiil -> will) in the "3.4. Nested virtual machines"
section.

Fixes: 5b76a3cf ("KVM: VMX: Tell the nested hypervisor to skip L1D flush on vmentry")
Cc: linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: linux-doc@vger.kernel.org
Cc: trivial@kernel.org

Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

parent 9c2556f4

Documentation/admin-guide/l1tf.rst

+1 −1

Original line number	Diff line number	Diff line
		@@ -556,7 +556,7 @@ When nested virtualization is in use, three operating systems are involved:
		the bare metal hypervisor, the nested hypervisor and the nested virtual
		machine. VMENTER operations from the nested hypervisor into the nested
		guest will always be processed by the bare metal hypervisor. If KVM is the
		bare metal hypervisor it wiil:
		bare metal hypervisor it will:

		- Flush the L1D cache on every switch from the nested hypervisor to the
		nested virtual machine, so that the nested hypervisor's secrets are not