Re: [PATCH 0/2] RFC use dirty bit for page dirty tracking (v2)

From: Ryan Harper <ryanh@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, Izik Eidus <ieidus@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] RFC use dirty bit for page dirty tracking (v2)
Date: Mon, 6 Jul 2009 22:32:02 -0500	[thread overview]
Message-ID: <20090707033202.GN11590@us.ibm.com> (raw)
In-Reply-To: <4A366679.9020604@redhat.com>

* Avi Kivity <avi@redhat.com> [2009-06-15 10:19]:
> On 06/15/2009 05:58 PM, Ryan Harper wrote:
> >* Izik Eidus<ieidus@redhat.com>  [2009-06-10 11:25]:
> >   
> >>RFC move to dirty bit tracking using the page table dirty bit (v2)
> >>
> >>     
> >
> >Where is this series at?  Did you want me to test one of the ept dirty
> >tracking patches for that hugepage+ept+local migration bug?
> >   
> 
> The first patch (which might cure your oops) is already in qemu-kvm.git, 
> please test it out.

Sorry for taking forever on this... current upstream kvm modules from
kvm-kmod.git are working fine for this.  I believe the final patch that
was committed:

commit e244584fe3a5c20deddeca246548ac86dbc6e1d1
Author: Izik Eidus <ieidus@redhat.com>
Date:   Wed Jun 10 19:23:24 2009 +0300

    KVM: Fix dirty bit tracking for slots with large pages

did the trick.  Should this get pulled back into any of the stable
trees?

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com