[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86: make sure memory block is RAM before passing to the allocator


  • To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Mon, 04 Nov 2013 13:25:43 +0000
  • Delivery-date: Mon, 04 Nov 2013 13:26:28 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac7ZYVyp9WbXhQKj4UeoUhDcwdZG1Q==
  • Thread-topic: [Xen-devel] [PATCH] x86: make sure memory block is RAM before passing to the allocator

On 04/11/2013 10:25, "Jan Beulich" <JBeulich@xxxxxxxx> 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@xxxxxxxx>

Acked-by: Keir Fraser <keir@xxxxxxx>

> --- 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@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.