From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
linux-kernel@vger.kernel.org, mtosatti@redhat.com,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/2] rcu: provide rcu_virt_note_context_switch() function.
Date: Mon, 9 May 2011 05:16:30 -0700 [thread overview]
Message-ID: <20110509121630.GJ2608@linux.vnet.ibm.com> (raw)
In-Reply-To: <4DC7AB16.7010609@redhat.com>
On Mon, May 09, 2011 at 11:51:34AM +0300, Avi Kivity wrote:
> On 05/04/2011 07:35 PM, Paul E. McKenney wrote:
> >On Wed, May 04, 2011 at 04:31:03PM +0300, Gleb Natapov wrote:
> >> Provide rcu_virt_note_context_switch() for vitalization use to note
> >> quiescent state during guest entry.
> >
> >Very good, queued on -rcu.
> >
> >Unless you tell me otherwise, I will assume that you want to carry the
> >patch modifying KVM to use this.
>
> Is -rcu a fast-forward-only tree (like tip)? If so I'll merge it
> and apply patch 2.
Yep, -rcu is subject to rebase and feeds into -tip. The patch is
SHA 29ce831000081dd757d3116bf774aafffc4b6b20 in
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-2.6-rcu.git
Branch is rcu/next. My guess is that this commit will show up in
-tip soon.
Thanx, Paul
next prev parent reply other threads:[~2011-05-09 12:16 UTC|newest]
Thread overview: 7+ 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 [this message]
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
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=20110509121630.GJ2608@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).