From mboxrd@z Thu Jan 1 00:00:00 1970 From: Izik Eidus Subject: Re: [PATCH] mmu_notifier, kvm: Introduce dirty bit tracking in spte and mmu notifier to help KSM dirty bit tracking Date: Wed, 22 Jun 2011 18:19:26 +0300 Message-ID: <4E0207FE.9080002@ravellosystems.com> References: <201106212055.25400.nai.xia@gmail.com> <201106212132.39311.nai.xia@gmail.com> <20110622150350.GX20843@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nai Xia , Andrew Morton , Hugh Dickins , Chris Wright , Rik van Riel , linux-mm , Johannes Weiner , linux-kernel , kvm To: Andrea Arcangeli Return-path: In-Reply-To: <20110622150350.GX20843@redhat.com> Sender: owner-linux-mm@kvack.org List-Id: kvm.vger.kernel.org > If we don't flush the smp tlb don't we risk that we'll insert pages in > the unstable tree that are volatile just because the dirty bit didn't > get set again on the spte? Yes, this is the trade off we take, the unstable tree will be flushed anyway - so this is nothing that won`t be recovered very soon after it happen... and most of the chances the tlb will be flushed before ksm get there anyway (specially for heavily modified page, that we don`t want in the unstable tree) -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org