From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH kvm-kmod] adjust timekeeping compatibility code
Date: Tue, 30 Sep 2014 12:39:08 +0200
Message-ID: <542A884C.4000905@redhat.com>
References: <1411460559-8160-1-git-send-email-pbonzini@redhat.com> <542A61AA.4030908@siemens.com> <542A6D2E.5090900@redhat.com> <542A6E67.3070107@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 7bit
To: Jan Kiszka <jan.kiszka@siemens.com>, kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:1471 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751696AbaI3KjO (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 30 Sep 2014 06:39:14 -0400
In-Reply-To: <542A6E67.3070107@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Il 30/09/2014 10:48, Jan Kiszka ha scritto:
>> > +            w('{')
>> > +            w('\treturn __kvm_mmu_notifier_clear_flush_young(mn, mm, hva, hva+1);')
> Ah, end=start+1, it's that easy!
> 

Yes, that's how kvm_handle_hva is implemented on top of
kvm_handle_hva_range.  So, now that kvm_age_hva calls
kvm_handle_hva_range instead of kvm_handle_hva, you can apply the same
technique to the call of kvm_age_hva.

Of course the bug that Andres fixed will remain.

Paolo