Re: [PATCH] memory hotadd fixes [4/5] avoid check in acpi

[Yasunori Goto]

> On Thu, 03 Aug 2006 20:23:46 -0700
> keith mannthey <kmannth@xxxxxxxxxx> wrote:
> 
> > On Fri, 2006-08-04 at 12:13 +0900, KAMEZAWA Hiroyuki wrote:
> > > On Thu, 03 Aug 2006 20:00:08 -0700
> > > keith mannthey <kmannth@xxxxxxxxxx> wrote:
> > > 
> > > 
> > > > > >   What protecting is there for calling add_memory on an already present
> > > > > > memory range?  
> > > > > > 
> > > > > For example, considering ia64, which has 1Gbytes section...
> > > > 
> > > > Maybe 1gb sections is too large?  
> > > > 
> > > ia64 machines sometimes to have crazy big memory...so 1gb section is requested.
> > > Configurable section_size for small machines was rejected in old days.
> > 
> > My HW supports about 512gb...... 
> > 
> 
> > What if you add a partial section.  Then online in sysfs and add another
> > section?  messy....
> Once a section is onlined, it cannot be re-onlined. My patch just helps memory holes
> in "a" memory hot add event.
> Our firmware team tells us they may create small memory holes in contiguous memory...

I would like to mention about it more.

We asked not to make memory hole to firmware team before.
But, conclusion became NO. 
Because this hole is made for memory partial broken case. 
Current ACPI doesn't have any spec to tell which memory area is
broken. So, _CRS must return address range of only sane memory area.
In addition, partial broken area should be smaller as much as possible.
This is why he mention about memory hole.

BTW, I prefer that we should fix only bug at this time for 2.6.18.
But, I really confusing that current patches are for only bug fix or
including for small memory hole case.
IIRC, small memory hole need more works. So, it should be 2.6.19
or later. Right?
Kame-san, could you divide between just fix patch and considering
small hole case? Or all of patches are for only bug fix?

Bye.

-- 
Yasunori Goto 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/