From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raghavendra K T Subject: Re: [PATCH 1/2] ARM: KVM: Yield CPU when vcpu executes a WFE Date: Tue, 08 Oct 2013 20:32:59 +0530 Message-ID: <52541EA3.7010403@linux.vnet.ibm.com> References: <1381160430-11790-1-git-send-email-marc.zyngier@arm.com> <1381160430-11790-2-git-send-email-marc.zyngier@arm.com> <5253FDDD.6050008@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Raghavendra KT , "linux-arm-kernel@lists.infradead.org" , "kvmarm@lists.cs.columbia.edu" , "kvm@vger.kernel.org" , Christoffer Dall To: Marc Zyngier Return-path: Received: from e28smtp04.in.ibm.com ([122.248.162.4]:45354 "EHLO e28smtp04.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752390Ab3JHPDM (ORCPT ); Tue, 8 Oct 2013 11:03:12 -0400 Received: from /spool/local by e28smtp04.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 8 Oct 2013 20:33:09 +0530 Received: from d28relay02.in.ibm.com (d28relay02.in.ibm.com [9.184.220.59]) by d28dlp03.in.ibm.com (Postfix) with ESMTP id ACB4D1258053 for ; Tue, 8 Oct 2013 20:33:26 +0530 (IST) Received: from d28av02.in.ibm.com (d28av02.in.ibm.com [9.184.220.64]) by d28relay02.in.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r98F5f4E24313866 for ; Tue, 8 Oct 2013 20:35:41 +0530 Received: from d28av02.in.ibm.com (localhost [127.0.0.1]) by d28av02.in.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id r98F32CZ024370 for ; Tue, 8 Oct 2013 20:33:03 +0530 In-Reply-To: <5253FDDD.6050008@arm.com> Sender: kvm-owner@vger.kernel.org List-ID: [...] >>> + kvm_vcpu_on_spin(vcpu); >> >> Could you also enable CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT for arm and >> check if ple handler logic helps further? >> we would ideally get one more optimization folded into ple handler if >> you enable that. > > Just gave it a go, and the results are slightly (but consistently) > worse. Over 10 runs: > > Without RELAX_INTERCEPT: Average run 3.3623s > With RELAX_INTERCEPT: Average run 3.4226s > > Not massive, but still noticeable. Any clue? Is it a 4x overcommit? Probably we would have hit the code overhead if it were small guests. RELAX_INTERCEPT is worth enabling for large guests with overcommits.