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] x86: fix improper return value from relinquish_m

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] x86: fix improper return value from relinquish_memory()
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Wed, 24 Mar 2010 11:23:32 +0000
Delivery-date: Wed, 24 Mar 2010 04:24:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4BAA00870200007800036B93@xxxxxxxxxxxxxxxxxx>
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: <4BAA00870200007800036B93@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> "Jan Beulich" <JBeulich@xxxxxxxxxx> 24.03.10 12:07 >>>
>While apparently only a theoretical possibility (domain_kill() has a
>BUG_ON() that wasn't reported to trigger so far), I still think it is
>better to have the code cleaned up.

Btw., the reason I was looking at that code was that we observe
zombie domains - ones in DOMDYING_dead state, perhaps having
almost none of their memory freed (shadowed guests appear to be
particularly bad). In one of the reports, an interesting extra fact
was that this happened only for the first 100 guests - any
subsequent ones got destroyed properly (obviously to get there
this requires quite a bit of memory in the host). Has anyone else
observed this? Does this ring any bells?


Xen-devel mailing list