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


[Xen-devel] alloc_heap_pages rejecting several order=6 requests early in

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] alloc_heap_pages rejecting several order=6 requests early in boot (not tmem)
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Fri, 20 Mar 2009 09:34:42 -0700 (PDT)
Delivery-date: Fri, 20 Mar 2009 09:35:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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
Due to some debug code I have in tmem (but otherwise
completely unrelated to tmem), I noticed that,
early in dom0 boot, four requests to alloc_heap_pages
for order=6 are getting rejected.  The allocation
requests are coming from do_memory_op which is
reached via a hypercall.  From console output,
the hypercalls are coming after the dom0 kernel does:

(XEN) Freed 132kB init memory

and the dom0 console output immediately following is:

PCI: BIOS: Bug: MCFG area at e0000000 is not E820-reserved
(XEN) io_apic.c2139:

which may or may not be related to the allocation rejections.

Dom0 boot and everything else proceed fine, so apparently
whatever is requesting the memory recovers or uses some
backup approach (e.g. getting smaller chunks of memory?).

I'm just reporting this because the allocation failures
are otherwise silent, and might be indicative of some
bug (one would think that allocating a 256K chunk
of memory during dom0 boot would always succeed...)
or something that might reduce functionality or performance
in dom0.

I've been seeing this for some time (weeks at least) but
not sure exactly when it started.  It's probably easy
to reproduce by flagging failures in alloc_heap_pages
or turning on gdprintk in memory.c, but if not let
me know and I will look further.


Xen-devel mailing list

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