From: Julien Grall <julien.grall@linaro.org>
To: Andrii Anisov <andrii.anisov@globallogic.com>
Cc: Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Restart domU failure (memory allocation issue)
Date: Fri, 14 Mar 2014 12:15:17 +0000 [thread overview]
Message-ID: <5322F2D5.9020906@linaro.org> (raw)
In-Reply-To: <CAGQvs6hT-8nS4cfhqNbJsEeDXsnjEwrJn3WmB7FLLT+wTmMqhg@mail.gmail.com>
Hello Andrii,
On 03/14/2014 11:14 AM, Andrii Anisov wrote:
> From the investigations done by Oleksandr it seems to me that some
> mappings done for so called kernel segment by xc_dom_alloc_segment()
> are left in dom0 space.
>
> Actually I do not see how pages from domU space (i.e. that kernel
> segment) are unmapped from dom0 after domain creation.
It seems that unmap will be done at the end of xc_dom_boot_image (see
xc_dom_unmap_all).
The latter function will go through the list of all mappings and close
it one by one.
You can add a print in xc_dom_unmap_one (tools/libxc/xc_dom_core.c) and
check if you have the same number of print with xc_dom_pfn_to_ptr_retcount.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-03-14 12:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 18:33 Restart domU failure (memory allocation issue) Oleksandr Tyshchenko
2014-03-13 19:48 ` Julien Grall
2014-03-14 11:10 ` Andrii Anisov
2014-03-14 11:14 ` Andrii Anisov
2014-03-14 12:15 ` Julien Grall [this message]
2014-03-14 12:45 ` Andrii Anisov
2014-03-14 14:00 ` Julien Grall
2014-03-14 14:05 ` Andrii Anisov
2014-03-14 14:17 ` Julien Grall
2014-03-14 14:37 ` Oleksandr Tyshchenko
2014-03-14 14:08 ` Oleksandr Tyshchenko
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=5322F2D5.9020906@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=andrii.anisov@globallogic.com \
--cc=oleksandr.tyshchenko@globallogic.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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).