On 03/20/2011 11:53 PM, Benjamin Herrenschmidt wrote:
On Sat, 2011-03-19 at 21:11 -0700, Hugh Dickins wrote:
As I warned a few weeks ago, Jeremy has vmalloc apply_to_pte_range
patches in mmotm, which again assault PowerPC's expectations, and
cause lots of noise with CONFIG_PREEMPT=y
Hi Ben.
I've submitted the fix for the xics mask real irq I mentioned.
During testing I realized current code is passing rtas a linux irq,
which means no interrupt (at least those above NR_IRQs) is being disabled.
I also created a patch to rename irq to hwirq in xics to try to make
the
If a given firmware doesn't have a token to support query-cpu-stopped-state,
its not likely to change during the lifetime of the kernel.
Only print this information once, not once per secondary thread.
While here, make the line wrap grep friendly.
Signed-off-by: Milton Miller milt...@bga.com
To try to avoid future confusion, rename irq to hwirq when it refers
to a xics domain number instead of a linux irq number.
Signed-off-by: Milton Miller milt...@bga.com
Index: next.git/arch/powerpc/platforms/pseries/xics.c
===
---
[reposting part of private email exchange as penance for my sins...]
On Mon, Mar 21, 2011 at 12:22 PM, Grant Likely
grant.lik...@secretlab.ca wrote:
On Sun, Mar 20, 2011 at 4:52 PM, Benjamin Herrenschmidt
b...@kernel.crashing.org wrote:
Grant, what in hell makes you believe that this patch was
commit 79f26c268ebad29bd75d078cfc09d3d82b30ccbd (powerpc:
platforms/pseries irq_data conversion) pushed irq_desc down into many
functions, dererencing the descriptor irq field as late as possible.
But it incorrectly passed a linix virtural irq number to RTAS,
resulting in the interrupt not being
On Mon, 2011-03-21 at 11:24 +, Jeremy Fitzhardinge wrote:
I'm very sorry about that, I didn't realize power was also using that
interface. Unfortunately, the no preemption definition was an error,
and had to be changed to match the pre-existing locking rules.
Could you implement a
On Thu, Mar 3, 2011 at 9:54 AM, Ira W. Snyder i...@ovro.caltech.edu wrote:
This makes debugging the driver much easier when multiple channels are
running concurrently. In addition, you can see how much descriptor
memory each channel has allocated via the dmapool API in sysfs.
Signed-off-by:
Hi all,
I have query about usage of range field at pcie@0 under PCIe controller.
Please find snap shot from mpc8536_36.dts..
pci3: pcie@fffe0b000 {
compatible = fsl,mpc8548-pcie;
device_type = pci;
#interrupt-cells = 1;
