On Fri, 2014-11-28 at 10:53 +, David Laight wrote:
From: Benjamin Herrenschmidt
On Fri, 2014-11-28 at 08:45 +0530, Madhavan Srinivasan wrote:
Can't we just unconditionally clear at as long as we do that after we've
saved it ? In that case, it's just a matter for the fixup code to
Hi,
I've been seeing intermittent hangs when booting a KVM guest on a busy box.
Both host and guest are mainline (3.18-rc6). The backtrace looks like:
INFO: rcu_sched self-detected stall on CPU { 7} (t=8404 jiffies g=-299 c=-300
q=79)
Task dump for CPU 7:
swapper/7 R running task
Memset on a local variable may be removed when it is called just before the
variable goes out of scope. Using memzero_explicit defeats this
optimization. The complete semantic patch that makes this change is as
follows: (http://coccinelle.lip6.fr/)
// smpl
@@
identifier x;
local idexpression e;
From: Julia Lawall ju...@diku.dk
Memset on a local variable may be removed when it is called just before the
variable goes out of scope. Using memzero_explicit defeats this
optimization. A simplified version of the semantic patch that makes this
change is as follows:
Memset on a local variable may be removed when it is called just before the
variable goes out of scope. Using memzero_explicit defeats this
optimization. The complete semantic patch that makes this change is as
follows: (http://coccinelle.lip6.fr/)
// smpl
@@
identifier x;
local idexpression e;
From: Julia Lawall julia.law...@lip6.fr
Memset on a local variable may be removed when it is called just before the
variable goes out of scope. Using memzero_explicit defeats this
optimization. A simplified version of the semantic patch that makes this
change is as follows:
The in kernel XICS emulation is faster than doing it all in QEMU
and it has got a lot of testing, so enable it by default
Signed-off-by: Anton Blanchard an...@samba.org
---
arch/powerpc/kvm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/kvm/Kconfig
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means that num_online_nodes()
returns 4, so when
On Wed, Nov 26, 2014 at 03:07:51PM +1100, Michael Ellerman wrote:
On Mon, 2014-24-11 at 22:26:59 UTC, Gavin Shan wrote:
The flag passed to ioda_eeh_phb_reset() should be EEH_RESET_DEACTIVATE,
which is translated to OPAL_DEASSERT_RESET or something else by the
EEH backend accordingly.
The
On Wed, Nov 26, 2014 at 03:09:10PM +1100, Michael Ellerman wrote:
On Mon, 2014-24-11 at 22:27:00 UTC, Gavin Shan wrote:
PE#0 should be regarded as valid for P7IOC, while it's invalid for
PHB3. The patch adds flag EEH_VALID_PE_ZERO to differentiate those
two cases. Without the patch, we possibly
(2014/12/01 7:16), Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means that
On Mon, Dec 01, 2014 at 09:14:40AM +0900, Yasuaki Ishimatsu wrote:
(2014/12/01 7:16), Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8
On Sun, 2014-11-30 at 18:03 +0100, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
Memset on a local variable may be removed when it is called just before the
variable goes out of scope. Using memzero_explicit defeats this
optimization. A simplified version of the semantic
(2014/12/01 9:42), Paul Mackerras wrote:
On Mon, Dec 01, 2014 at 09:14:40AM +0900, Yasuaki Ishimatsu wrote:
(2014/12/01 7:16), Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic
irq_dispose_mapping() in turns calls unregister_irq_proc(),
which will remove irq proc entry, if IRQ is not freed
before calling of irq_dispose_mapping(), then it will cause
kernel warning.
By free IRQ before irq_dispose_mapping(), this patch fix
the following kernel warning found when remove of
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means that num_online_nodes()
returns 4, so when
(2014/12/01 13:28), Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17. This means that
On Mon, 2014-12-01 at 15:28 +1100, Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For example, on a POWER8 machine the node
IDs are typically 0, 1, 16 and 17.
On Mon, Dec 01, 2014 at 04:02:14PM +1100, Michael Ellerman wrote:
On Mon, 2014-12-01 at 15:28 +1100, Paul Mackerras wrote:
The bounds check for nodeid in cache_alloc_node gives false
positives on machines where the node IDs are not contiguous, leading
to a panic at boot time. For
On Fri, 2014-28-11 at 04:36:42 UTC, Anshuman Khandual wrote:
This patch enables support for hardware instruction breakpoint in
xmon on POWER8 platform with the help of a new register called the
CIABR (Completed Instruction Address Breakpoint Register). With this
patch, a single hardware
Drop BP_IABR_TE, which though used, does not do anything useful. Rename
BP_IABR to BP_CIABR. Renumber the flags.
Signed-off-by: Michael Ellerman m...@ellerman.id.au
---
arch/powerpc/xmon/xmon.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
This is on top of
On Friday 28 November 2014 05:20 AM, Paul Mackerras wrote:
On Tue, Nov 25, 2014 at 04:47:58PM +0530, Shreyas B. Prabhu wrote:
[snip]
+2:
+/* Sleep or winkle */
+li r7,1
+mfspr r8,SPRN_PIR
+/*
+ * The last 3 bits of PIR represents the thread id of a cpu
+ *
Hi,
On Mon, Dec 01, 2014 at 11:50:51AM +0900, Jiada Wang wrote:
irq_dispose_mapping() in turns calls unregister_irq_proc(),
which will remove irq proc entry, if IRQ is not freed
before calling of irq_dispose_mapping(), then it will cause
kernel warning.
By free IRQ before
23 matches
Mail list logo
