public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: riel@redhat.com, will.deacon@arm.com,
	linux-kernel@vger.kernel.org, Catalin.Marinas@arm.com,
	fweisbec@gmail.com, kvm@vger.kernel.org, mtosatti@redhat.com,
	borntraeger@de.ibm.com, mingo@kernel.org, oleg@redhat.com,
	lcapitulino@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH 6/6] kvm,rcu,nohz: use RCU extended quiescent state when running KVM guest
Date: Tue, 10 Feb 2015 12:14:02 -0800	[thread overview]
Message-ID: <20150210201402.GU4166@linux.vnet.ibm.com> (raw)
In-Reply-To: <54DA630D.6020601@amacapital.net>

On Tue, Feb 10, 2015 at 11:59:09AM -0800, Andy Lutomirski wrote:
> On 02/10/2015 06:41 AM, riel@redhat.com wrote:
> >From: Rik van Riel <riel@redhat.com>
> >
> >The host kernel is not doing anything while the CPU is executing
> >a KVM guest VCPU, so it can be marked as being in an extended
> >quiescent state, identical to that used when running user space
> >code.
> >
> >The only exception to that rule is when the host handles an
> >interrupt, which is already handled by the irq code, which
> >calls rcu_irq_enter and rcu_irq_exit.
> >
> >The guest_enter and guest_exit functions already switch vtime
> >accounting independent of context tracking. Leave those calls
> >where they are, instead of moving them into the context tracking
> >code.
> >
> >Signed-off-by: Rik van Riel <riel@redhat.com>
> >---
> >  include/linux/context_tracking.h       | 6 ++++++
> >  include/linux/context_tracking_state.h | 1 +
> >  include/linux/kvm_host.h               | 3 ++-
> >  3 files changed, 9 insertions(+), 1 deletion(-)
> >
> >diff --git a/include/linux/context_tracking.h b/include/linux/context_tracking.h
> >index 954253283709..b65fd1420e53 100644
> >--- a/include/linux/context_tracking.h
> >+++ b/include/linux/context_tracking.h
> >@@ -80,10 +80,16 @@ static inline void guest_enter(void)
> >  		vtime_guest_enter(current);
> >  	else
> >  		current->flags |= PF_VCPU;
> >+
> >+	if (context_tracking_is_enabled())
> >+		context_tracking_enter(IN_GUEST);
> 
> Why the if statement?
> 
> Also, have you checked how much this hurts guest lightweight
> entry/exit latency?  Context tracking is shockingly expensive for
> reasons I don't fully understand, but hopefully most of it is the
> vtime stuff.  (Context tracking is *so* expensive that I almost
> think we should set the performance taint flag if we enable it,
> assuming that flag ended up getting merged.  Also, we should make
> context tracking faster.)

It turns out that context_tracking_is_enabled() is a static inline
that uses a static_key, so the overhead should be minimal on platforms
having a full implementation of static keys.

							Thanx, Paul


  parent reply	other threads:[~2015-02-10 20:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 14:41 [PATCH -v4 0/6] rcu,nohz,kvm: use RCU extended quiescent state when running KVM guest riel
2015-02-10 14:41 ` [PATCH 1/6] rcu,nohz: add context_tracking_user_enter/exit wrapper functions riel
2015-02-10 15:28   ` Frederic Weisbecker
2015-02-10 16:48     ` Rik van Riel
2015-02-10 17:25       ` Paul E. McKenney
2015-02-10 17:36         ` Frederic Weisbecker
2015-02-10 17:49           ` Paul E. McKenney
2015-02-10 14:41 ` [PATCH 2/6] rcu,nohz: add state parameter to context_tracking_enter/exit riel
2015-02-10 14:41 ` [PATCH 3/6] nohz: add stub context_tracking_is_enabled riel
2015-02-10 14:41 ` [PATCH 4/6] rcu,nohz: run vtime_user_enter/exit only when state == IN_USER riel
2015-02-10 14:41 ` [PATCH 5/6] nohz,kvm: export context_tracking_user_enter/exit riel
2015-02-10 14:41 ` [PATCH 6/6] kvm,rcu,nohz: use RCU extended quiescent state when running KVM guest riel
2015-02-10 19:59   ` Andy Lutomirski
2015-02-10 20:13     ` Rik van Riel
2015-02-10 20:14     ` Paul E. McKenney [this message]
2015-02-10 20:19       ` Andy Lutomirski
2015-02-10 20:42         ` Paul E. McKenney
2015-02-10 21:00           ` Andy Lutomirski
2015-02-10 21:17             ` Paul E. McKenney

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=20150210201402.GU4166@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=lcapitulino@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=oleg@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=riel@redhat.com \
    --cc=will.deacon@arm.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