From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86: fix improper return value from relinquish_memory()
Date: Wed, 24 Mar 2010 10:43:13 -0400 [thread overview]
Message-ID: <20100324144313.GB2245@phenom.dumpdata.com> (raw)
In-Reply-To: <4BAA04440200007800036BBB@vpn.id2.novell.com>
On Wed, Mar 24, 2010 at 11:23:32AM +0000, Jan Beulich wrote:
> >>> "Jan Beulich" <JBeulich@novell.com> 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?
Yes.
http://lists.xensource.com/archives/html/xen-devel/2008-12/msg00222.html
B/c of the page count we had guests that would never have their mmap
count removed causing them to be zombie guests. Our fix, which wasn't
nice, was to have the guest domain id re-number and shove it and its
remaining page ownership (at that point it only has some pages in Dom0
and DomU) in a corner.
next prev parent reply other threads:[~2010-03-24 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 11:07 [PATCH] x86: fix improper return value from relinquish_memory() Jan Beulich
2010-03-24 11:23 ` Jan Beulich
2010-03-24 14:43 ` Konrad Rzeszutek Wilk [this message]
2010-03-24 14:54 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100324144313.GB2245@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).