From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Thomas Goirand <thomas@goirand.fr>
Cc: xen-devel@lists.xensource.com
Subject: Re: Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages
Date: Mon, 12 Apr 2010 12:34:01 -0700 [thread overview]
Message-ID: <4BC375A9.1060904@goop.org> (raw)
In-Reply-To: <4BC19B2A.3040501@goirand.fr>
On 04/11/2010 02:49 AM, Thomas Goirand wrote:
>> Excellent.
>>
> Could this be also the reason why I had very funky memory management
> (eg: some RAM missing between "xm list" and "xm info")?
>
I don't think so. Before I added the "unused memory freeing" code, then
you'd see memory assigned to a domain that the domain itself couldn't
use, and so it was effectively wasted. With the memory-freeing in
place, the "xm list" and the domain's internal view of memory should be
basically the same.
Either way, it shouldn't have any effect on the global memory accounting
shown by xm info.
J
next prev parent reply other threads:[~2010-04-12 19:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 11:34 Debian linux-image-2.6.32-4-xen-amd64 2.6.32-11 doesn't boot with > 4 GiB; resets immediatelly, no log messages Thomas Schwinge
2010-04-08 13:38 ` Konrad Rzeszutek Wilk
2010-04-08 13:42 ` Ian Campbell
2010-04-08 22:19 ` Thomas Schwinge
2010-04-08 22:51 ` Jeremy Fitzhardinge
2010-04-09 18:00 ` Thomas Schwinge
2010-04-09 18:20 ` Jeremy Fitzhardinge
2010-04-10 22:13 ` Thomas Schwinge
2010-04-10 22:52 ` Jeremy Fitzhardinge
2010-04-11 9:49 ` Thomas Goirand
2010-04-12 19:34 ` Jeremy Fitzhardinge [this message]
2010-04-13 1:20 ` Thomas Goirand
2010-04-13 6:02 ` Pasi Kärkkäinen
2010-04-13 9:48 ` Thomas Goirand
2010-04-13 9:52 ` Pasi Kärkkäinen
2010-04-13 10:08 ` Thomas Goirand
2010-04-13 19:50 ` Jeremy Fitzhardinge
2010-04-13 22:27 ` Thomas Goirand
2010-04-13 23:16 ` Mike Viau
2010-04-13 23:59 ` Jeremy Fitzhardinge
2010-04-14 5:48 ` Thomas Goirand
2010-04-20 11:18 ` Thomas Schwinge
2010-04-20 18:19 ` Jeremy Fitzhardinge
2010-04-28 21:21 ` Jeremy Fitzhardinge
2010-05-08 15:46 ` Thomas Schwinge
2010-05-08 23:01 ` Jeremy Fitzhardinge
2010-05-10 9:48 ` Thomas Schwinge
2010-04-09 18:52 ` 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=4BC375A9.1060904@goop.org \
--to=jeremy@goop.org \
--cc=thomas@goirand.fr \
--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 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.