[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v5 3/4] xen: implement guest_physmap_pin_range and guest_physmap_unpin_range
On Mon, 2013-09-09 at 17:06 +0100, Stefano Stabellini wrote: > > +static int pin_one_pte(lpae_t *ptep, void *arg, int level) > +{ > + lpae_t pte = *ptep; > + ASSERT(level == 3); > + > + if ( pte.p2m.avail & P2M_DMA_PIN ) > + return -EBUSY; > + pte.p2m.avail |= P2M_DMA_PIN; > + write_pte(ptep, pte); > + return 0; > +} > + > +int guest_physmap_pin_range(struct domain *d, > + xen_pfn_t gpfn, > + unsigned int order) > +{ > + return p2m_walker(d, gpfn << PAGE_SHIFT, order, > + pin_one_pte, NULL); Did we not also discuss accounting and limits on the amount of memory a guest can lock down? _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |