From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch 2/5] KVM: hypercall based pte updates and TLB flushes Date: Sun, 17 Feb 2008 16:57:36 +0200 Message-ID: <47B84B60.6020508@qumranet.com> References: <20080216220924.733723618@redhat.com>> <20080216221220.843135254@redhat.com>> <47B7F017.10902@qumranet.com> <47B8330B.6050405@qumranet.com> <20080217145148.GA31750@dmt> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net To: Marcelo Tosatti Return-path: In-Reply-To: <20080217145148.GA31750@dmt> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Marcelo Tosatti wrote: > Issue is the paravirt_ops code in Linux does not cover all pte updates > (bit updates, ptep_get_and_clear, etc). > > The plan is to get the basic infrastructure merged into KVM first (which > is a significant improvement already) and then later have paravirt_ops > cover all updates, disabling write protection. > Okay, sounds good. Do you know if anyone is working on extending pv_ops as you describe? -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/