lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1287396707.29097.1544.camel@twins>
Date:	Mon, 18 Oct 2010 12:11:47 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Ingo Molnar <mingo@...e.hu>, mathieu.desnoyers@...icios.com,
	sanagi.koki@...fujitsu.com, fweisbec@...il.com,
	rostedt@...dmis.org, nhorman@...driver.com,
	scott.a.mcmillan@...el.com, tglx@...utronix.de,
	laijs@...fujitsu.com, hpa@...or.com, linux-kernel@...r.kernel.org,
	eric.dumazet@...il.com, kaneshige.kenji@...fujitsu.com,
	davem@...emloft.net, izumi.taku@...fujitsu.com,
	kosaki.motohiro@...fujitsu.com, linux-tip-commits@...r.kernel.org,
	Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [sparc build bug] Re: [tip:perf/core] irq: Add tracepoint to
 softirq_raise

On Mon, 2010-10-18 at 11:44 +0200, Peter Zijlstra wrote:
> On Wed, 2010-09-08 at 13:25 +0200, Ingo Molnar wrote:
> > * tip-bot for Lai Jiangshan <laijs@...fujitsu.com> wrote:
> > 
> > > Commit-ID:  2bf2160d8805de64308e2e7c3cd97813cb58ed2f
> > > Gitweb:     http://git.kernel.org/tip/2bf2160d8805de64308e2e7c3cd97813cb58ed2f
> > > Author:     Lai Jiangshan <laijs@...fujitsu.com>
> > > AuthorDate: Mon, 23 Aug 2010 18:42:48 +0900
> > > Committer:  Frederic Weisbecker <fweisbec@...il.com>
> > > CommitDate: Tue, 7 Sep 2010 17:49:34 +0200
> > > 
> > > irq: Add tracepoint to softirq_raise
> > > 
> > > Add a tracepoint for tracing when softirq action is raised.
> > > 
> > > This and the existing tracepoints complete softirq's tracepoints:
> > > softirq_raise, softirq_entry and softirq_exit.
> > > 
> > > And when this tracepoint is used in combination with
> > > the softirq_entry tracepoint we can determine
> > > the softirq raise latency.
> > > 
> > > Signed-off-by: Lai Jiangshan <laijs@...fujitsu.com>
> > > Acked-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
> > > Acked-by: Neil Horman <nhorman@...driver.com>
> > > Cc: David Miller <davem@...emloft.net>
> > > Cc: Kaneshige Kenji <kaneshige.kenji@...fujitsu.com>
> > > Cc: Izumo Taku <izumi.taku@...fujitsu.com>
> > > Cc: Kosaki Motohiro <kosaki.motohiro@...fujitsu.com>
> > > Cc: Lai Jiangshan <laijs@...fujitsu.com>
> > > Cc: Scott Mcmillan <scott.a.mcmillan@...el.com>
> > > Cc: Steven Rostedt <rostedt@...dmis.org>
> > > Cc: Eric Dumazet <eric.dumazet@...il.com>
> > > LKML-Reference: <4C724298.4050509@...fujitsu.com>
> > > [ factorize softirq events with DECLARE_EVENT_CLASS ]
> > > Signed-off-by: Koki Sanagi <sanagi.koki@...fujitsu.com>
> > > Signed-off-by: Frederic Weisbecker <fweisbec@...il.com>
> > > ---
> > >  include/linux/interrupt.h  |    8 +++++++-
> > >  include/trace/events/irq.h |   26 ++++++++++++++++++++++++--
> > >  2 files changed, 31 insertions(+), 3 deletions(-)
> > 

> I could build sparc64_defconfig, but s390 is broken for me by this...


the below makes s390 build again, not sure its completely safe for all
configs though...

Heiko?

---
 arch/s390/include/asm/hardirq.h |    1 -
 1 files changed, 0 insertions(+), 1 deletions(-)

diff --git a/arch/s390/include/asm/hardirq.h
b/arch/s390/include/asm/hardirq.h
index 498bc38..9558a71 100644
--- a/arch/s390/include/asm/hardirq.h
+++ b/arch/s390/include/asm/hardirq.h
@@ -15,7 +15,6 @@
 #include <linux/threads.h>
 #include <linux/sched.h>
 #include <linux/cache.h>
-#include <linux/interrupt.h>
 #include <asm/lowcore.h>
 
 #define local_softirq_pending() (S390_lowcore.softirq_pending)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ