[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131030194301.GA26143@redhat.com>
Date: Wed, 30 Oct 2013 21:43:01 +0200
From: "Michael S. Tsirkin" <mst@...hat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Gleb Natapov <gleb@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
Alexander Graf <agraf@...e.de>,
Takuya Yoshikawa <yoshikawa_takuya_b1@....ntt.co.jp>,
"Michael S. Tsirkin" <mst@...hat.com>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] kvm_host: typo fix
fix up typo in comment.
Signed-off-by: Michael S. Tsirkin <mst@...hat.com>
---
include/linux/kvm_host.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index 0fbbc7a..7445013 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -789,7 +789,7 @@ static inline void kvm_guest_enter(void)
/* KVM does not hold any references to rcu protected data when it
* switches CPU into a guest mode. In fact switching to a guest mode
- * is very similar to exiting to userspase from rcu point of view. In
+ * is very similar to exiting to userspace from rcu point of view. In
* addition CPU may stay in a guest mode for quite a long time (up to
* one time slice). Lets treat guest mode as quiescent state, just like
* we do with user-mode execution.
--
MST
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists