From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [PATCH v2] kvm/x86: Inform RCU of quiescent state when entering guest mode Date: Wed, 11 Jul 2018 20:39:36 +0200 Message-ID: <62e945ee-a58e-f9b3-279c-74cd0f5809da@de.ibm.com> References: <20180711174843.GX3593@linux.vnet.ibm.com> <20180711180101.3711464-1-dwmw2@infradead.org> <20180711182053.GA3593@linux.vnet.ibm.com> <20180711183645.GA23820@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: peterz@infradead.org, mhillenb@amazon.de, linux-kernel@vger.kernel.org, kvm@vger.kernel.org To: paulmck@linux.vnet.ibm.com, David Woodhouse Return-path: In-Reply-To: <20180711183645.GA23820@linux.vnet.ibm.com> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 07/11/2018 08:36 PM, Paul E. McKenney wrote: > On Wed, Jul 11, 2018 at 11:20:53AM -0700, Paul E. McKenney wrote: >> On Wed, Jul 11, 2018 at 07:01:01PM +0100, David Woodhouse wrote: >>> From: David Woodhouse >>> >>> RCU can spend long periods of time waiting for a CPU which is actually in >>> KVM guest mode, entirely pointlessly. Treat it like the idle and userspace >>> modes, and don't wait for it. >>> >>> Signed-off-by: David Woodhouse >> >> And idiot here forgot about some of the debugging code in RCU's dyntick-idle >> code. I will reply with a fixed patch. >> >> The code below works just fine as long as you don't enable CONFIG_RCU_EQS_DEBUG, >> so should be OK for testing, just not for mainline. > > And here is the updated code that allegedly avoids splatting when run with > CONFIG_RCU_EQS_DEBUG. > > Thoughts? > > Thanx, Paul > > ------------------------------------------------------------------------ > > commit 12cd59e49cf734f907f44b696e2c6e4b46a291c3 > Author: David Woodhouse > Date: Wed Jul 11 19:01:01 2018 +0100 > > kvm/x86: Inform RCU of quiescent state when entering guest mode > > RCU can spend long periods of time waiting for a CPU which is actually in > KVM guest mode, entirely pointlessly. Treat it like the idle and userspace > modes, and don't wait for it. > > Signed-off-by: David Woodhouse > Signed-off-by: Paul E. McKenney > [ paulmck: Adjust to avoid bad advice I gave to dwmw, avoid WARN_ON()s. ] > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index 0046aa70205a..b0c82f70afa7 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -7458,7 +7458,9 @@ static int vcpu_enter_guest(struct kvm_vcpu *vcpu) > vcpu->arch.switch_db_regs &= ~KVM_DEBUGREG_RELOAD; > } > > + rcu_kvm_enter(); > kvm_x86_ops->run(vcpu); > + rcu_kvm_exit(); As indicated in my other mail. This is supposed to be handled in the guest_enter|exit_ calls around the run function. This would also handle other architectures. So if the guest_enter_irqoff code is not good enough, we should rather fix that instead of adding another rcu hint.