From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-kernel@vger.kernel.org, david.vrabel@citrix.com, JBeulich@suse.com
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] auto balloon initial domain and fix dom0_mem=X inconsistencies (v5).
Date: Mon, 16 Apr 2012 13:15:31 -0400 [thread overview]
Message-ID: <1334596539-18172-1-git-send-email-konrad.wilk@oracle.com> (raw)
Changelog v5 [since v4]:
- used populate_physmap, fixed bugs.
[v2-v4: not posted]
- reworked the code in setup.c to work properly.
[v1: https://lkml.org/lkml/2012/3/30/492]
- initial patchset
These patches that did not change between the first posting and this one are:
xen/p2m: Move code around to allow for better re-usage.
xen/p2m: Allow alloc_p2m_middle to call reserve_brk depending on argument
xen/p2m: Collapse early_alloc_p2m_middle redundant checks.
xen/p2m: An early bootup variant of set_phys_to_machine
so if you read them before - you can skip them.
The purpose of these patches is three-fold:
1) Fix the case where dom0_mem=X is not used and the machine boots with less
memory than it should. A subsequent 'xl mem-set 0 X' is required to balloon up
to the right amount. Here is an example of what it looks like with the older
kernels and with a pvops (and the patches):
2.6.32 SLES:
Memory: 7538688k/8079432k available (3971k kernel code, 8192k absent, 532300k reserved, 2491k data, 348k init)
MemTotal: 8063140 kB
MemFree: 7421504 kB
DirectMap4k: 8071240 kB
Domain-0 0 7873 4 r----- 20.3
3.3:
Memory: 6486452k/9208688k available (5825k kernel code, 1136060k absent, 1586176k reserved, 2890k data, 692k init)
MemTotal: 6716156 kB
MemFree: 6365696 kB
DirectMap4k: 8078192 kB
Domain-0 0 6774 4 r----- 26.0
3.3+patches:
Memory: 7621460k/9208688k available (5817k kernel code, 1136060k absent, 451168k reserved, 2899k data, 692k init)
MemTotal: 7849924 kB
MemFree: 7500748 kB
DirectMap4k: 8078192 kB
Domain-0 0 7883 4 r----- 11.9
This is implemented in:
[PATCH 7/8] xen/setup: Populate freed MFNs from non-RAM E820 entries
2). Fix where dom0_mem=XXXG is used (so the 'max' parameter is not involved). The
bug is that we would ignore it:
With dom0_mem=1G
2.6.32 SLES:
Memory: 650240k/1056768k available (3971k kernel code, 8192k absent, 397852k reserved, 2491k data, 348k init)
3.3:
Memory: 610884k/9435136k available (5817k kernel code, 1136060k absent, 7688192k reserved, 2899k data, 696k init)
3.3+patches:
Memory: 724184k/1053064k available (5817k kernel code, 4552k absent, 324328k reserved, 2899k data, 696k init)
This is implemented in:
[PATCH 6/8] xen/setup: Work properly with 'dom0_mem=X' or with not
Note, that the combination of 'dom0_mem=XXXG,max:YYYG' is perfectly fine, so there is no
need to fix that:
With dom0_mem=1G,max:3G
2.6.32 SLES:
Memory: 650240k/1056768k available (3971k kernel code, 8192k absent, 397852k reserved, 2491k data, 348k init)
3.3:
Memory: 690324k/4281724k available (5826k kernel code, 1136060k absent, 2455340k reserved, 2891k data, 692k init)
3.3+patches:
Memory: 690960k/4281724k available (5824k kernel code, 1136060k absent, 2454704k reserved, 2893k data, 692k init)
Konrad Rzeszutek Wilk (8):
xen/p2m: Move code around to allow for better re-usage.
xen/p2m: Allow alloc_p2m_middle to call reserve_brk depending on argument
xen/p2m: Collapse early_alloc_p2m_middle redundant checks.
xen/p2m: An early bootup variant of set_phys_to_machine
xen/setup: Only print "Freeing XXX-YYY pfn range: Z pages freed" if Z > 0
xen/setup: Work properly with 'dom0_mem=X' or with not dom0_mem.
xen/setup: Populate freed MFNs from non-RAM E820 entries and gaps to E820 RAM
xen/setup: Combine the two hypercall functions - since they are quite similar.
arch/x86/include/asm/xen/page.h | 1 +
arch/x86/xen/p2m.c | 104 ++++++++++++++++-----------
arch/x86/xen/setup.c | 152 +++++++++++++++++++++++++++++++++------
3 files changed, 193 insertions(+), 64 deletions(-)
next reply other threads:[~2012-04-16 17:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 17:15 Konrad Rzeszutek Wilk [this message]
2012-04-16 17:15 ` [PATCH 1/8] xen/p2m: Move code around to allow for better re-usage Konrad Rzeszutek Wilk
2012-04-16 17:15 ` [PATCH 2/8] xen/p2m: Allow alloc_p2m_middle to call reserve_brk depending on argument Konrad Rzeszutek Wilk
2012-04-16 17:15 ` [PATCH 3/8] xen/p2m: Collapse early_alloc_p2m_middle redundant checks Konrad Rzeszutek Wilk
2012-04-16 17:15 ` [PATCH 4/8] xen/p2m: An early bootup variant of set_phys_to_machine Konrad Rzeszutek Wilk
2012-04-16 17:15 ` [PATCH 6/8] xen/setup: Work properly with 'dom0_mem=X' or with not dom0_mem Konrad Rzeszutek Wilk
2012-05-03 11:54 ` [Xen-devel] " David Vrabel
2012-04-16 17:15 ` [PATCH 7/8] xen/setup: Populate freed MFNs from non-RAM E820 entries and gaps to E820 RAM Konrad Rzeszutek Wilk
2012-05-03 11:56 ` [Xen-devel] " David Vrabel
2012-04-16 17:15 ` [PATCH 8/8] xen/setup: Combine the two hypercall functions - since they are quite similar Konrad Rzeszutek Wilk
2012-05-03 11:58 ` [Xen-devel] " David Vrabel
2012-05-03 15:37 ` Konrad Rzeszutek Wilk
2012-05-01 16:37 ` [PATCH] auto balloon initial domain and fix dom0_mem=X inconsistencies (v5) Konrad Rzeszutek Wilk
2012-05-02 9:05 ` Jan Beulich
2012-05-03 11:48 ` David Vrabel
2012-05-03 15:15 ` [Xen-devel] " David Vrabel
2012-05-03 16:27 ` David Vrabel
2012-05-07 18:48 ` Konrad Rzeszutek Wilk
2012-05-08 18:12 ` David Vrabel
2012-05-08 18:24 ` Konrad Rzeszutek Wilk
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=1334596539-18172-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.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;
as well as URLs for NNTP newsgroup(s).