From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-kernel@vger.kernel.org, mtosatti@redhat.com,
kvm@vger.kernel.org, paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH 2/2] KVM: make guest mode entry to be rcu quiescent state
Date: Wed, 11 May 2011 12:57:59 +0300 [thread overview]
Message-ID: <4DCA5DA7.9010201@redhat.com> (raw)
In-Reply-To: <1304515864-17105-3-git-send-email-gleb@redhat.com>
On 05/04/2011 04:31 PM, Gleb Natapov wrote:
> 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.
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-11 15:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 13:31 [PATCH 0/2] make kvm guest mode to be rcu quiescent state Gleb Natapov
2011-05-04 13:31 ` [PATCH 1/2] rcu: provide rcu_virt_note_context_switch() function Gleb Natapov
2011-05-04 16:35 ` Paul E. McKenney
2011-05-09 8:51 ` Avi Kivity
2011-05-09 12:16 ` Paul E. McKenney
2011-05-04 13:31 ` [PATCH 2/2] KVM: make guest mode entry to be rcu quiescent state Gleb Natapov
2011-05-11 9:57 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-28 9:52 [PATCH 0/2] make kvm guest mode " Gleb Natapov
2011-04-28 9:52 ` [PATCH 2/2] KVM: make guest mode entry " Gleb Natapov
2011-05-03 13:13 ` Marcelo Tosatti
2011-05-03 13:20 ` Avi Kivity
2011-05-03 13:21 ` Gleb Natapov
2011-05-03 13:29 ` Marcelo Tosatti
2011-05-03 13:39 ` Gleb Natapov
2011-05-03 15:42 ` Marcelo Tosatti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DCA5DA7.9010201@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.