From: Jeremy Fitzhardinge <jeremy@goop.org>
To: roberto@unbit.it
Cc: jeremy@xensource.com, linux-kernel@vger.kernel.org,
Mirko Iannella <mirko@unbit.it>, Ingo Molnar <mingo@elte.hu>,
Alex Nixon <alex.nixon@citrix.com>
Subject: Re: Fix for xen guest with mem > 3.7G
Date: Sat, 13 Sep 2008 14:09:38 -0700 [thread overview]
Message-ID: <48CC2C12.4080302@goop.org> (raw)
In-Reply-To: <1221333418.6036.9.camel@sirius>
Roberto De Ioris wrote:
> Xen domU kernel 2.6.26 and 2.6.27-rc cannot allocate
> more than 3.7GB of ram on my PAE systems (compiled
> with gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)).
>
> I have found the problem is in function xen_memory_setup (in
> arch/x86/xen/setup.c).
>
> It set max_pfn as 'unsigned long' but add_memory_region()
> takes 'unsigned long long'.
>
> I do not know if it is a compiler problem but this is the simple fix
> (works on my systems):
>
Thanks very much for the patch. We have a more general fix for this in
Ingo's tip.git tree, but I overlooked that this particular problem
affected current -rc.
Ingo, this is fixed by the phys_addr_t + PFN_PHYS() patches. Should we
send them up to Linus, or do an ad-hoc fix in this one place?
Thanks,
J
> --- setup.c.orig 2008-09-13 21:12:56.000000000 +0200
> +++ setup.c 2008-09-13 20:35:29.000000000 +0200
> @@ -36,7 +36,7 @@
>
> char * __init xen_memory_setup(void)
> {
> - unsigned long max_pfn = xen_start_info->nr_pages;
> + unsigned long long max_pfn = xen_start_info->nr_pages;
>
> e820.nr_map = 0;
> add_memory_region(0, LOWMEMSIZE(), E820_RAM);
>
>
>
>
next prev parent reply other threads:[~2008-09-13 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 19:16 Fix for xen guest with mem > 3.7G Roberto De Ioris
2008-09-13 21:09 ` Jeremy Fitzhardinge [this message]
2008-09-14 13:21 ` Ingo Molnar
2008-09-14 14:42 ` [PATCH] xen: " Jeremy Fitzhardinge
2008-09-14 14:47 ` Ingo Molnar
2008-09-14 21:43 ` Roberto De Ioris
2008-09-15 6:09 ` Jeremy Fitzhardinge
2008-09-15 6:20 ` Roberto De Ioris
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=48CC2C12.4080302@goop.org \
--to=jeremy@goop.org \
--cc=alex.nixon@citrix.com \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mirko@unbit.it \
--cc=roberto@unbit.it \
/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.