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-next>] [day] [month] [year] [list]

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

Frederic Weisbecker wrote:
> This patchset adds all the features to draw hardirq triggering on output
> for the function graph tracer.
> An example is given on the third patch.
> 
> Just one question, on recordmcount.pl:
> 
> my %text_sections = (
>       ".text" => 1,
>       ".sched.text" => 1,
>       ".spinlock.text" => 1,
> 
> The .sched.text section is included inside .text, it's a subsection, I'm not sure
> it's necessary to add it in text_sections. In doubt I added the new .irqentry.text
> 
> The stat of the patchset:
> 
>  arch/x86/kernel/apic.c               |    3 +-
>  arch/x86/kernel/irq_64.c             |    3 +-
>  arch/x86/kernel/vmlinux_64.lds.S     |    1 +
>  include/asm-generic/vmlinux.lds.h    |   10 +++++
>  include/linux/ftrace.h               |   11 ++++++
>  kernel/trace/trace_functions_graph.c |   66 +++++++++++++++++++++++++++++++--
>  scripts/recordmcount.pl              |    1 +
>  7 files changed, 89 insertions(+), 6 deletions(-)
> 
> 

Sorry, forgot to cc LKML on this one.
--
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/