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]

Message-ID: <alpine.DEB.1.10.0812092111510.19875@gandalf.stny.rr.com>
Date:	Tue, 9 Dec 2008 21:14:54 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
cc:	Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt
 triggering on output


On Tue, 9 Dec 2008, 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
> 

Matters what objdump -dr shows.

$ objdump -dr kernel/sched.o | grep 'Disassembly'
Disassembly of section .text:
Disassembly of section .cpuinit.text:
Disassembly of section .init.text:
Disassembly of section .sched.text:

Yep, .sched.text is needed.  It is not about what gets linked by the 
linker. It is about what objdump shows, which is what recordmcount.pl uses 
to determine whether or not to record the mcount callers in that section.

-- Steve

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