[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [patch] more correct pfn_valid()


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Scott Parish" <srparish@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Thu, 19 May 2005 10:36:40 +0100
  • Delivery-date: Thu, 19 May 2005 09:36:15 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVb9aZ7Rlj1GNpbTJqBIcUW7A2ChAAANsGgAAkVbyAACQmCUAAAqYiQAADuuCAAAHE4wAAA0NrwAAAvHuAAAFFFUAABmb1gAABZ/HAAAG5yIA==
  • Thread-topic: [Xen-devel] [patch] more correct pfn_valid()

 

> OK, got it. Then, aside from para-virtualized linux, do you 
> agree that some change should be made to unmodified vmx 
> domain build and DM? When domain creation in CP and when DM 
> services other domain, they shouldn't operate DomN's memory 
> by simply acquiring a plain continuous page_array which has 
> no hole information. Either extra information about hole, or 
> the page_array itself containing hole, should be added thereafter...

vmx domains already have a virtually mapped pfn->mfn table stored within
Xen.
See phys_to_machine_mapping(gpfn)

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.