[Patch v4 01/12] memory-hotplug: try to offline the memory twice to avoid dependence

2012-11-27 Thread Wen Congyang
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/. If CONFIG_MEMCG is selected, we will

[Patch v4 07/12] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap

2012-11-27 Thread Wen Congyang
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com For removing memmap region of sparse-vmemmap which is allocated bootmem, memmap region of sparse-vmemmap needs to be registered by get_page_bootmem(). So the patch searches pages of virtual mapping and registers the pages by

[Patch v4 02/12] memory-hotplug: check whether all memory blocks are offlined or not when removing memory

2012-11-27 Thread Wen Congyang
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com We remove the memory like this: 1. lock memory hotplug 2. offline a memory block 3. unlock memory hotplug 4. repeat 1-3 to offline all memory blocks 5. lock memory hotplug 6. remove memory(TODO) 7. unlock memory hotplug All memory blocks

[Patch v4 08/12] memory-hotplug: remove memmap of sparse-vmemmap

2012-11-27 Thread Wen Congyang
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com All pages of virtual mapping in removed memory cannot be freed, since some pages used as PGD/PUD includes not only removed memory but also other memory. So the patch checks whether page can be freed or not. How to check whether page can be

[Patch v4 06/12] memory-hotplug: unregister memory section on SPARSEMEM_VMEMMAP

2012-11-27 Thread Wen Congyang
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com Currently __remove_section for SPARSEMEM_VMEMMAP does nothing. But even if we use SPARSEMEM_VMEMMAP, we can unregister the memory_section. So the patch add unregister_memory_section() into __remove_section(). CC: David Rientjes

[Patch v4 00/12] memory-hotplug: hot-remove physical memory

2012-11-27 Thread Wen Congyang
The patch-set was divided from following thread's patch-set. https://lkml.org/lkml/2012/9/5/201 The last version of this patchset: https://lkml.org/lkml/2012/11/1/93 If you want to know the reason, please read following thread. https://lkml.org/lkml/2012/10/2/83 The patch-set has only

[Patch v4 04/12] memory-hotplug: remove /sys/firmware/memmap/X sysfs

2012-11-27 Thread Wen Congyang
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com 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

[Patch v4 03/12] memory-hotplug: remove redundant codes

2012-11-27 Thread Wen Congyang
offlining memory blocks and checking whether memory blocks are offlined are very similar. This patch introduces a new function to remove redundant codes. CC: David Rientjes rient...@google.com CC: Jiang Liu liu...@gmail.com CC: Len Brown len.br...@intel.com CC: Christoph Lameter c...@linux.com

[Patch v4 09/12] memory-hotplug: remove page table of x86_64 architecture

2012-11-27 Thread Wen Congyang
For hot removing memory, we sholud remove page table about the memory. So the patch searches a page table about the removed memory, and clear page table. CC: David Rientjes rient...@google.com CC: Jiang Liu liu...@gmail.com CC: Len Brown len.br...@intel.com CC: Christoph Lameter c...@linux.com

[Patch v4 10/12] memory-hotplug: memory_hotplug: clear zone when removing the memory

2012-11-27 Thread Wen Congyang
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com When a memory is added, we update zone's and pgdat's start_pfn and spanned_pages in the function __add_zone(). So we should revert them when the memory is removed. The patch adds a new function __remove_zone() to do this. CC: David Rientjes

[Patch v4 11/12] memory-hotplug: remove sysfs file of node

2012-11-27 Thread Wen Congyang
This patch introduces a new function try_offline_node() to remove sysfs file of node when all memory sections of this node are removed. If some memory sections of this node are not removed, this function does nothing. CC: David Rientjes rient...@google.com CC: Jiang Liu liu...@gmail.com CC: Len

[Patch v4 12/12] memory-hotplug: free node_data when a node is offlined

2012-11-27 Thread Wen Congyang
We call hotadd_new_pgdat() to allocate memory to store node_data. So we should free it when removing a node. CC: David Rientjes rient...@google.com CC: Jiang Liu liu...@gmail.com CC: Len Brown len.br...@intel.com CC: Benjamin Herrenschmidt b...@kernel.crashing.org CC: Paul Mackerras

Re: [Patch v4 00/12] memory-hotplug: hot-remove physical memory

2012-11-27 Thread Andrew Morton
On Tue, 27 Nov 2012 18:00:10 +0800 Wen Congyang we...@cn.fujitsu.com wrote: The patch-set was divided from following thread's patch-set. https://lkml.org/lkml/2012/9/5/201 The last version of this patchset: https://lkml.org/lkml/2012/11/1/93 As we're now at -rc7 I'd prefer to take

Re: [Patch v4 00/12] memory-hotplug: hot-remove physical memory

2012-11-27 Thread Rafael J. Wysocki
On Tuesday, November 27, 2012 11:27:41 AM Andrew Morton wrote: On Tue, 27 Nov 2012 18:00:10 +0800 Wen Congyang we...@cn.fujitsu.com wrote: The patch-set was divided from following thread's patch-set. https://lkml.org/lkml/2012/9/5/201 The last version of this patchset:

[PATCH 05/16] i2c: i2c-cpm: remove __dev* attributes

2012-11-27 Thread Bill Pemberton
CONFIG_HOTPLUG is going away as an option. As result the __dev* markings will be going away. Remove use of __devinit, __devexit_p, __devinitdata, __devinitconst, and __devexit. Signed-off-by: Bill Pemberton wf...@virginia.edu Cc: Jochen Friedrich joc...@scram.de Cc:

Re: [PATCH 192/493] scsi: remove use of __devinit

2012-11-27 Thread vinayak holikatti
drivers/scsi/ufs/ufshcd.c | 2 +- Acked-by: Vinayak Holikatti vinholika...@gmail.com only for drivers/scsi/ufs/ufshcd.c diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c index 4a370f8..a79ff87 100644 --- a/drivers/scsi/ufs/ufshcd.c +++

Re: problem with mpc8536 and kernel 2.6.32 and interrupts

2012-11-27 Thread Scott Wood
On 11/22/2012 06:12:03 AM, Koen Swinters wrote: We have a module from broadcom loaded that makes use of interrupts via PCI and interrupt driver FSL-MSI . When we disable this interrupt the coredumps dissapear. I`ve tried the following patch: 78e2e68a2b79f394b7cd61e07987a8a89af907f7. But is

Re: [Patch v4 00/12] memory-hotplug: hot-remove physical memory

2012-11-27 Thread Yasuaki Ishimatsu
Hi Andrew, 2012/11/28 4:27, Andrew Morton wrote: On Tue, 27 Nov 2012 18:00:10 +0800 Wen Congyang we...@cn.fujitsu.com wrote: The patch-set was divided from following thread's patch-set. https://lkml.org/lkml/2012/9/5/201 The last version of this patchset:

Re: [PATCH] powerpc/pci-hotplug: fix the rescanned pci device's dma_set_mask issue

2012-11-27 Thread Chen Yuanquan-B41889
On 11/25/2012 08:41 PM, Kumar Gala wrote: On Nov 22, 2012, at 10:29 PM, Yuanquan Chen wrote: On powerpc arch, dma_ops of rescanned pci device after system's booting up won't be initialized by system, so it will fail to execute the dma_set_mask in the device's driver. Initialize it to solve

linux-next: build failure after merge of the powerpc tree

2012-11-27 Thread Stephen Rothwell
Hi all, After merging the powerpc tree, next-20121115's build (powerpc allmodconfig) failed like this: ERROR: .of_reconfig_notifier_register [drivers/crypto/nx/nx-compress.ko] undefined! ERROR: .of_reconfig_notifier_unregister [drivers/crypto/nx/nx-compress.ko] undefined! Caused by commit

3.7-rc7: BUG: MAX_STACK_TRACE_ENTRIES too low!

2012-11-27 Thread Christian Kujau
Hi, the same thing[0] happened again in 3.7-rc7, after ~20h uptime: [40007.339487] [sched_delayed] sched: RT throttling activated [69731.388717] BUG: MAX_STACK_TRACE_ENTRIES too low! [69731.390371] turning off the locking correctness validator. [69731.391942] Call Trace: [69731.393525]

Re: 3.7-rc7: BUG: MAX_STACK_TRACE_ENTRIES too low!

2012-11-27 Thread Christian Kujau
On Tue, 27 Nov 2012 at 19:06, Christian Kujau wrote: the same thing[0] happened again in 3.7-rc7, after ~20h uptime: I found the following on patchwork, but this seems to deal with powerpc64 only, while this PowerBook G4 of mine is powerpc32: http://patchwork.ozlabs.org/patch/193414/ It

Re: linux-next: build failure after merge of the powerpc tree

2012-11-27 Thread Benjamin Herrenschmidt
On Wed, 2012-11-28 at 14:03 +1100, Stephen Rothwell wrote: Hi all, After merging the powerpc tree, next-20121115's build (powerpc allmodconfig) failed like this: ERROR: .of_reconfig_notifier_register [drivers/crypto/nx/nx-compress.ko] undefined! ERROR: .of_reconfig_notifier_unregister

[PATCH] vfio powerpc: enabled on powernv platform

2012-11-27 Thread Alexey Kardashevskiy
This patch initializes IOMMU groups based on the IOMMU configuration discovered during the PCI scan on POWERNV (POWER non virtualized) platform. The IOMMU groups are to be used later by VFIO driver (PCI pass through). It also implements an API for mapping/unmapping pages for guest PCI drivers and

[PATCH] vfio powerpc: implemented IOMMU driver for VFIO

2012-11-27 Thread Alexey Kardashevskiy
VFIO implements platform independent stuff such as a PCI driver, BAR access (via read/write on a file descriptor or direct mapping when possible) and IRQ signaling. The platform dependent part includes IOMMU initialization and handling. This patch implements an IOMMU driver for VFIO which does