From: Wen Congyang we...@cn.fujitsu.com
This patch series aims to support physical memory hot-remove.
The patches can free/remove following things:
- acpi_memory_info : [RFC PATCH 4/19]
- /sys/firmware/memmap/X/{end, start, type} : [RFC PATCH 8/19]
-
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
remove_memory() only try to offline pages. It is called in two cases:
1. hot remove a memory device
2. echo offline /sys/devices/system/memory/memoryXX/state
In the 1st case, we should also change memory block's state, and notify
the
From: Wen Congyang we...@cn.fujitsu.com
The function acpi_bus_remove() can remove a acpi device from acpi device.
When a acpi device is removed, we need to call this function to remove
the acpi device from acpi bus. So export this function.
CC: David Rientjes rient...@google.com
CC: Jiang Liu
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
We should offline and remove memory when removing the memory device.
The memory device can be removed by 2 ways:
1. send eject request by SCI
2. echo 1 /sys/bus/pci/devices/PNP0C80:XX/eject
In the 1st case, acpi_memory_disable_device() will
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
If system supports memory hot-remove, online_pages() may online removed pages.
So online_pages() need to check whether onlining pages are present or not.
CC: David Rientjes rient...@google.com
CC: Jiang Liu liu...@gmail.com
CC: Len Brown
From: Wen Congyang we...@cn.fujitsu.com
The memory device has been ejected and powoffed, so we can call
acpi_bus_remove() to remove the memory device from acpi bus.
CC: David Rientjes rient...@google.com
CC: Jiang Liu liu...@gmail.com
CC: Len Brown len.br...@intel.com
CC: Benjamin Herrenschmidt
From: Wen Congyang we...@cn.fujitsu.com
The function offline_memory() will be called when hot removing a
memory device. The memory device may contain more than one memory
block. If the memory block has been offlined, __offline_pages()
will fail. So we should try to offline one memory block at a
From: Wen Congyang we...@cn.fujitsu.com
The memory device has only one node id. Store the node id when
enable the memory device, and we can reuse it when removing the
memory device.
CC: David Rientjes rient...@google.com
CC: Jiang Liu liu...@gmail.com
CC: Len Brown len.br...@intel.com
CC:
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
Since applying a patch(de7f0cba96786c), release_mem_region() has been changed
as called in PAGES_PER_SECTION chunks because register_memory_resource() is
called in PAGES_PER_SECTION chunks by add_memory(). But it seems firmware
dependency. If
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
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
The patch adds __remove_pages() to remove_memory(). Then the range of
phys_start_pfn argument and nr_pages argument in __remove_pagse() may
have different zone. So zone argument is removed from __remove_pages()
and __remove_pages()
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
When calling unregister_node(), the function shows following message at
device_release().
Device 'node2' does not have a release() function, it is broken and must be
fixed.
So the patch implements node_device_release()
CC: David Rientjes
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
The patch adds node_set_offline() and unregister_one_node() to remove_memory()
for removing sysfs file of node.
CC: David Rientjes rient...@google.com
CC: Jiang Liu liu...@gmail.com
CC: Len Brown len.br...@intel.com
CC: Benjamin
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 these when the memory is
removed. Add a new function __remove_zone() to do this.
CC: David Rientjes
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
There is a possibility that get_page_bootmem() is called to the same page many
times. So when get_page_bootmem is called to the same page, the function only
increments page-_count.
CC: David Rientjes rient...@google.com
CC: Jiang Liu
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
For implementing register_page_bootmem_info_node of sparse-vmemmap,
register_page_bootmem_info_node and put_page_bootmem are moved to
memory_hotplug.c
CC: David Rientjes rient...@google.com
CC: Jiang Liu liu...@gmail.com
CC: Len Brown
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
From: Wen Congyang we...@cn.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 freed or not?
From: Yasuaki Ishimatsu isimatu.yasu...@jp.fujitsu.com
When calling remove_memory_block(), the function shows following message at
device_release().
Device 'memory528' does not have a release() function, it is broken and must
be fixed.
remove_memory_block() calls kfree(mem). I think it shouled
From: Wen Congyang we...@cn.fujitsu.com
We don't call __add_pages() directly in the function add_memory()
because some other architecture related things need to be done
before or after calling __add_pages(). So we should introduce
a new function arch_remove_memory() to revert the things
done in
The first patch fixed a kernel panic when scanning PCI bus if it is working
in agent mode.
In later two patches we unified PCI initialization code by changing fsl_pci
to a platform drvier. The approach will affect swiotlb init and this issue
is addressed in the second patch.
All boards are
We change fsl_add_bridge to return -ENODEV if the controller is working in
agent mode. Then check the return value of fsl_add_bridge to guarantee
that only successfully added host bus will be scanned.
Signed-off-by: Jia Hongtao b38...@freescale.com
Signed-off-by: Li Yang le...@freescale.com
---
Remove the dependency on PCI initialization for SWIOTLB initialization.
So that PCI can be initialized at proper time.
SWIOTLB is partly determined by PCI inbound/outbound map which is assigned
in PCI initialization. But swiotlb_init() should be done at the stage of
mem_init() which is much
We unified the Freescale pci/pcie initialization by changing the fsl_pci
to a platform driver. In previous PCI code architecture the initialization
routine is called at board_setup_arch stage. Now the initialization is done
in probe function which is architectural better. Also It's convenient for
On Aug 2, 2012, at 9:21 PM, Jia Hongtao-B38951 wrote:
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Thursday, August 02, 2012 8:55 PM
To: Jia Hongtao-B38951
Cc: linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421; Li Yang-R58472
Subject: Re: [PATCH V4
Ben:
Here is the OProfile patch to reject samples for marked events if the
SIAR register is not valid. Please review and let me know if it looks
OK. Thanks.
Carl Love
-
Power 7+, OProfile:
On Jul 31, 2012, at 9:42 AM, Varun Sethi wrote:
All SOC device error interrupts are muxed and delivered to the core as a
single
MPIC error interrupt. Currently all the device drivers requiring access to
device
errors have to register for the MPIC error interrupt as a shared interrupt.
Ben,
Weekly bug fix pull request.
- k
The following changes since commit 0d7614f09c1ebdbaa1599a5aba7593f147bf96ee:
Linux 3.6-rc1 (2012-08-02 16:38:10 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git merge
for you to fetch
Guys,
As v3.6-rc1 is now out we really need to get some of these simpler patches
upstream and accepted NOW. Please provide status updates if the patch is
upstream already let me know.
[P1025RDB] (some major differences between upstream and internal P1025RDB
support)
powerpc/85xx: Add Quicc
Sorry,
This meant for an internal fsl list.
- k
On Aug 3, 2012, at 8:51 AM, Gala Kumar-B11780 wrote:
Guys,
As v3.6-rc1 is now out we really need to get some of these simpler patches
upstream and accepted NOW. Please provide status updates if the patch is
upstream already let me know.
On Aug 3, 2012, at 5:14 AM, Jia Hongtao wrote:
We change fsl_add_bridge to return -ENODEV if the controller is working in
agent mode. Then check the return value of fsl_add_bridge to guarantee
that only successfully added host bus will be scanned.
Signed-off-by: Jia Hongtao
On 08/02/2012 09:23 PM, Michael Ellerman wrote:
virt_to_abs() is just a wrapper around __pa(), use __pa() directly.
We should be including asm/page.h to get __pa(). abs_addr.h will be
removed shortly so drop that.
We were getting of.h via abs_addr.h so we need to include that directly.
On Fri, Aug 3, 2012 at 8:38 PM, Kumar Gala ga...@kernel.crashing.org wrote:
On Aug 2, 2012, at 9:21 PM, Jia Hongtao-B38951 wrote:
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Thursday, August 02, 2012 8:55 PM
To: Jia Hongtao-B38951
Cc:
Hi,
I'm actually chasing a problem with GDB and hw watchpoints for embedded
ppc targets.
If a thread X creates thread Y, is it expected that thread Y will
inherit all the debug state from thread X? Including, for example, any
hardware watchpoints/breakpoints that are set in thread X?
Hi,
I'm actually chasing a problem with GDB and hw watchpoints for embedded
ppc targets.
If a thread X creates thread Y, is it expected that thread Y will
inherit all the debug state from thread X? Including, for example, any
hardware watchpoints/breakpoints that are set in thread X?
On 08/02/2012 10:39 PM, Jia Hongtao-B38951 wrote:
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Thursday, August 02, 2012 8:24 PM
To: Jia Hongtao-B38951
Cc: linuxppc-dev@lists.ozlabs.org; Wood Scott-B07421; Li Yang-R58472
Subject: Re: [PATCH V4 3/3]
On 08/02/2012 09:20 PM, Jia Hongtao-B38951 wrote:
-Original Message-
From: Wood Scott-B07421
Sent: Friday, August 03, 2012 4:19 AM
To: Jia Hongtao-B38951
Cc: linuxppc-dev@lists.ozlabs.org; ga...@kernel.crashing.org; Wood Scott-
B07421; Li Yang-R58472
Subject: Re: [PATCH V4 3/3]
On Aug 3, 2012, at 9:42 AM, Li Yang wrote:
On Fri, Aug 3, 2012 at 8:38 PM, Kumar Gala ga...@kernel.crashing.org wrote:
On Aug 2, 2012, at 9:21 PM, Jia Hongtao-B38951 wrote:
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Thursday, August 02, 2012
On 08/03/2012 05:14 AM, Jia Hongtao wrote:
-void __devinit fsl_pci_init(void)
+/* Checkout if PCI contains ISA node */
+static int of_pci_has_isa(struct device_node *pci_node)
+{
+ struct device_node *np;
+ int ret = 0;
+
+ if (!pci_node)
+ return 0;
+
+
On 08/03/2012 08:19 AM, Kumar Gala wrote:
On Jul 31, 2012, at 9:42 AM, Varun Sethi wrote:
+/* ioremap'ed base for error interrupt registers */
+u32 __iomem *err_regs;
+/* error interrupt config */
+u32 err_int_config_done;
+
Is this really needed
On Jul 9, 2012, at 8:04 AM, Varun Sethi wrote:
Added CPU_FTR_EMB_HV feature check for e550.
Signed-off-by: Varun Sethi varun.se...@freescale.com
Signed-off-by: Mihai Caraman mihai.cara...@freescale.com
---
arch/powerpc/kernel/cpu_setup_fsl_booke.S |6 ++
1 files changed, 6
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Friday, August 03, 2012 6:49 PM
To: Sethi Varun-B16395
Cc: linuxppc-dev@lists.ozlabs.org; Hamciuc Bogdan-BHAMCIU1
Subject: Re: [PATCH 3/3 v3] powerpc/mpic: FSL MPIC error interrupt
support.
On Jul
On Aug 3, 2012, at 11:44 AM, Scott Wood wrote:
On 08/03/2012 08:19 AM, Kumar Gala wrote:
On Jul 31, 2012, at 9:42 AM, Varun Sethi wrote:
+ /* ioremap'ed base for error interrupt registers */
+ u32 __iomem *err_regs;
+ /* error interrupt config */
+ u32
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Saturday, August 04, 2012 12:43 AM
To: Wood Scott-B07421
Cc: Sethi Varun-B16395; Hamciuc Bogdan-BHAMCIU1; linuxppc-
d...@lists.ozlabs.org
Subject: Re: [PATCH 3/3 v3] powerpc/mpic: FSL MPIC error interrupt
On Aug 3, 2012, at 2:16 PM, Sethi Varun-B16395 wrote:
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Saturday, August 04, 2012 12:43 AM
To: Wood Scott-B07421
Cc: Sethi Varun-B16395; Hamciuc Bogdan-BHAMCIU1; linuxppc-
d...@lists.ozlabs.org
Subject:
On Aug 3, 2012, at 1:52 PM, Sethi Varun-B16395 wrote:
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Friday, August 03, 2012 6:49 PM
To: Sethi Varun-B16395
Cc: linuxppc-dev@lists.ozlabs.org; Hamciuc Bogdan-BHAMCIU1
Subject: Re: [PATCH 3/3 v3]
-Original Message-
From: Kumar Gala [mailto:ga...@kernel.crashing.org]
Sent: Saturday, August 04, 2012 12:55 AM
To: Sethi Varun-B16395
Cc: linuxppc-dev@lists.ozlabs.org; Hamciuc Bogdan-BHAMCIU1
Subject: Re: [PATCH 3/3 v3] powerpc/mpic: FSL MPIC error interrupt
support.
On Aug
On Fri, 2012-08-03 at 08:39 -0500, Kumar Gala wrote:
Ben,
Weekly bug fix pull request.
Well, Linus is on holiday so I don't think it makes sense for me to ask
him to pull anything just yet... I'll put it in my tree some time next
week and will send it along with whatever I have as well when
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: edac: Change internal representation to work with layers
Author: Mauro Carvalho Chehab mche...@redhat.com
Date:Wed Apr 18 15:20:50 2012
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: edac: move nr_pages to dimm struct
Author: Mauro Carvalho Chehab mche...@redhat.com
Date:Sat Jan 28 09:09:38 2012 -0300
The number of pages
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: edac: Rename the parent dev to pdev
Author: Mauro Carvalho Chehab mche...@redhat.com
Date:Fri Mar 16 07:44:18 2012 -0300
As EDAC doesn't
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: pasemi_edac: convert driver to use the new edac ABI
Author: Mauro Carvalho Chehab mche...@redhat.com
Date:Mon Apr 16 15:11:36 2012 -0300
This is an automatic generated email to let you know that the following patch
were queued at the
http://git.linuxtv.org/media_tree.git tree:
Subject: edac: change the mem allocation scheme to make
Documentation/kobject.txt happy
Author: Mauro Carvalho Chehab mche...@redhat.com
Date:Tue
53 matches
Mail list logo
