Hi Al,
Today's linux-next merge of the signal tree got a conflict in
arch/powerpc/kernel/entry_64.S between commit c58ce2b1e3c7 (ppc64: fix
missing to check all bits of _TIF_USER_WORK_MASK in preempt) from Linus'
tree and commit d07644a97726 (powerpc: missing NOTIFY_RESUME check on
64bit if
On Mon, 2 Jul 2012 at 14:50, Benjamin Herrenschmidt wrote:
Interesting... I observed something roughly similar on a dual G4
the other day associated with a 30s to 1mn pause during boot. RCU
was complaining loudly.
In my case, it did continue booting normally, is that the case for you ?
No,
Hi,
On Tue, Jun 26, 2012 at 11:27:13AM -0300, Alexandre Pereira da Silva wrote:
Grab the devicetree node properties to override VendorId, ProductId,
bcdDevice, Manucacturer, Product and SerialNumber
Signed-off-by: Alexandre Pereira da Silva aletes@gmail.com
I need Grant's acked-by to
On Fri, Jun 29, 2012 at 10:39:24AM -0500, Tabi Timur-B04825 wrote:
On Tue, Jun 26, 2012 at 5:25 AM, Zhao Chenhui
chenhui.z...@freescale.com wrote:
Do hardware timebase sync. Firstly, stop all timebases, and transfer
the timebase value of the boot core to the other core. Finally,
start all
Hi Stephan,
On Sun, 01 Jul 2012 08:47:01 +0200
Stephan Gatzka step...@gatzka.org wrote:
Hi Albrecht,
I don't recall who proposed this patch, but exactly this solution is
around for a longer time (mayby you search archives...). On my board, I
have a flash chip attached to the
On Thu, Jun 28, 2012 at 08:50:51PM +1000, Benjamin Herrenschmidt wrote:
On Thu, 2012-06-28 at 11:38 +0800, Zhao Chenhui wrote:
The bootloader have done a timebase sync. If we do not need KEXEC or
HOTPLUG_CPU feature, it is unnecessary to do it again at boot time of
kernel. I only
The powerpc kernel doesn't export the memory limit enforced by 'mem='
kernel parameter. This is required for building the ELF header in
kexec-tools to limit the vmcore to capture only the used memory. On
powerpc the kexec-tools depends on the device-tree for memory related
information, unlike
On Mon, 2 Jul 2012 at 14:50, Benjamin Herrenschmidt wrote:
while trying to upgrade from 3.4.0 to 3.5.0-rc5 on this Powerbook G4
(powerpc 32 bit), this happens during booting:
--
usb 2-1: new full-speed USB device number 4 using ohci_hcd
SCSI subsystem initialized
scsi0
On Apr 16, 2012, at 8:42 PM, chang-ming.hu...@freescale.com
chang-ming.hu...@freescale.com wrote:
From: Jerry Huang chang-ming.hu...@freescale.com
Add the RTC support for p1022ds
Signed-off-by: Jerry Huang chang-ming.hu...@freescale.com
---
arch/powerpc/boot/dts/p1022ds.dtsi |4
Hi!
This problem has been discussed several times [1], [2], but wasn't
resolved yet. The clean solution suggested was to implement a custom
mapping driver [3].
Then I'll do that. It doesn't look terribly complicated.
It would be helpful if someone can test the first version if it's
On Sun, Jul 01, 2012 at 11:30:40PM -0700, Christian Kujau wrote:
On Mon, 2 Jul 2012 at 14:50, Benjamin Herrenschmidt wrote:
Interesting... I observed something roughly similar on a dual G4
the other day associated with a 30s to 1mn pause during boot. RCU
was complaining loudly.
In my
On Apr 16, 2012, at 8:42 PM, chang-ming.hu...@freescale.com
chang-ming.hu...@freescale.com wrote:
From: Jerry Huang chang-ming.hu...@freescale.com
The compatilbe 'simple-bus' is removed from the latest DTS for NAND and
NOR flash partition, so we must add the new compatilbe support for
Kumar Gala wrote:
No, I forgot all about it. I'll try it today, assuming the lone 8323
board in the board farm still works.
Do you remember if you ever tested this?
Well, I tried to test it. We have an 83xx board that has a QE UART that
needs firmware uploaded, but I don't know how to
On Mon, 2 Jul 2012 at 09:45, Paul E. McKenney wrote:
On Sun, Jul 01, 2012 at 11:30:40PM -0700, Christian Kujau wrote:
On Mon, 2 Jul 2012 at 14:50, Benjamin Herrenschmidt wrote:
Interesting... I observed something roughly similar on a dual G4
the other day associated with a 30s to 1mn
From: Stuart Yoder stuart.yo...@freescale.com
Signed-off-by: Stuart Yoder stuart.yo...@freescale.com
---
-this patch is a pre-requisite for the idle hcall which I
am trying to get into Alex's KVM tree, so ideally would like
Ben's ack and get this applied to Alex's tree
-built/tested with a
On 02.07.2012, at 22:56, Stuart Yoder wrote:
From: Stuart Yoder stuart.yo...@freescale.com
Signed-off-by: Stuart Yoder stuart.yo...@freescale.com
---
-this patch is a pre-requisite for the idle hcall which I
am trying to get into Alex's KVM tree, so ideally would like
Ben's ack and get
From: Stuart Yoder stuart.yo...@freescale.com
Signed-off-by: Stuart Yoder stuart.yo...@freescale.com
---
-this patch is a pre-requisite for the idle hcall which I
am trying to get into Alex's KVM tree, so ideally would like
Ben's ack and get this applied to Alex's tree
-built/tested with a
On 02.07.2012, at 23:14, Stuart Yoder wrote:
From: Stuart Yoder stuart.yo...@freescale.com
Signed-off-by: Stuart Yoder stuart.yo...@freescale.com
---
-this patch is a pre-requisite for the idle hcall which I
am trying to get into Alex's KVM tree, so ideally would like
Ben's ack and get
On Mon, 2012-07-02 at 22:59 +0200, Alexander Graf wrote:
This should go into an #ifdef __ASSEMBLY__ block, right? :)
We almost never use #ifdef __ASSEMBLY__, we use it the other way around,
to prevent C stuff from being included in assembly. The other way around
is legit since things might be
On Mon, 2012-07-02 at 16:14 -0500, Stuart Yoder wrote:
-v2
-moved CURRENT_THREAD_INFO under assembly only
#ifdef
Nak, invert the two cases to avoid the if_n_def, but don't move it
inside __ASSEMBLY__ only.
IE. Address Alex other comment :-)
Cheers,
Ben.
On 02.07.2012, at 23:26, Benjamin Herrenschmidt wrote:
On Mon, 2012-07-02 at 22:59 +0200, Alexander Graf wrote:
This should go into an #ifdef __ASSEMBLY__ block, right? :)
We almost never use #ifdef __ASSEMBLY__, we use it the other way around,
to prevent C stuff from being included in
On 07/02/2012 04:27 PM, Alexander Graf wrote:
On 02.07.2012, at 23:26, Benjamin Herrenschmidt wrote:
On Mon, 2012-07-02 at 22:59 +0200, Alexander Graf wrote:
This should go into an #ifdef __ASSEMBLY__ block, right? :)
We almost never use #ifdef __ASSEMBLY__, we use it the other way
On 02.07.2012, at 23:31, Scott Wood wrote:
On 07/02/2012 04:27 PM, Alexander Graf wrote:
On 02.07.2012, at 23:26, Benjamin Herrenschmidt wrote:
On Mon, 2012-07-02 at 22:59 +0200, Alexander Graf wrote:
This should go into an #ifdef __ASSEMBLY__ block, right? :)
We almost never use
Original-Nachricht
Datum: Mon, 02 Jul 2012 14:57:39 +1000
Von: Benjamin Herrenschmidt b...@kernel.crashing.org
An: Linus Torvalds torva...@linux-foundation.org
CC: linuxppc-dev list linuxppc-...@ozlabs.org, Andrew Morton
a...@linux-foundation.org, Linux Kernel list
On Mon, 2012-07-02 at 23:38 +0200, Gerhard Pircher wrote:
What about this fix:?
http://patchwork.ozlabs.org/patch/166346/
At least I can't see it in the log...
The module fix went in. The ftrace patch, well, it's untested and we
don't even know if we have a problem with mcount yet, so
On 07/02/2012 02:35 AM, Felipe Balbi wrote:
Hi,
On Tue, Jun 26, 2012 at 11:27:13AM -0300, Alexandre Pereira da Silva wrote:
Grab the devicetree node properties to override VendorId, ProductId,
bcdDevice, Manucacturer, Product and SerialNumber
Signed-off-by: Alexandre Pereira da Silva
On Mon, Jul 2, 2012 at 7:54 PM, Jiang Liu jiang@huawei.com wrote:
On 2012-7-3 4:43, Yinghai Lu wrote:
On Sun, Jul 1, 2012 at 7:01 PM, Jiang Liu jiang@huawei.com wrote:
Hi Yinghai,
The patch fails compilation as below:
mm/page_alloc.c:151: error: initializer element is not
On 2012-7-3 4:43, Yinghai Lu wrote:
On Sun, Jul 1, 2012 at 7:01 PM, Jiang Liu jiang@huawei.com wrote:
Hi Yinghai,
The patch fails compilation as below:
mm/page_alloc.c:151: error: initializer element is not constant
mm/page_alloc.c:151: error: expected ‘,’ or ‘;’ before
Hi Yinghai,
I'm afraid the v2 will break powerpc. Currently only IA64 and PowerPC
supports variable hugetlb size.
HPAGE_SHIFT is a variable default to 0 on powerpc. But seems PowerPC
is doing something wrong here, according to it's mm initialization
sequence as below:
start_kernel()
This patch series aims to support physical memory hot-remove.
[RFC PATCH v2 1/13] memory-hotplug : rename remove_memory to offline_memory
[RFC PATCH v2 2/13] memory-hotplug : add physical memory hotplug code to
acpi_memory_device_remove
[RFC PATCH v2 3/13] memory-hotplug : unify argument
remove_memory() does not remove memory but just offlines memory. The patch
changes name of it to offline_memory().
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
acpi_memory_device_remove() has been prepared to remove physical memory.
But, the function only frees acpi_memory_device currentlry.
The patch adds following functions into acpi_memory_device_remove():
- offline memory
- remove physical memory (only return -EBUSY)
- free acpi_memory_device
There are two ways to create /sys/firmware/memmap/X sysfs:
- firmware_map_add_early
When the system starts, it is calledd from e820_reserve_resources()
- firmware_map_add_hotplug
When the memory is hot plugged, it is called from add_memory()
But these functions are called without
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 firmware_map_entry since there is no way to free
memory which
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 CRS are written in the PAGES_PER_SECTION chunks in ACPI
35 matches
Mail list logo
