xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86: make sure memory block is RAM before passing to the allocator
Date: Mon, 04 Nov 2013 13:25:43 +0000	[thread overview]
Message-ID: <CE9D50D7.3CC9D%keir.xen@gmail.com> (raw)
In-Reply-To: <5277842A02000078000FEF63@nat28.tlf.novell.com>

On 04/11/2013 10:25, "Jan Beulich" <JBeulich@suse.com> wrote:

> Memory blocks outside of the always visible 1:1 mapping range get
> passed to the allocator separately (once enough other setup was done).
> Skipping non-RAM regions, however, was forgotten in adc5afbf ("x86:
> support up to 16Tb").
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Keir Fraser <keir@xen.org>

> --- a/xen/arch/x86/setup.c
> +++ b/xen/arch/x86/setup.c
> @@ -1155,6 +1155,8 @@ void __init __start_xen(unsigned long mb
>          {
>              uint64_t s, e;
>  
> +            if ( boot_e820.map[i].type != E820_RAM )
> +                continue;
>              s = (boot_e820.map[i].addr + mask) & ~mask;
>              e = (boot_e820.map[i].addr + boot_e820.map[i].size) & ~mask;
>              if ( PFN_DOWN(e) <= limit )
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2013-11-04 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 10:25 [PATCH] x86: make sure memory block is RAM before passing to the allocator Jan Beulich
2013-11-04 13:25 ` Keir Fraser [this message]

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=CE9D50D7.3CC9D%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xenproject.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).