xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jonathan Tripathy <jonnyt@abpni.co.uk>, xen-devel@lists.xen.org
Subject: Re: Can't see more than 3.5GB of RAM / UEFI / no e820 memory map detected
Date: Tue, 28 Aug 2012 23:31:49 +0100	[thread overview]
Message-ID: <CC630565.3D228%keir.xen@gmail.com> (raw)
In-Reply-To: <503D3D2E.70103@abpni.co.uk>

On 28/08/2012 22:50, "Jonathan Tripathy" <jonnyt@abpni.co.uk> wrote:

>>>>> I reversed the if block in setup.c and now my server can see the full
>>>>> 32GB of RAM. I haven't submitted a patch yet as we have run into another
>>>>> (possibly unrelated to xen) issue with this server build that we are
>>>>> working on. Once we complete our full testing, a patch will be submitted
>>>>> :)
>>>> In this case, I will re-make the patch myself and check it in. Since it is
>>>> a
>>>> trivial one.
>>>> 
>>>>     Thanks,
>>>>    Keir
>>> Thanks Keir
>> Now done. xen-unstable:25786
>> 
>>   -- Keir
> Hi Keir,
> 
> Thanks for doing that. However, the ordering of the if block in my code
> that I used was slightly different from your commit. Perhaps this
> doesn't make too much of a difference?

Your ordering favours Multiboot-e820 over Xen-e820, which we do not want to
do, and Multiboot-e801 over Xen-e820 which is definitely not sane.

I see you tested the checked-in version and it worked okay for you, which is
expected, and is a more sensible re-ordering. :)

 -- Keir

  parent reply	other threads:[~2012-08-28 22:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50356E43.3030208@abpni.co.uk>
2012-08-22 23:48 ` Can't see more than 3.5GB of RAM Jonathan Tripathy
2012-08-23  0:11   ` Jonathan Tripathy
2012-08-23  6:06   ` Can't see more than 3.5GB of RAM / UEFI / no e820 memory map detected Pasi Kärkkäinen
2012-08-23  7:22     ` Pasi Kärkkäinen
2012-08-23  7:27       ` Jonathan Tripathy
2012-08-23  7:39         ` Jan Beulich
2012-08-23  8:07           ` Jonathan Tripathy
2012-08-24 15:35             ` Jan Beulich
2012-08-24 17:39               ` Jonathan Tripathy
2012-08-24 20:05                 ` Keir Fraser
2012-08-28 19:36                   ` Jonathan Tripathy
2012-08-28 21:10                     ` Keir Fraser
2012-08-28 21:13                       ` Jonathan Tripathy
2012-08-28 21:37                         ` Keir Fraser
2012-08-28 21:41                         ` Keir Fraser
2012-08-28 21:50                           ` Jonathan Tripathy
2012-08-28 21:52                             ` Jonathan Tripathy
2012-08-28 22:05                               ` Jonathan Tripathy
2012-08-28 22:31                             ` Keir Fraser [this message]
2012-08-28 22:33                               ` Jonathan Tripathy
2012-08-23  8:12         ` Keir Fraser
2012-08-23  8:28           ` Jonathan Tripathy
2012-08-23  8:43             ` Keir Fraser
2012-08-23  8:49               ` Ian Campbell
2012-08-23  8:58               ` Jonathan Tripathy
2012-08-23  9:43                 ` Keir Fraser
2012-08-23  9:13             ` Pasi Kärkkäinen
2012-08-23  9:50 Jonathan Tripathy
2012-08-23 11:17 ` 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=CC630565.3D228%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=jonnyt@abpni.co.uk \
    --cc=xen-devel@lists.xen.org \
    /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).