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

Re: [Xen-devel] Hyp compat_memory_op() and 256 GB PV

To: "mukesh.rathor@xxxxxxxxxx" <mukesh.rathor@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Hyp compat_memory_op() and 256 GB PV
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 18 Feb 2009 08:23:28 +0000
Cc:
Delivery-date: Wed, 18 Feb 2009 00:24:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <499B830A.5050301@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmRerRsCB2c4npEReGp1eidadZfsAAJ3hu+
Thread-topic: [Xen-devel] Hyp compat_memory_op() and 256 GB PV
User-agent: Microsoft-Entourage/12.15.0.081119
On 18/02/2009 03:39, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:

> Moving on to 256 GB guest, the hyp is failing the XENMEM_populate_physmap
> hcall in compat_memory_op(). The problem is size too large for continuation
> encoding:
> 
>      /* Is size too large for us to encode a continuation? */
>      if ( cmp.rsrv.nr_extents > (UINT_MAX >> MEMOP_EXTENT_SHIFT))
>          return start_extent;
> 
>       for 256 GB : nr_extents == 0x4000000
> 
>   Currently at a loss on this one!

Well, who's making the compat call? Not the guest itself presumably since it
is 64-bit? So it's probably dom0? But I would think that dom0 would only do
large amounts of allocation for the new domU in xc_hvm_build.c, and that is
careful to allocate memory in batches of 8MB at a time.

Basically you need to track down the call site of the failed
compat_memory_op().

 -- Keir



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

<Prev in Thread] Current Thread [Next in Thread>