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

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

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

>-----Original Message-----
>From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx]
>Sent: Thursday, May 19, 2005 5:37 PM
>> 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
>See phys_to_machine_mapping(gpfn)

Yes, as you said earlier. But it's not used by CP and DM by far, which
still go to page_array style. :( I just mean some change may be required
there for CP and DM to correctly manipulate other domain's memory. 


Xen-devel mailing list



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