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/
Home Products Support Community News


Re: [Xen-devel] [PATCH 2 of 4] x86: make the pv-only e820 array be dynam

To: Keir Fraser <keir@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2 of 4] x86: make the pv-only e820 array be dynamic
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 12 Apr 2011 08:53:17 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Ian.Campbell@xxxxxxxxxx, Tim.Deegan@xxxxxxxxxx
Delivery-date: Tue, 12 Apr 2011 05:54:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C9CA04D1.2C8FB%keir@xxxxxxx>
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>
References: <e7057fec103ba69776d1.1302557732@xxxxxxxxxxxxxxxxxxxxxxx> <C9CA04D1.2C8FB%keir@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-06-14)
On Tue, Apr 12, 2011 at 01:32:01PM +0100, Keir Fraser wrote:
> On 11/04/2011 22:35, "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:
> > # HG changeset patch
> > # User Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
> > # Date 1302295108 14400
> > # Node ID e7057fec103ba69776d157d470d630ce99dbc540
> > # Parent  0f279f43f41ffa8549e076f2a30f499bd8d6cc1d
> > x86: make the pv-only e820 array be dynamic.
> > 
> > During creation of the PV domain we allocate the E820 structure to
> > have the amount of E820 entries on the machine, plus the number three.
> How cunning.
> Why wouldn't you just allocate exactly the right size of array in
> XENMEM_set_memory_map?

I was thinking about it, but the mm.c code did not have the
xen/xmalloc.h header, nor any references to xmalloc_array.

Is it OK to make an xmalloc_array during a hypercall?

Xen-devel mailing list

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