From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mukesh Rathor Subject: [hybrid] : mmap pfn space... Date: Fri, 23 Mar 2012 11:01:44 -0700 Message-ID: <20120323110144.4b2f1d45@mantra.us.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Xen-devel@lists.xensource.com" , Ian Campbell , "stefano.stabellini@eu.citrix.com" List-Id: xen-devel@lists.xenproject.org Hi Ian/Stefano, So, I'm back to using pfn space from maxphysaddr below. Stefano, you suggested ballooning, but that would be just too slow. There are lot of pages to be mapped, 4k at a time during guest creation, and I am afraid ballooning and hypercalls to populate EPT will be pretty slow. OTOH, there is tons of address space available between max-physaddr and max pfn in dom0. Stefano, your concern was stuff mapped there causing problems in future. But we can always look at the e820 for conflicts. Keeping things fast is important for us . Please let me know if you still have issues with my approach. I believe this is what Ian is doing on ARM port. thanks, Mukesh