| commit | 8fa2206821953a50a3a02ea33fcfb3ced2fd9997 | |
| author | Gleb Natapov <gleb@redhat.com> | |
| Wed, 4 May 2011 13:31:04 +0000 (4 16:31 +0300) | ||
| committer | Avi Kivity <avi@redhat.com> | |
| Sun, 22 May 2011 12:48:09 +0000 (22 08:48 -0400) | ||
| tree | f4f773a0501f0fd8d3bfe30dd4851c9f0095911d | treesnapshot (tar.gz zip) |
| parent | e3aa52d665ec1a962d1cf025a2e5ee84b3b33406 | commitdiff |
KVM: make guest mode entry to be rcu quiescent state
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 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.
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
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 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.
Signed-off-by: Gleb Natapov <gleb@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
| include/linux/kvm_host.h | diffblobblamehistory |