From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
Alex Williams <awilliams@iweb.com>
Subject: Re: Possible regression: XEN 4.0.0 total_memory decrease
Date: Fri, 16 Apr 2010 18:37:36 +0100 [thread overview]
Message-ID: <C7EE5EF0.11823%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BC83396020000780003A934@vpn.id2.novell.com>
On 16/04/2010 08:53, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> Keir Fraser <keir.fraser@eu.citrix.com> 15.04.10 20:23 >>>
>> I've fixed this regression as xen-unstable:21190 and xen-4.0-testing:21114.
>> The fix will appear in Xen 4.0.1.
>
> That seems wrong to me - I specifically changed the accounting so
> that pieces not used from the E820 map (which can no longer be cut
> off in e820.c, as that code doesn't know *where* to cut off) won't
> get reported as available memory. The real question is where (for
> the non-cut-off case) the two calculations differ.
boot_e820 has chunks cut out of it for stashing kexec stuff, as well as all
the multiboot modules. The value thereby obtained is just confusing to users
who think we've binned possibly 100s of megabytes (if they run a big
initrd).
-- Keir
next prev parent reply other threads:[~2010-04-16 17:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 15:54 Possible regression: XEN 4.0.0 total_memory decrease Alex Williams
2010-04-15 16:33 ` Keir Fraser
2010-04-15 17:33 ` Alex Williams
2010-04-15 17:42 ` Alex Williams
2010-04-15 18:05 ` Keir Fraser
2010-04-15 18:23 ` Keir Fraser
2010-04-16 7:53 ` Jan Beulich
2010-04-16 17:37 ` Keir Fraser [this message]
2010-04-19 7:35 ` Jan Beulich
2010-04-19 7:51 ` Keir Fraser
2010-04-15 18:26 ` Alex Williams
2010-04-15 18:34 ` Keir Fraser
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=C7EE5EF0.11823%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=Xen-devel@lists.xensource.com \
--cc=awilliams@iweb.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).