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

From: Avi Kivity <avi@redhat.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Izik Eidus <ieidus@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] RFC use dirty bit for page dirty tracking (v2)
Date: Tue, 07 Jul 2009 08:11:01 +0300	[thread overview]
Message-ID: <4A52D8E5.604@redhat.com> (raw)
In-Reply-To: <20090707033202.GN11590@us.ibm.com>

On 07/07/2009 06:32 AM, Ryan Harper wrote:
> * 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?
>
>    

It's in 2.6.30.1 and hopefully on its way to the other trees.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.