Re: memory-hotplug : suppres "Trying to free nonexistent resource " warning

On Thu, 4 Oct 2012 14:31:09 +0900 Yasuaki Ishimatsu wrote: > When our x86 box calls __remove_pages(), release_mem_region() shows > many warnings. And x86 box cannot unregister iomem_resource. > > "Trying to free nonexistent resource " > > release_mem_region() has been changed as called in each

[PATCH] powerpc/mpc5200: move lpbfifo node and fix its interrupt property

The LPB FIFO interrupt is a peripheral interrupt, thus its L1 cell has to be 2 instead of 3. Fix it and while at it, move the lpbfifo node to the common dtsi file. Reported-by: Stefan Roese Signed-off-by: Anatolij Gustschin --- arch/powerpc/boot/dts/mpc5200b.dtsi |6 ++ arch/powerpc/boo

Re: [PATCH 2/10] memory-hotplug : remove /sys/firmware/memmap/X sysfs

On Thu, Oct 4, 2012 at 10:26 PM, Yasuaki Ishimatsu wrote: > When (hot)adding memory into system, /sys/firmware/memmap/X/{end, start, type} > sysfs files are created. But there is no code to remove these files. The patch > implements the function to remove them. > > Note : The code does not free fi

Re: [PATCH 1/10] memory-hotplug : check whether memory is offline or not when removing memory

On Thu, Oct 4, 2012 at 10:25 PM, Yasuaki Ishimatsu wrote: > When calling remove_memory(), the memory should be offline. If the function > is used to online memory, kernel panic may occur. > > So the patch checks whether memory is offline or not. You don't explain WHY we need the check. > CC: Da

Re: [PATCH 0/10] memory-hotplug: hot-remove physical memory

> Known problems: > 1. memory can't be offlined when CONFIG_MEMCG is selected. >For example: there is a memory device on node 1. The address range >is [1G, 1.5G). You will find 4 new directories memory8, memory9, memory10, >and memory11 under the directory /sys/devices/system/memory/. >

Re: memory-hotplug : suppres "Trying to free nonexistent resource " warning

CC to Dave Hanse. Hello Dave, I think following patch works both x86 and ppc. but I'm not ppc expert. So I'm glad if you double check it. thank you. > When our x86 box calls __remove_pages(), release_mem_region() shows > many warnings. And x86 box cannot unregister iomem_resource. > > "Tryin

Re: [PATCHv2] PPC: Enable the Watchdog vector for 405

The watchdog and FIT code has been #if 0'd for ever, if the CPU takes an exception to either of those vectors it will jump into the middle of the PIT or Data TLB code and surely crash. At least some (all?) 405 cores have both the WDT and FIT vectors defined, so lets have proper entry points for th

Re: [Cbe-oss-dev] [PATCH 4/5] Rename the drivers/of prom_* functions to of_*

On Tue, 2012-10-02 at 21:58 -0500, Nathan Fontenot wrote: > Rename the prom_*_property routines of the generic OF code to of_*_property. > This brings them in line with the naming used by the rest of the OF code. > > Signed-off-by: Nathan Fontenot > --- > arch/powerpc/platforms/ps3/os-area.c

Re: PCI device not working

On Oct 5, 2012, at 3:54 AM, Davide Viti wrote: > (just realized I did not send this to the mailing list: sorry for the noise) > > Hi Kumar, > > 2012/10/4 Kumar Gala : >> >> On Oct 4, 2012, at 7:24 AM, Davide Viti wrote: >> >>> Hi, >>> it turns out that if define CONFIG_PCI_NOSCAN in u-boot (a

Changing TASK_UNMAPPED_BASE to a low address

Hi, The current virtual address space of a 32-bit userspace process looks like this on powerpc: # cat /proc/28922/maps 0010-00102000 r-xp 00:00 0 [vdso] 0fe7-0ffd8000 r-xp 00:01 754/lib/libc-2.10.1.so 0ffd8000-0ffe8000 ---p 00168000 00:01 754/lib/

Fwd: PCI device not working

(just realized I did not send this to the mailing list: sorry for the noise) Hi Kumar, 2012/10/4 Kumar Gala : > > On Oct 4, 2012, at 7:24 AM, Davide Viti wrote: > >> Hi, >> it turns out that if define CONFIG_PCI_NOSCAN in u-boot (as per [1]), the >> device behind the second controller is detected