From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mario Smarduch <m.smarduch@samsung.com>
Subject: Re: KVM: HAVE_KVM_ARCH_DIRTY_LOG_PROTECT?
Date: Thu, 22 Jan 2015 09:47:53 -0800
Message-ID: <54C137C9.1060906@samsung.com>
References: <1421918381.13638.43.camel@x220> <54C0E2FF.6050607@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Paul Bolle <pebolle@tiscali.nl>,
	Valentin Rothberg <valentinrothberg@gmail.com>,
	Christoffer Dall <christoffer.dall@linaro.org>,
	Gleb Natapov <gleb@kernel.org>, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
To: Paolo Bonzini <pbonzini@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-reply-to: <54C0E2FF.6050607@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

On 01/22/2015 03:46 AM, Paolo Bonzini wrote:
> 
> 
> On 22/01/2015 10:19, Paul Bolle wrote:
>> Mario,
>>
>> Your commit ba0513b5b8ff ("KVM: Add generic support for dirty page
>> logging") is included in today's linux-next (ie, next-20150122). I
>> noticed because a script I use to check linux-next spotted a problem
>> with it.
>>
>> That commit added a Kconfig symbol HAVE_KVM_ARCH_DIRTY_LOG_PROTECT. But
>> nothing in linux-next uses that symbol. Why was it added?
> 
> That's a bug.  I'll fix it when pulling from the kvm-arm tree.
> 
> Paolo
> 

Paolo,
   thanks, left over from early iteration.

- Mario