WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [XenPPC] Re: [Xen-ia64-devel] [PATCH 1/2] remove xencomm page size l

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: Re: [XenPPC] Re: [Xen-ia64-devel] [PATCH 1/2] remove xencomm page size limit(xen side)
From: Hollis Blanchard <hollisb@xxxxxxxxxx>
Date: Thu, 02 Aug 2007 10:00:46 -0500
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx, Alex Williamson <alex.williamson@xxxxxx>, xen-ppc-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 02 Aug 2007 07:58:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070802024439.GB6395%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: IBM Linux Technology Center
References: <20070731061019.GB6039%yamahata@xxxxxxxxxxxxx> <1185913517.6802.74.camel@bling> <20070801063654.GD14448%yamahata@xxxxxxxxxxxxx> <1185995274.15389.21.camel@basalt> <20070802024439.GB6395%yamahata@xxxxxxxxxxxxx>
Reply-to: Hollis Blanchard <hollisb@xxxxxxxxxx>
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2007-08-02 at 11:44 +0900, Isaku Yamahata wrote:
> 
> > But we can issue sequential p2m hcalls with different offsets, so we
> do.
> > So what exactly is the new problem?
> 
> The limit is about 64GB for xen/ia64 because xen/ia64 deafult page
> size
> is 16KB.
> The issue I'm seeing is the populate physmap hypercall failure
> at domain creation. It's essentially same issue you described above.
> I want to remove the limitation with the patches. 

Can't you simply issue repeated populate_physmap hypercalls,
incrementing extent_start?

Or, since you in fact probably don't need access to all 100GB during
domain creation, can't you just map the area you need?

> > (As a side question, is it really so difficult for you guys to just use
> > the common code? I tried very hard to make it easy for you to just
> > implement a couple hooks; I can't imagine it would take more than a day
> > to do it.)
> 
> Sorry for that. It seems to be good time to resolve it.
> I'll work on xencomm consolidation.

No need to apologize, I'm just surprised that with all your xencomm work
it hasn't already been done.

-- 
Hollis Blanchard
IBM Linux Technology Center


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