From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Page Eviction Algorithm Date: Thu, 28 Oct 2010 10:45:07 +0200 Message-ID: <4CC93813.708@redhat.com> References: <4CC6ADF1.9000805@redhat.com> <4CC6D292.3050703@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Prasad Joshi Return-path: Received: from mx1.redhat.com ([209.132.183.28]:30920 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750705Ab0J1IpK (ORCPT ); Thu, 28 Oct 2010 04:45:10 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 10/26/2010 05:08 PM, Prasad Joshi wrote: > >>> > >>> Can you please suggest me something that would add value to KVM? > >>> > >> > >> O(1) write protection (on the TODO page) is interesting and important. It's > >> difficult, so you may want to start with O(1) invalidation. > > > > I am not sure if I can understand what exactly is a MMU invalidation. > > Is it cache invalidation or TLB invalidation? Can you please > > elaborate. I am really sorry if I am asking a silly question. > > Does this MMU invalidation has to do something with the EPT (Extended > Page Table) No > and instruction INVEPT? No, (though INVEPT has to be run as part of this operation, via kvm_flush_remote_tlbs). -- error compiling committee.c: too many arguments to function