From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>, <linux-kernel@vger.kernel.org>,
<xen-devel@lists.xensource.com>, <konrad.wilk@oracle.com>,
<david.vrabel@citrix.com>
Subject: Re: [Xen-devel] [PATCH] xen: delay construction of mfn_list_list
Date: Tue, 14 Oct 2014 17:59:10 +0100 [thread overview]
Message-ID: <543D565E.7020402@citrix.com> (raw)
In-Reply-To: <1413286426-1415-1-git-send-email-jgross@suse.com>
On 14/10/14 12:33, Juergen Gross wrote:
> The 3 level p2m tree for the Xen tools is constructed very early at
> boot by calling xen_build_mfn_list_list(). Memory needed for this tree
> is allocated via extend_brk().
>
> As this tree (other than the kernel internal p2m tree) is only needed
> for domain save/restore, live migration and crash dump analysis it
> doesn't matter whether it is constructed very early or just some
> milliseconds later when memory allocation is possible by other means.
>
> This patch moves the call of xen_build_mfn_list_list() just after
> calling xen_pagetable_p2m_copy() simplifying this function, too, as it
> doesn't have to bother with two parallel trees now. The same applies
> for some other internal functions.
>
> While simplifying code, make early_can_reuse_p2m_middle() static and
> drop the unused second parameter. p2m_mid_identity_mfn can be removed
> as well, it isn't used either.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> arch/x86/xen/enlighten.c | 3 ---
> arch/x86/xen/mmu.c | 5 +++-
> arch/x86/xen/p2m.c | 65 +++++++++++-------------------------------------
> 3 files changed, 18 insertions(+), 55 deletions(-)
Nice!
Applied to stable/for-linus-3.18
Thanks.
David
prev parent reply other threads:[~2014-10-14 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 11:33 Juergen Gross
2014-10-14 16:59 ` David Vrabel [this message]
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=543D565E.7020402@citrix.com \
--to=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome