From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/3] xen: allow extra memory to be two regions
Date: Tue, 16 Aug 2011 16:03:01 +0100 [thread overview]
Message-ID: <4E4A86A5.4030306@citrix.com> (raw)
In-Reply-To: <20110816144801.GA30979@dumpdata.com>
On 16/08/11 15:48, Konrad Rzeszutek Wilk wrote:
> On Tue, Aug 16, 2011 at 03:33:19PM +0100, David Vrabel wrote:
>> On 16/08/11 14:48, Konrad Rzeszutek Wilk wrote:
>>> On Tue, Aug 16, 2011 at 11:00:37AM +0100, David Vrabel wrote:
>>>> Allow the extra memory (used by the balloon driver) to be in two
>>>> regions (typically low and high memory). This allows the balloon
>>>> driver to increase the number of available low pages (if the initial
>>>> number if pages is small).
>>>>
>>>> As a side effect, the algorithm for building the e820 memory map is
>>>> simpler and more obviously correct as the map supplied by the
>>>> hypervisor is (almost) used as is.
>>>
>>> Hm, which is not always good. The setting of 'E820_RESERVED' and 'E820_UNUSABLE',
>>> and realigning of start of balloon space at 4GB (if necessary) changes
>>> need to be preserved. You can look up the why if you run 'git annotate'
>>> and look at those lines - we had lots of time getting those right.
>>
>> My understanding of the history is that the problems were caused by not
>> paying attention to the reserved regions reported in the machine memory
>
> That might have been a problem too, but this is specific to RAM regions.
>> map. This proposed algorithm is careful to only alter RAM regions --
>> all reserved regions and gaps are preserved as-is. I should add some
>> comments explaining this.
>
> We cut RAM regions down and the Linux code thought that they were "gap" spaces
> and used it as PCI I/O space. Hence we marked them as unusable. We need
> that behavior.
Okay. This behaviour is kept as well.
For example, on my test box with 8 GiB RAM with dom0 started with 752
MiB of initial pages and limited to 4 GiB.
[ 0.000000] Xen: 0000000000000000 - 000000000009e000 (usable)
[ 0.000000] Xen: 00000000000a0000 - 0000000000100000 (reserved)
[ 0.000000] Xen: 0000000000100000 - 00000000bf699000 (usable)
[ 0.000000] Xen: 00000000bf699000 - 00000000bf6af000 (reserved)
[ 0.000000] Xen: 00000000bf6af000 - 00000000bf6ce000 (ACPI data)
[ 0.000000] Xen: 00000000bf6ce000 - 00000000c0000000 (reserved)
[ 0.000000] Xen: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] Xen: 00000000fe000000 - 0000000100000000 (reserved)
[ 0.000000] Xen: 0000000100000000 - 0000000140967000 (usable)
[ 0.000000] Xen: 0000000140967000 - 0000000240000000 (unusable)
David
next prev parent reply other threads:[~2011-08-16 15:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 10:00 [RFC] limit dom0 memory using Xen's dom0_mem command line option David Vrabel
2011-08-16 10:00 ` [PATCH 1/3] xen: allow balloon driver to use more than one memory region David Vrabel
2011-08-16 13:38 ` Konrad Rzeszutek Wilk
2011-08-16 14:21 ` David Vrabel
2011-08-16 14:48 ` Konrad Rzeszutek Wilk
2011-08-16 15:03 ` David Vrabel
2011-08-16 10:00 ` [PATCH 2/3] xen: allow extra memory to be two regions David Vrabel
2011-08-16 13:48 ` Konrad Rzeszutek Wilk
2011-08-16 14:33 ` David Vrabel
2011-08-16 14:48 ` Konrad Rzeszutek Wilk
2011-08-16 15:03 ` David Vrabel [this message]
2011-08-16 15:36 ` Konrad Rzeszutek Wilk
2011-08-22 13:55 ` Konrad Rzeszutek Wilk
2011-08-22 14:01 ` David Vrabel
2011-08-16 10:00 ` [PATCH 3/3] xen: use maximum reservation to limit dom0 memory David Vrabel
2011-08-16 13:53 ` Konrad Rzeszutek Wilk
2011-08-16 14:41 ` David Vrabel
2011-08-16 14:54 ` Konrad Rzeszutek Wilk
2011-08-16 14:50 ` Konrad Rzeszutek Wilk
2011-08-16 13:33 ` [RFC] limit dom0 memory using Xen's dom0_mem command line option 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=4E4A86A5.4030306@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.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).