From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756397Ab3A2NRB (ORCPT ); Tue, 29 Jan 2013 08:17:01 -0500 Received: from mx1.redhat.com ([209.132.183.28]:14734 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751977Ab3A2NQ5 (ORCPT ); Tue, 29 Jan 2013 08:16:57 -0500 Date: Tue, 29 Jan 2013 15:16:51 +0200 From: Gleb Natapov To: Marcelo Tosatti Cc: Xiao Guangrong , Avi Kivity , LKML , KVM Subject: Re: [PATCH v2 06/12] KVM: MMU: introduce a static table to map guest access to spte access Message-ID: <20130129131651.GD15004@redhat.com> References: <50FFB5A1.5090708@linux.vnet.ibm.com> <50FFB658.6040205@linux.vnet.ibm.com> <20130125001550.GB22875@amt.cnet> <5101F207.6040603@linux.vnet.ibm.com> <20130129000715.GA10814@amt.cnet> <20130129010758.GA12132@amt.cnet> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130129010758.GA12132@amt.cnet> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 28, 2013 at 11:07:58PM -0200, Marcelo Tosatti wrote: > On Mon, Jan 28, 2013 at 10:07:15PM -0200, Marcelo Tosatti wrote: > > On Fri, Jan 25, 2013 at 10:46:31AM +0800, Xiao Guangrong wrote: > > > On 01/25/2013 08:15 AM, Marcelo Tosatti wrote: > > > > On Wed, Jan 23, 2013 at 06:07:20PM +0800, Xiao Guangrong wrote: > > > >> It makes set_spte more clean and reduces branch prediction > > > >> > > > >> Signed-off-by: Xiao Guangrong > > > >> --- > > > >> arch/x86/kvm/mmu.c | 37 ++++++++++++++++++++++++++----------- > > > >> 1 files changed, 26 insertions(+), 11 deletions(-) > > > > > > > > Don't see set_spte as being a performance problem? > > > > IMO the current code is quite simple. > > > > > > Yes, this is not a performance problem. > > > > > > I just dislike this many continuous "if"-s in the function: > > > > > > if (xxx) > > > xxx > > > if (xxx) > > > xxx > > > .... > > > > > > Totally, it has 7 "if"-s before this patch. > > > > > > Okay, if you think this is unnecessary, i will drop this patch. :) > > > > Yes, please (unless you can show set_spte is a performance problem). > > Same thing for spte fast drop: is it a performance problem? > I like spte fast drop because it gets rid of "goto restart" pattern. for_each_spte_in_rmap_safe() can be the alternative. > Please try to group changes into smaller, less controversial sets with > a clear goal: > > - Debated performance improvement. > - Cleanups (eg mmu_set_spte argument removal). > - Bug fixes. > - Performance improvements. > > Thanks. -- Gleb.