linux-kernel - Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output

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]

Date:	Mon, 15 Dec 2008 09:03:21 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Frédéric Weisbecker <fweisbec@...il.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt
 triggering on output

On Sat, 2008-12-13 at 08:49 +0100, Ingo Molnar wrote:
> * Frédéric Weisbecker <fweisbec@...il.com> wrote:
> 
> > > applied to tip/tracing/function-graph-tracer, thanks Frederic!
> > >
> > > The output looks really nice.
> > >
> > >        Ingo
> > >
> > 
> > Thanks :-)
> > 
> > If anyone  has other needs or suggestions about this tracer, don't
> > hesitate to request it.
> > I remember Peter suggested that the preempt count could be output.
> 
> that reminds me ... did you know about hardirq_count()? We could use it 
> to detect IRQ entries in a more generic way, instead of the section 
> trick?

hardirq_count() is set from __irq_enter(), which is too late, we've
already had all the ARCH irq code before that.



--
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/