From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Date: Thu, 29 Mar 2012 15:21:05 +0000
Subject: Re: Question about removing memslots
Message-Id: <20120330002105.a66858d82bdd1802cae7b401@gmail.com>
List-Id: <kvm-ppc.vger.kernel.org>
References: <1332919486.2882.88.camel@pasglop>
	<4F72DBE2.6060909@redhat.com>
	<20120329141553.3bc61de3.yoshikawa.takuya@oss.ntt.co.jp>
	<4F742EEC.3020501@redhat.com>
In-Reply-To: <4F742EEC.3020501@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Avi Kivity <avi@redhat.com>
Cc: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, kvm@vger.kernel.org, Alexander Graf <agraf@suse.de>, kvm-ppc@vger.kernel.org, Scott Wood <scottwood@freescale.com>, Alex Williamson <Alex.Williamson@redhat.com>

On Thu, 29 Mar 2012 11:44:12 +0200
Avi Kivity <avi@redhat.com> wrote:

> > Even without using reverse mapping we can restrict that flush easily:
> >
> > 	http://www.spinics.net/lists/kvm/msg68695.html
> > 	[PATCH] KVM: Avoid zapping unrelated shadows in __kvm_set_memory_region()
> >
> > This would be better than using reverse mapping because we do not have so
> > many shadow pages when we are in a tight loop like you mensioned.
> >
> > Anyway we could easily see tens of milliseconds difference by eliminating
> > unrelated flush.
> 
> Hm, the patch uses ->slot_bitmap which we might want to kill if we
> increase the number of slots dramatically, as some people want to do.
> 
> btw, what happened to that patch, did it just get ignored on the list?

I did not get any comments, maybe because it was during around your vacation.

	Takuya