From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pv_ops & gntdev? Date: Wed, 25 Feb 2009 12:06:21 -0800 Message-ID: <49A5A4BD.7080207@goop.org> References: <49A44030.2070709@redhat.com> <49A4640E.1000807@goop.org> <49A470DD.2000008@redhat.com> <49A517F6.30005@redhat.com> <49A58506.2020407@goop.org> <49A58FFF.3050604@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49A58FFF.3050604@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gerd Hoffmann Cc: Xen Development Mailing List List-Id: xen-devel@lists.xenproject.org Gerd Hoffmann wrote: >> Yes, my plan is: >> >> 1. when installing a grant in a pte page, allocate a shadow page and >> hang it off page->private; also set a page flag on the pgd page >> flags (steal something spare) >> > > pgd or pte page flags? or both? > Just pgd, so that the unpinner can see it needs to make a second pass. At the pte level, looking for a non-NULL page->private should be enough. >> 3. when clearing the pte, check to see if there's a grant handle and >> zap it >> > > That needs a new paravirt hook I think ... > Hm, I hope not. Doesn't it always end up using set_pte*? >> 4. when unpinning the pagetable, check to see if there's the "grant >> mapping" flag in the pgd, and do a grant-zap pass before unpinning >> > > ok. > > Prelimary patches by chance? > No, I haven't got around to implementing this at all. Thanks, J