linux-kernel - Re: [PATCH 2/2] tracing/events: Add kexec tracepoints

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 08 Sep 2009 21:39:26 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Li Zefan <lizf@...fujitsu.com>, Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] tracing/events: Add kexec tracepoints

On Tue, 2009-09-08 at 18:27 -0700, Eric W. Biederman wrote:
> Li Zefan <lizf@...fujitsu.com> writes:
> 
> > When panic, save in ring buffer the time when crash happened,
> > the panic message, etc. And the data can be retrieved from
> > core dump file using flight-recorder, which is going to be a
> > module of the crash utility.
> >
> > Also if we implement flight-recorder in perf tool, those trace
> > outputs can be used by perf tool.
> 
> Please let's keep dynamic code out of crash_kexec if we can.

What dynamic code? It's a tracepoint not something like the function
tracer. It is activated via a bit test and a jmp. Not very dynamic.

-- Steve


> 
> If this is just about timestamsp I don't see the point.


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