summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2013-10-30 21:43:01 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2013-10-31 22:14:23 +0100
commit81e87e26796782e014fd1f2bb9cd8fb6ce4021a8 (patch)
tree10422ba6742d9c28afdc0e4933a2fea2db37903c
parent98f73630f96f1a6d8c845b8b3e5f9ae532cf82d1 (diff)
kvm_host: typo fix
fix up typo in comment. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
-rw-r--r--include/linux/kvm_host.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index 92aae88756db..9bb1048d010e 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -804,7 +804,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.