From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2] xen: prevent PVH Dom0 from having pages with more than one ref
Date: Fri, 13 Jun 2014 17:49:08 +0200 [thread overview]
Message-ID: <539B1D74.3050909@citrix.com> (raw)
In-Reply-To: <539AE522.1080607@citrix.com>
On 13/06/14 13:48, Andrew Cooper wrote:
> On 13/06/14 12:43, Roger Pau Monne wrote:
>> With the current implementation of the Dom0 domain builder a PVH Dom0
>> ends up with pages that have 2 references, which means they are not
>> freed when Dom0 balloons memory down. This leads to those pages
>> not being freed in guest_remove_page, so they are leaked and the
>> memory accounting between Xen and Dom0 differs, because Dom0 OS
>> actually thinks they are freed, but d->tot_pages is not decreased.
>
> Please can you explain the cause of the problem, and state that it is a
> difference between PV and HVM memory management.
What about the following commit message:
xen: prevent PVH Dom0 from having pages with more than one ref
On PV guests a reference is taken when a page gets added to the page
tables, which makes pages added to the page tables have two references,
but this is not suitable for PVH that doesn't use the PVMMU. In the PVH
case only one reference has to be taken or else the page would not be
freed when the memory of the domain is decreased.
Roger.
next prev parent reply other threads:[~2014-06-13 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 11:43 [PATCH v2] xen: prevent PVH Dom0 from having pages with more than one ref Roger Pau Monne
2014-06-13 11:48 ` Andrew Cooper
2014-06-13 15:49 ` Roger Pau Monné [this message]
2014-06-14 1:11 ` Mukesh Rathor
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=539B1D74.3050909@citrix.com \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.