On Fri, 2008-10-24 at 16:55 -0600, Chris Friesen wrote:
> Rafael J. Wysocki wrote:
> > On Friday, 17 of October 2008, Kumar Gala wrote:
>
> >> I've got a patch that seems to address this for me building w/
> >> CONFIG_RELOCATABLE on ppc32/85xx.
> >
> > Has that been fixed in 2.6.27 and/or curren
On Fri, 2008-10-17 at 10:47 -0700, Badari Pulavarty wrote:
> Hi,
>
> I get this following compile error on my ppc box.
>
> Let me know if its a known issue. Otherwise, I can figure out
> whats happening.
>
> Thanks,
> Badari
This is due to recent changes to move phys
Hi,
I get this following compile error on my ppc box.
Let me know if its a known issue. Otherwise, I can figure out
whats happening.
Thanks,
Badari
CC arch/powerpc/mm/slb.o
In file included from
/usr/src/linux-2.6.27/arch/powerpc/include/asm/mmu-hash64.h:16,
from /usr/s
On Mon, 2008-10-06 at 11:05 +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2008-10-03 at 10:40 -0700, Badari Pulavarty wrote:
> > Hi,
> >
> > I am not able to boot my Power5 box with 2.6.27-rc8 (defconfig).
> > However, I am able to boot with my own custom config.
>
Hi,
I am not able to boot my Power5 box with 2.6.27-rc8 (defconfig).
However, I am able to boot with my own custom config.
Known issue ?
Thanks,
Badari
boot: 2627rc8
Please wait, loading kernel...
Elf32 kernel loaded...
zImage starting: loaded at 0x040001fc (sp: 0x019ffa80)
Allocating 0xa
unsigned long nr_pages, void *arg,
> + int (*func)(unsigned long, unsigned long, void *));
> +
> extern int add_memory(int nid, u64 start, u64 size);
> extern int arch_add_memory(int nid, u64 start, u64 size);
> extern int remove_memory(u64 start, u64 size);
Sorry. I couldn't get back earlier.
Acked-by: Badari Pulavarty <[EMAIL PROTECTED]>
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Tue, 2008-06-03 at 15:49 -0500, Nathan Lynch wrote:
> Hannes Hering wrote:
> >
> > On Wednesday 28 May 2008 18:44:05 Nathan Lynch wrote:
> > >
> > > Hannes Hering wrote:
> > > > The new ehea memory hot plug implementation depends on MEMORY_HOTPLUG.
> > > >
> > > > Signed-off-by: Hannes Herin
On Mon, 2008-05-12 at 17:17 -0700, Geoff Levand wrote:
> Hi,
>
> I've had some trouble with this change.
>
> Badari Pulavarty wrote:
> > Provide walk_memory_resource() for ppc64. PPC maintains
> > logic memory region mapping in lmb.memory structures. Walk
>
On Thu, 2008-05-01 at 15:13 +1000, Tony Breeds wrote:
> On Tue, Apr 29, 2008 at 11:12:41PM -0700, David Miller wrote:
> >
> > This commit causes bootup failures on sparc64:
> >
> > commit 86f6dae1377523689bd8468fed2f2dd180fc0560
> > Author: Yasunori Goto <[EMAIL PROTECTED]>
> > Date: Mon Apr 2
Hi Greg,
Ran into this sysfs oops while booting 2.6.25-git12.
ipr issue ?
Thanks,
Badari
ipr: IBM Power RAID SCSI Device Driver version: 2.4.1 (April 24, 2007)
ipr :d0:01.0: Found IOA with IRQ: 119
ipr :d0:01.0: Starting IOA initialization sequence.
ipr :d0:01.0: Adapter firmware ver
usemap);
> }
>
> - free_bootmem(__pa(section_map), size);
> + free_bootmem(__pa(usemap_map), size);
> }
>
> #ifdef CONFIG_MEMORY_HOTPLUG
Tested and boots my machine fine.
Acked-by: Badari Pulavarty <[EMAIL PROTECTED]>
Thanks,
Badari
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
On Wed, 2008-04-02 at 18:17 +1100, Michael Ellerman wrote:
> On Wed, 2008-04-02 at 12:38 +0530, Kamalesh Babulal wrote:
> > Andrew Morton wrote:
> > > On Wed, 02 Apr 2008 11:55:36 +0530 Kamalesh Babulal <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > >> Hi Andrew,
> > >>
> > >> The 2.6.25-rc8-mm1 kern
On Wed, 2008-04-02 at 22:39 +0530, Kamalesh Babulal wrote:
> Michael Ellerman wrote:
> > On Wed, 2008-04-02 at 12:38 +0530, Kamalesh Babulal wrote:
> >> Andrew Morton wrote:
> >>> On Wed, 02 Apr 2008 11:55:36 +0530 Kamalesh Babulal <[EMAIL PROTECTED]>
> >>> wrote:
> >>>
> Hi Andrew,
>
>
Kumar Gala wrote:
On Mar 27, 2008, at 7:39 PM, Badari Pulavarty wrote:
ppc kernel maintains information about logical memory blocks in
lmb.memory structure at the boot time. Its not updated for
hotplug memory add/remove. hotplug memory notifier for memory
add/remove now updates lmb.memory
Provide walk_memory_resource() for ppc64. PPC maintains
logic memory region mapping in lmb.memory structures. Walk
through these structures and do the callbacks for the
contiguous chunks.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/mm/mem.c
holes.
NOTE: No special locking is needed for lmb_add() and lmb_remove().
Calls to these are serialized by caller. (pSeries_reconfig_chain).
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 43 +++
include/linux
.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
Reviewed-by: Michael Ellerman <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/pseries/Makefile |1
arch/powerpc/platforms/pseries/hotplug-memory.c | 98
2 files changed, 99 insertions(+)
Index:
If the sub-arch doesn't support hpte_removebolted(), gracefully
return failure rather than success.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/mm/hash_utils_64.c | 14 +-
include/asm-powerpc/sparsemem.h |2 +-
2 files changed, 10 inser
Generic helper function to remove section mappings and sysfs entries
for the section of the memory we are removing. offline_pages() correctly
adjusted zone and marked the pages reserved.
TODO: Yasunori Goto is working on patches to freeup allocations from bootmem.
Signed-off-by: Badari
Hi Andrew & Paul,
Here are the updates for hotplug memory remove. Most changes are
PPC specific, but I would like these to be included in next -mm
for easy testing and review, before including in Paul's tree.
eHEA driver folks are verifying if the exported interface
walk_memory_resource() is good
On Sat, 2008-03-22 at 00:25 +0900, Yasunori Goto wrote:
> Badari-san.
>
> > Index: linux-2.6.25-rc2/mm/memory_hotplug.c
> > ===
> > --- linux-2.6.25-rc2.orig/mm/memory_hotplug.c 2008-02-27
> > 12:58:17.0 -0800
> > +++ l
On Wed, 2008-03-12 at 18:25 +0530, Kamalesh Babulal wrote:
> Hi Andrew,
>
> The 2.6.25-rc5-mm1 kernel panics while bootup on powerpc
>
> returning from prom_init
> Unable to handle kernel paging request for data at address 0x
> Faulting instruction address: 0xc000d5dc
> cpu 0x0: V
Yasunori Goto wrote:
> Hi Badari-san.
>
>
>> On Thu, 2008-03-06 at 12:54 -0800, Dave Hansen wrote:
>>
>>> On Thu, 2008-03-06 at 10:55 -0800, Badari Pulavarty wrote:
>>>
>>>> + if (memmap)
>>>> +
Yasunori Goto wrote:
> Hi Badari-san.
>
>
>> On Thu, 2008-03-06 at 12:54 -0800, Dave Hansen wrote:
>>
>>> On Thu, 2008-03-06 at 10:55 -0800, Badari Pulavarty wrote:
>>>
>>>> + if (memmap)
>>>> +
semap allocation could come from different places -
kmalloc, vmalloc, alloc_pages or bootmem. There is no easy way
to find and free up bootmem allocations.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
include/linux/memory_hotplug.h |6 +++-
mm/memory_hotplug.c
On Thu, 2008-03-06 at 12:54 -0800, Dave Hansen wrote:
> On Thu, 2008-03-06 at 10:55 -0800, Badari Pulavarty wrote:
> > + if (memmap)
> > + __kfree_section_memmap(memmap, PAGES_PER_SECTION);
> > +
On Thu, 2008-03-06 at 11:08 -0800, Randy Dunlap wrote:
> On Thu, 06 Mar 2008 10:55:34 -0800 Badari Pulavarty wrote:
>
> > Generic helper function to remove section mappings and sysfs entries
> > for the section of the memory we are removing. offline_pages() correctly
>
Provide walk_memory_resource() for ppc64. PPC maintains
logic memory region mapping in lmb.memory structures. Walk
through these structures and do the callbacks for the
contiguous chunks.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/mm/mem.c
holes.
NOTE: Calls to lmb_add() and lmb_remove() needs to be serialized by
the caller. In this case blocking_notifier_chain(pSeries_reconfig_chain)
does that.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/pseries/hotplug-memory.c | 43 +++
i
.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
Reviewed-by: Michael Ellerman <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/pseries/Makefile |1
arch/powerpc/platforms/pseries/hotplug-memory.c | 98
2 files changed, 99 insertions(+)
Index:
If the sub-arch doesn't support hpte_removebolted(), gracefully
return failure rather than success.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/mm/hash_utils_64.c | 14 +-
include/asm-powerpc/sparsemem.h |2 +-
2 files changed, 10 inser
bootmem. There is no easy way
to find and free up bootmem allocations.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
include/linux/memory_hotplug.h |4 +++
mm/memory_hotplug.c| 44 +
mm/sparse.c
Hi Andrew & Paul,
Here are the updates for hotplug memory remove. Most changes are
PPC specific, but I would like these to be included in next -mm
for easy testing and review, before including in Paul's tree.
eHEA driver folks are verifying if the exported interface
walk_memory_resource() is goo
On Wed, 2008-03-05 at 13:54 -0800, Andrew Morton wrote:
> On Wed, 05 Mar 2008 13:34:14 -0800
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2008-03-04 at 01:19 -0800, Andrew Morton wrote:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches
On Tue, 2008-03-04 at 01:19 -0800, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc3/2.6.25-rc3-mm1/
>
Hi Andrew,
Not able to boot 2.6.25-rc3-mm1 my ppc64 box.
2.6.25-rc2-mm1 and 2.6.25-rc3 boots fine.
I applied slab.c fix also.
Any other known iss
David Miller wrote:
> From: Badari Pulavarty <[EMAIL PROTECTED]>
> Date: Fri, 29 Feb 2008 17:12:44 -0800
>
>
>> Here is what I cooked up and it seems to work fine.
>> It may be easier to review the code (against my earlier patches).
>>
>
> BTW,
Stephen Rothwell wrote:
> On Fri, 29 Feb 2008 09:47:16 -0800 Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
>> Here is the latest for review. (just to make sure I didn't miss
>> anything).
>>
>
> Sorry I didn't review the previous on
On Fri, 2008-02-29 at 09:56 -0800, Badari Pulavarty wrote:
> Hi,
>
> I am wondering if you could give me your opinion on how to proceed
> (before I code too much).
>
> eHEA driver writers wants to know what the memory layout is - where the
> holes are and where the reserve
Hi,
I am wondering if you could give me your opinion on how to proceed
(before I code too much).
eHEA driver writers wants to know what the memory layout is - where the
holes are and where the reserved memory is. They can get this from
parsing through the device-tree every time, but it would be t
On Fri, 2008-02-29 at 12:03 +1100, Michael Ellerman wrote:
> On Thu, 2008-02-28 at 18:39 -0600, Nathan Lynch wrote:
> > Michael Ellerman wrote:
> > > On Thu, 2008-02-28 at 08:46 -0800, Badari Pulavarty wrote:
> > > > Hotplug memory notifier for ppc64. This gets
Nathan Lynch wrote:
> Badari Pulavarty wrote:
>
>> Hi Paul,
>>
>> Here are the hotplug memory remove updates for 2.6.25-rc2-mm1.
>>
>
> How have these been tested? Have you initiated a memory remove
> operation from the HMC? That's the only
On Thu, 2008-02-28 at 11:20 -0600, Nathan Lynch wrote:
> Badari Pulavarty wrote:
>
> > +static struct notifier_block pseries_smp_nb = {
>
> Rename this to pseries_mem_nb?
Sure.
>
> > + .notifier_call = pseries_memory_notifier,
> > +};
> > +
> > +
.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/pseries/Makefile |1
arch/powerpc/platforms/pseries/hotplug-memory.c | 98
2 files changed, 99 insertions(+)
Index: linux-2.6.25-rc2/arch/powerpc/platforms/pseries/hotplug-me
bootmem. There is no easy way
to find and free up properly. Especially for bootmem, we need to
know which node the allocation came from.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
include/linux/memory_hotplug.h |4 +++
mm/memory_hotplug.c
: Badari Pulavarty <[EMAIL PROTECTED]>
Acked-by: Paul Mackerras <[EMAIL PROTECTED]>
---
arch/powerpc/mm/hash_utils_64.c | 26 ++
arch/powerpc/platforms/pseries/lpar.c | 15 +++
include/asm-powerpc/machdep.h |2 ++
include
Hi Paul,
Here are the hotplug memory remove updates for 2.6.25-rc2-mm1.
[PATCH 1/3] ppc64-specific remove htab bolted mapping support
[PATCH 2/3] generic __remove_pages() support
[PATCH 3/3] ppc64-specific memory notifier support
As you can see PATCH 1,3 are ppc64-specific. PATCH 1 was already
r
On Thu, 2008-02-14 at 09:12 -0800, Dave Hansen wrote:
..
> > > > - Use currently other not exported functions in kernel/resource.c, like
> > > > walk_memory_resource (where we would still need the maximum
> > > possible number
> > > > of pages NR_MEM_SECTIONS)
> > >
> > > It isn't the act of ex
ed memory should be invalidated at least.
I think its a generic issue. Nothing specific for ppc64. Isn't it ?
Thanks,
Badari
>
> But anyway, this is a great first step for physical memory remove.
>
> Thanks.
>
>
> > On Mon, 2008-01-28 at 16:31 -0800, Badari Pulavart
On Mon, 2008-01-28 at 16:31 -0800, Badari Pulavarty wrote:
> 2) Can you replace the following patch with this ?
>
> add-remove_memory-for-ppc64-2.patch
>
> I found that, I do need arch-specific hooks to get the memory remove
> working on ppc64 LPAR. Earlier, I tried to
orking on ppc64 LPAR. Earlier, I tried to make remove_memory() arch
neutral, but we do need arch specific hooks.
Thanks,
Badari
Supply ppc64 remove_memory() function. Arch specific is still
being reviewed by Paul Mackerras.
From: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/po
On Sat, 2008-01-26 at 12:24 +1100, Paul Mackerras wrote:
> Badari Pulavarty writes:
>
> > Here is the code I cooked up, it seems to be working fine.
> > But I have concerns where I need your help.
> >
> > In order to invalidate htab entries, we need to find the &
ned-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/mm/hash_utils_64.c | 32
include/asm-powerpc/sparsemem.h |1 +
2 files changed, 33 insertions(+)
Index: linux-2.6.24-rc8/arch/powerpc/mm
On Fri, 2007-11-02 at 10:32 +, Johannes Berg wrote:
> > This patch provides a way for an architecture to provide its
> > own walk_memory_resource()
>
> It seems that the patch description "walk_memory_remove()" is wrong?
>
Yep. Patch title is wrong.
Thanks,
Badari
_
On Wed, 2007-10-31 at 13:45 -0700, Dave Hansen wrote:
> On Wed, 2007-10-31 at 08:49 -0800, Badari Pulavarty wrote:
> > +#ifdef CONFIG_MEMORY_HOTREMOVE
> > +int remove_memory(u64 start, u64 size)
> > +{
> > + unsigned long start_pfn, end_pfn;
> > + unsigned lon
On Wed, 2007-10-31 at 13:45 -0700, Dave Hansen wrote:
> On Wed, 2007-10-31 at 08:49 -0800, Badari Pulavarty wrote:
> > +#ifdef CONFIG_MEMORY_HOTREMOVE
> > +int remove_memory(u64 start, u64 size)
> > +{
> > + unsigned long start_pfn, end_pfn;
> > + unsigned lon
On Thu, 2007-11-01 at 01:26 -0500, Kumar Gala wrote:
> On Oct 31, 2007, at 11:49 AM, Badari Pulavarty wrote:
>
> > Supply arch specific remove_memory() for PPC64. There is nothing
> > ppc specific code here and its exactly same as ia64 version.
> > For now, lets keep it
Supply arch specific remove_memory() for PPC64. There is nothing
ppc specific code here and its exactly same as ia64 version.
For now, lets keep it arch specific - so each arch can add
its own special things if needed.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powe
patch provides a way for an architecture to provide its
own walk_memory_resource() function. On PPC64, the memory
region is small (16MB), contiguous and non-overlapping.
So extra checking, against device-tree is not needed.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
Acked-by: KAMEZA
Enable hotplug memory remove for ppc64.
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/Kconfig |3 +++
1 file changed, 3 insertions(+)
Index: linux-2.6.23/arch/powerpc/Kconfig
===
--- linux-2.6.2
Hi Paul/Andrew,
Here are few minor fixes needed to get hotplug memory remove working
on ppc64. Could you please consider them for -mm ?
[PATCH 1/3] Add remove_memory() for ppc64
[PATCH 2/3] Enable hotplug memory remove for ppc64
[PATCH 3/3] Add arch-specific walk_memory_re
On Wed, 2007-10-31 at 14:28 +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 30 Oct 2007 11:19:11 -0800
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
> > Hi KAME,
> >
> > As I mentioned while ago, ppc64 does not export information about
> > "system RAM&qu
On Wed, 2007-10-31 at 14:34 +0900, KAMEZAWA Hiroyuki wrote:
> On Wed, 31 Oct 2007 14:28:46 +0900
> KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
>
> > ioresource was good structure for remembering "which memory is conventional
> > memory" and i386/x86_64/ia64 registered conventional memory as "Syst
Hi KAME,
As I mentioned while ago, ppc64 does not export information about
"system RAM" in /proc/iomem. Looking at the code and usage
scenerios I am not sure what its really serving. Could you
explain what its purpose & how the range can be invalid ?
At least on ppc64, all the memory ranges we g
forms/powermac/time.c:95: warning: `from_rtc_time' defined but
not used
Signed-off-by: Badari Pulavarty <[EMAIL PROTECTED]>
---
arch/powerpc/platforms/powermac/time.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.23/arch/powerpc/platforms
On Thu, 2007-10-04 at 01:25 +0900, KAMEZAWA Hiroyuki wrote:
> On Wed, 03 Oct 2007 08:35:35 -0700
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
>
> > On Wed, 2007-10-03 at 10:19 +0900, KAMEZAWA Hiroyuki wrote:
> > CONFIG_ARCH_HAS_VALID_MEMORY_RANGE. Then define o
On Wed, 2007-10-03 at 10:19 +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 02 Oct 2007 16:10:53 -0700
> Badari Pulavarty <[EMAIL PROTECTED]> wrote:
> > > > Otherwise, we need to add arch-specific hooks in hotplug-remove
> > > > code to be able to do this.
&g
On Wed, 2007-10-03 at 08:56 +1000, Paul Mackerras wrote:
> Badari Pulavarty writes:
>
> > I am trying to get hotplug memory remove working on ppc64.
> > In order to verify a given memory region, if its valid or not -
> > current hotplug-memory patches used /proc/iomem
On Tue, 2007-10-02 at 13:11 -0700, Geoff Levand wrote:
> Hi Badari,
>
> Badari Pulavarty wrote:
> > Hi Paul & Ben,
> >
> > I am trying to get hotplug memory remove working on ppc64.
> > In order to verify a given memory region, if its valid or not -
> >
Hi Paul & Ben,
I am trying to get hotplug memory remove working on ppc64.
In order to verify a given memory region, if its valid or not -
current hotplug-memory patches used /proc/iomem. On IA64 and
x86-64 /proc/iomem shows all memory regions.
I am wondering, if its acceptable to do the same on
69 matches
Mail list logo
