[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:31:07 +0800
  • Delivery-date: Thu, 19 May 2005 09:30:44 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVb9aZ7Rlj1GNpbTJqBIcUW7A2ChAAANsGgAAkVbyAACQmCUAAAqYiQAADuuCAAAHE4wAAA0NrwAAAvHuAAAFFFUAABmb1gAABZ/HA=
  • 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:14 PM
>
>> Is that assumption right?
>
>Yes, that's it.

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...

>
>> BTW, will that make some
>> complexities for non-access operation, like comparison upon
>> some address?
>
>Linux doesn't do this (It doesn't make sense anyhow).

Keep my mouth close now until I convince myself with more knowledge from
Linux. :)

- Kevin

_______________________________________________
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®.