Re: CONFIG_ACPI_HOTPLUG_MEMORY=m with x86_64 devel tree II

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

 



On Thu, Mar 30, 2006 at 10:54:59PM +0900, KAMEZAWA Hiroyuki wrote:
> On 30 Mar 2006 15:41:33 +0200
> Andi Kleen <ak@xxxxxx> wrote:
> 
> > 
> > Hi,
> > 
> > I started to implement your suggestion now.
> > 
> > But one problem I noticed and I don't see how the current sparsemem code
> > handles correctly is that it makes no attempt to handle hotadd
> > areas that cross zone boundaries. Is there code somewhere that rejects
> > them?
> > 
> 
> add_memory() selects a zone which pages are added, before adding memory regardless
> of its address. Now this is hard-coded.
> 
> ia64 adds memory to NORMAL.
> i386 adds memory to HIGHMEM.
> x86_64 adds memory to NORMAL.

Yes but what stops ACPI from trying to add memory that crosses 
a zone? (e.g. from 2GB to 6GB) 

> 
> if x86_64 people wants to add memory to DMA32 or some other zone, please add code.

I added a check for it in the reserve hotadd code now.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux