Hi Ben,
Looks like something that got fixed but the new patches from Bjorn
aren't in next yet. I'll fwd you the patch separately to apply on top
of what you have see if that helps (to confirm that's indeed the
issue).
Thanks, confirmed that it fixes it. Patch below in case anyone else is
We want to implement a ppc64 specific version of atomic_inc_not_zero
so wrap it in an ifdef to allow it to be overridden.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/include/linux/atomic.h
===
--- linux
: 39 00 00 00 li r8,0
- c01b63c4: 39 40 00 01 li r10,1
...
- c01b63e8: 7c 0a 00 50 subfr0,r10,r0
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/include/asm/atomic.h
| tail -1
SAMPLE events: 9948
Signed-off-by: Anton Blanchard an...@samba.org
---
Cc: sta...@kernel.org
Index: linux-build/arch/powerpc/kernel/perf_event.c
===
--- linux-build.orig/arch/powerpc/kernel/perf_event.c 2012-02
multiplatform builds.
The simple fix is to avoid tracing H_CEDE and rely on other tracepoints
and the hypervisor dispatch trace log to work out if we called H_CEDE.
This fixes a hang during boot on pSeries.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel
Hi,
This is 2.6.32, but I think 2.6.36 is the same.
Sounds a bit like this, merged in 2.6.39.
Anton
--
commit ad5d1c888e556bc00c4e86f452cad4a3a87d22c1
Author: Anton Blanchard an...@samba.org
Date: Sun Mar 20 15:28:03 2011 +
powerpc: Fix accounting of softirq time when idle
We support 16TB of user address space and half a million contexts
so update the comment to reflect this.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/include/asm/mmu-hash64.h
===
--- linux
add:
Cc: sta...@vger.kernel.org [2.6.37+]
so it will make it back into the stable trees?
Anton
Signed-off-by: Andreas Schwab sch...@linux-m68k.org
FWIW:
Acked-by: Anton Blanchard an...@samba.org
---
arch/powerpc/include/asm/cputime.h |6 +++---
arch/powerpc/kernel/time.c
Hi Andreas,
There is no user of usecs_to_cputime before 3.2-rc1, so it wouldn't
have any effect for older versions.
Great, that explains why I only noticed it last week :)
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
we can calculate the break points quickly.
- One suggestion from Ben was to save and restore the VSX registers
we use inline instead of using enable_kernel_altivec.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/include/asm/cputable.h
Hi,
I hate the idea of having a POWER7 FTR bit. Every loon will (and has
tried to in the past) attach every POWER7 related thing to it, rather
than thinking about what the feature really is for.
What about other processors which could also benefit from this copy
loop? Turning on
we can calculate the break points quickly.
- One suggestion from Ben was to save and restore the VSX registers
we use inline instead of using enable_kernel_altivec.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/include/asm/cputable.h
the boot
issues we have on 128MB RMO boxes and all new machines have virtual
RMO, we may as well set our minimum to 256MB.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/prom_init.c
===
--- linux
Here are a number of patches I've put together based on some rather
strenuous testing of our oops and kdump paths.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
, then delay 1 second before calling into the
panic code. Move oops_exit inside the die lock and put a newline
between oopses for clarity.
Signed-off-by: Anton Blanchard an...@samba.org
---
We should really rename kexec_should_crash() to something like
kernel_will_panic() and use it here. I'll work
We have a lot of complicated logic that handles possible recursion between
kdump and a system reset exception. We can solve this in a much simpler
way using the same setjmp/longjmp tricks xmon does.
As a first step, this patch removes the old system reset code.
Signed-off-by: Anton Blanchard
continue
the kdump.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/crash.c
===
--- linux-build.orig/arch/powerpc/kernel/crash.c2011-11-25
16:41:06.228864087 +1100
+++ linux-build/arch
Remove some unnecessary defines and fix some spelling mistakes.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/crash.c
===
--- linux-build.orig/arch/powerpc/kernel/crash.c2011-11-25
Our die() code was based off a very old x86 version. Update it to
mirror the current x86 code.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/traps.c
===
--- linux-build.orig/arch/powerpc
it is to power cycle.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/platforms/pseries/setup.c
===
--- linux-build.orig/arch/powerpc/platforms/pseries/setup.c 2011-11-08
11:41:51.84258 +1100
+++ linux
I have an intermittent kdump fail where the hypervisor fails an H_EOI.
As a result our CPPR is never reset to 0xff and we no longer accept
interrupts.
This patch calls icp_hv_set_cppr to reset the CPPR if H_EOI fails,
fixing the kdump fail.
Signed-off-by: Anton Blanchard an...@samba.org
handler which is not what we want.
I took the opportunity to add defines for all the various delays
we have. There's no need for cpu_relax when we are doing an mdelay,
so remove them too.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/crash.c
.
For controlling progress now use atomic_t cpus_in_crash to count how
many CPUs have made it into the kdump code, and time_to_dump to tell
everyone it's time to dump.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/crash.c
Most distros use it so we may as well enable it and get regular compile
testing.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux-powerpc.orig/arch/powerpc
at exactly
the same time but I think it's best to play it safe for now. Once we
are happy with the reliability we can change it to a full spinlock.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/platforms/pseries/nvram.c
Hi Ben,
How would we miss ?
trylock does loop on stwcx. failure, it doesn't loop if the lock is
-taken-, so if the lock is only used for actually dealing with the
oops the only miss is because somebody already got it... or am I
missing something ?
I'm thinking of two CPUs that enter at
Hi Kumar,
static void register_decrementer_clockevent(int cpu)
{
struct clock_event_device *dec = per_cpu(decrementers,
cpu).event; @@ -955,7 +928,8 @@ static void __init
init_decrementer_cloc {
int cpu = smp_processor_id();
- setup_clockevent_multiplier(ppc_tb_freq);
and for
completeness add the rest of the bits in.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/process.c
===
--- linux-build.orig/arch/powerpc/kernel/process.c 2011-11-25
13:22:24.294919094
and continue on. Add some more information to the
debug messages as well.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/sysdev/xics/icp-hv.c
===
--- linux-build.orig/arch/powerpc/sysdev/xics/icp-hv.c 2011
From: Milton Miller milt...@bga.com
show_stack uses up to 4 printks per line and other CPUs using printk
can corrupt the output. This patch calls printk once per stack frame
line to produce more readable output.
Signed-off-by: Milton Miller milt...@bga.com
Signed-off-by: Anton Blanchard
Here is a roll up of various time fixes I have pending.
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
the cause of the lockup.
We already keep track of the timebase of the next event so use that
to work out if we should trigger a decrementer exception.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
- I'd like to get this into -stable if possible since the reports
We can use clockevents_calc_mult_shift instead of doing all
the work ourselves.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
===
--- linux-build.orig/arch/powerpc/kernel/time.c
Use clocksource_register_hz which calculates the shift/mult
factors for us. Also remove the shift = 22 assumption in
vsyscall_update - thanks to Paul Mackerras and John Stultz for
catching that.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
The clockevents code uses max_delta_ns to avoid calling a
clockevent with too large a value.
Remove the redundant version of this in the timer_interrupt
code.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
Fix some formatting issues and use the DECREMENTER_MAX
define instead of 0x7fff.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
===
--- linux-build.orig/arch/powerpc/kernel
-cr7,6c .arch_local_irq_restore+0x6c
...
6c: ld r30,-16(r1)
70: blr
Unfortunately we still setup a local TOC (due to -mminimal-toc). Yet
another sign we should be moving to -mcmodel=medium.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc
we added
POWERNV (breaks everyone).
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org [v3.0+]
---
Index: linux-build/arch/powerpc/include/asm/sections.h
===
--- linux-build.orig/arch/powerpc/include/asm/sections.h
and failing in mysterious ways we should just
panic up front if RTAS exists and we can't allocate space for it.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/prom_init.c
===
--- linux-powerpc.orig
We've resisted adding System RAM to /proc/iomem because it is
the wrong place for it. Unfortunately we continue to find tools
that rely on this behaviour so give up and add it in.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/mm/mem.c
We can use clockevents_calc_mult_shift instead of doing all
the work ourselves.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
===
--- linux-build.orig/arch/powerpc/kernel/time.c
Use clocksource_register_hz which calculates the shift/mult
factors for us.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
===
--- linux-build.orig/arch/powerpc/kernel/time.c 2011-11
Fix some formatting issues and use the DECREMENTER_MAX
define instead of 0x7fff.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/arch/powerpc/kernel/time.c
===
--- linux-build.orig/arch/powerpc/kernel
Hi Jimi,
It would really help me a lot if you could review and maybe merge
this with my earlier patch that splits this file.
http://patchwork.ozlabs.org/patch/109103/ All it does is split.. I
promise. You don't have to take the other stuff.. yet :)
Sorry it took so long to get to this.
100644
index 000..2f1dd29
--- /dev/null
+++ b/arch/powerpc/mm/icswx.c
@@ -0,0 +1,162 @@
+/*
+ * ICSWX and ACOP Management
+ *
+ * Copyright (C) 2011 Anton Blanchard, IBM Corp. an...@samba.org
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify
Hi Peter,
On Mon, 2011-07-25 at 12:33 +1000, Anton Blanchard wrote:
Here are a set of ppc64 scheduler fixes that help with some
multi node performance issues.
They look fine to me. I'll probably ping you when I'll rip out all
that SD_NODES_PER_DOMAIN crap for good, but until then I'm
mm_users constant, take the
page table spinlock.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
diff --git a/arch/powerpc/mm/mmu_context_hash64.c
b/arch/powerpc/mm/mmu_context_hash64.c
index 3bafc3d..4ff587e 100644
--- a/arch/powerpc/mm/mmu_context_hash64.c
+++ b/arch
Return -EINVAL instead of creating these bad regions.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-build/drivers/base/memory.c
===
--- linux-build.orig/drivers/base/memory.c 2011-08-11 08:25:55.005941391
Hi Mahesh,
Just a few comments.
+#define RMR_START0x0
+#define RMR_END (0x1UL 28) /* 256 MB */
What if the RMO is bigger than 256MB? Should we be using ppc64_rma_size?
+#ifdef DEBUG
+#define PREFIX fadump:
+#define DBG(fmt...) printk(KERN_ERR PREFIX
Hi,
+static void fadump_show_config(void)
+{
+ DBG(Support for firmware-assisted dump (fadump): %s\n,
+ (fw_dump.fadump_supported ? present : no support));
+
+ if (!fw_dump.fadump_supported)
+ return;
+
+ DBG(Fadump enabled: %s\n,
+
diff --git a/kernel/panic.c b/kernel/panic.c
index 6923167..1965b50 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -49,6 +49,15 @@ static long no_blink(int state)
long (*panic_blink)(int state);
EXPORT_SYMBOL(panic_blink);
+#ifdef CONFIG_FA_DUMP
+/*
+ * provide an empty
During hotplug CPU add we get the following error:
Unexpected Error (0) returned from configure-connector
ibm,configure-connector returns 0 for configuration complete, so
catch this and avoid the error.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc
only
need the handle the case where we terminate the loop early.
As suggested by Stephen Rothwell we can do the of_node_put
unconditionally outside of the loop since of_node_put handles a
NULL argument fine.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux
Use for_each_node_by_type instead of open coding it.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/machine_kexec_64.c
===
--- linux-powerpc.orig/arch/powerpc/kernel/machine_kexec_64.c
While converting code to use for_each_node_by_type I noticed a
number of coding style issues.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/setup_64.c
===
--- linux-powerpc.orig/arch
/memory/probe
-bash: echo: write error: Invalid argument
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-build/arch/powerpc/mm/hash_utils_64.c
===
--- linux-build.orig/arch/powerpc/mm/hash_utils_64
the
duplicate one inside the loop.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-powerpc/arch/powerpc/mm/numa.c
===
--- linux-powerpc.orig/arch/powerpc/mm/numa.c 2011-06-06 08:07:35.148708089
Use for_each_node_by_type instead of open coding it.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/machine_kexec_64.c
===
--- linux-powerpc.orig/arch/powerpc/kernel/machine_kexec_64.c
While converting code to use for_each_node_by_type I noticed a
number of coding style issues.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/setup_64.c
===
--- linux-powerpc.orig/arch
Hi Stephen,
Index: linux-powerpc/arch/powerpc/mm/numa.c
===
--- linux-powerpc.orig/arch/powerpc/mm/numa.c 2011-06-06
08:07:35.148708089 +1000 +++
linux-powerpc/arch/powerpc/mm/numa.c2011-08-10
-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/platforms/Kconfig
===
--- linux-powerpc.orig/arch/powerpc/platforms/Kconfig 2011-08-01
17:33:46.120121554 +1000
+++ linux-powerpc/arch/powerpc/platforms
will get 128MB.
We cap it at 256MB (small SLB size) since some early allocations need
to be in the bolted SLB region. We could relax this on machines with
1TB SLBs in a future patch.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/include/asm/kdump.h
The ibm,io-events code is a bit verbose with its error messages.
Reverse the reporting so we only print when we successfully enable
I/O event interrupts.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/platforms/pseries/io_event_irq.c
with
an obvious error. We could relocate the device tree in a future
patch.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-powerpc/arch/powerpc/kernel/prom_init.c
===
--- linux-powerpc.orig/arch
Add a newline to the panic messages in make_room. Also fix a
comment that suggested our chunk size is 4Mb. It's 1MB.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/prom_init.c
00 00 00 lfs f0,0(0)
c0ad0a24: 00 ac a4 20 .long 0xaca420
And the jump table sort code gets very confused and writes into the
wrong spot. Remove the alignment and also remove the padding since
we it saves some space and we shouldn't need it.
Signed-off-by: Anton Blanchard
.long 0xaca420
And the jump table sort code gets very confused and writes into the
wrong spot. Remove the alignment, and also remove the padding since
we it saves some space and we shouldn't need it.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/include/asm
On a box with 8TB of RAM the MMU hashtable is 64GB in size. That
means we have 4G PTEs. pSeries_lpar_hptab_clear was using a signed
int to store the index which will overflow at 2G.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-powerpc/arch/powerpc
Here are a few pseries kexec fixes after testing on a recent version
version.
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
is ignored by firmware on unregister so we
may as well remove it.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-powerpc/arch/powerpc/platforms/pseries/kexec.c
===
--- linux-powerpc.orig/arch/powerpc
Make the VPA, SLB shadow and DTL registration and deregistration
functions print consistent messages on error. I needed the firmware
error code while chasing a kexec bug but we weren't printing it.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/platforms
The VPA, SLB shadow and DTL degistration functions do not need an
address, so simplify things and remove it.
Also cleanup pseries_kexec_cpu_down a bit by storing the cpu IDs
in local variables.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/platforms
Here are a set of ppc64 scheduler fixes that help with some
multi node performance issues.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Signed-off-by: Anton Blanchard an...@samba.org
---
Cc-ing arch maintainers who might need to look at their SD_NODE_INIT
definitions
Index: linux-2.6-work/arch/powerpc/include/asm/topology.h
===
--- linux-2.6-work.orig/arch/powerpc
We want to override the default value of SD_NODES_PER_DOMAIN on ppc64,
so move it into linux/topology.h.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-2.6-work/include/linux/topology.h
===
--- linux-2.6-work.orig
The largest POWER7 boxes have 32 nodes. SD_NODES_PER_DOMAIN groups
nodes into chunks of 16 and adds a global balancing domain
(SD_ALLNODES) above it.
If we bump SD_NODES_PER_DOMAIN to 32, then we avoid this extra
level of balancing on our largest boxes.
Signed-off-by: Anton Blanchard
on the scheduler tick to
rebalance across nodes.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-2.6-work/arch/powerpc/include/asm/topology.h
===
--- linux-2.6-work.orig/arch/powerpc/include/asm/topology.h 2011-07-25
12:14
We have two identical definitions of RECLAIM_DISTANCE, looks like
the patch got applied twice. Remove one.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-2.6-work/arch/powerpc/include/asm/topology.h
===
--- linux
when reading the stack otherwise
we can lock up trying to take the mmap_sem when the code we are
profiling already has a write lock taken.
This will not happen for hardware events, but could for software
events.
Reported-by: David Ahern dsah...@gmail.com
Signed-off-by: Anton Blanchard
Hi Peter,
That looks very strange indeed.. up to node 23 there is the normal
symmetric matrix with all the trace elements on 10 (as we would expect
for local access), and some 4x4 sub-matrix stacked around the trace
with 20, suggesting a single hop distance, and the rest on 40 being
Hi Peter,
So with that fix the patch makes the machine happy again?
Yes, the machine looks fine with the patches applied. Thanks!
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Hi David,
As a result of changes to Kconfig files, we no longer enable
the lockup and hung task detectors. Both are very light weight
and provide useful information in the event of a hang, so
reenable them.
...
+CONFIG_LOCKUP_DETECTOR=y
+CONFIG_DETECT_HUNG_TASK=y
Is one of thise
Hi,
That looks very strange indeed.. up to node 23 there is the normal
symmetric matrix with all the trace elements on 10 (as we would expect
for local access), and some 4x4 sub-matrix stacked around the trace
with 20, suggesting a single hop distance, and the rest on 40 being
out-there.
On Mon, 18 Jul 2011 23:35:56 +0200
Peter Zijlstra a.p.zijls...@chello.nl wrote:
Anton, could you test the below two patches on that machine?
It should make things boot again, while I don't have a machine nearly
big enough to trigger any of this, I tested the new code paths by
setting
Hi,
Urgh.. so those spans are generated by sched_domain_node_span(), and
it looks like that simply picks the 15 nearest nodes to the one we've
got without consideration for overlap with previously generated spans.
I do wonder if we need this extra level at all on ppc64. From memory
SGI added
Hi,
Add poll_get_char and poll_put_char for kdb. Enable kdb at boot
with:
Did you mean ...for kgdb. Enable kgdb at boot.. ?
I thought kdb and kgdb shared some infrastructure now, but your patch
and comments seem to be all about kgdb.
No I do mean kdb :) From the Documentation:
Hi Peter,
Surely this isn't the first multi-node P7 to boot a kernel with this
patch? If my git foo is any good it hit -next on 23rd of May.
I guess I'm asking is, do smaller P7 machines boot? And if so, is
there any difference except size?
How many nodes does the thing have anyway, 28?
I took a quick look and we are stuck in update_group_power:
do {
power += group-cpu_power;
group = group-next;
} while (group != child-groups);
I looked at the linked list:
child-groups = c07b2f74ff00
and dumping group as we go:
into
and give it out as requested.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/drivers/tty/hvc/hvc_vio.c
===
--- linux-powerpc.orig/drivers/tty/hvc/hvc_vio.c2011-07-13
14:37:16.251635811 +1000
Add poll_get_char and poll_put_char for kdb. Enable kdb at boot with:
kgdboc=hvc0
or at runtime with:
echo hvc0 /sys/module/kgdboc/parameters/kgdboc
Signed-off-by: Anton Blanchard an...@samba.org
---
A couple of things:
- I needed to enable CONFIG_KGDB_SERIAL_CONSOLE in order to
enable
debugfs now so we may as well turn it into a pr_debug.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/kernel/irq.c
===
--- linux-powerpc.orig/arch/powerpc/kernel/irq.c2011-07-08
08:49
Hi Hendrik,
So with the patch below, the backend can now indirectly control the
way console output is handled for it. I still have to think if this
solution is ok or if it is better to introduce a new callback to
console output only (and might provide a default implemenatation
similar to
control the way how console output is
handled through the hvc console layer.
Signed-off-by: Hendrik Brueckner brueck...@linux.vnet.ibm.com
Acked-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-powerpc/drivers/tty/hvc/hvc_console.c
Return -EAGAIN when we get H_BUSY back from the hypervisor. This
makes the hvc console driver retry, avoiding dropped printks.
Signed-off-by: Anton Blanchard an...@samba.org
Cc: sta...@kernel.org
---
Index: linux-powerpc/arch/powerpc/platforms/pseries/hvconsole.c
On Tue, 05 Jul 2011 16:40:10 +1000
Michael Neuling mi...@neuling.org wrote:
The existing code it pretty ugly. How about we clean it up even more
like this?
Looks good and it passed my kdump test cases.
Anton
From: Anton Blanchard an...@samba.org
We check for timeout expiry in the outer
Here are a few defconfig updates I had lying around in my tree.
Anton
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
The pseries defconfig had a number of drivers enabled and we may
as well add them to the ppc64 defconfig.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux
The IRQs off tracer enables mcount which has a big impact on
performance. Disable it.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux-powerpc.orig/arch
Add mpt2sas driver to pseries and ppc64 defconfig.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/configs/ppc64_defconfig
===
--- linux-powerpc.orig/arch/powerpc/configs/ppc64_defconfig 2011
As a result of changes to Kconfig files, we no longer enable
the lockup and hung task detectors. Both are very light weight
and provide useful information in the event of a hang, so
reenable them.
Signed-off-by: Anton Blanchard an...@samba.org
---
Index: linux-powerpc/arch/powerpc/configs
801 - 900 of 1164 matches
Mail list logo
