linux-kernel - Re: How to write marker info in MMIO trace from kernel

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: <1272998579.9739.235.camel@gandalf.stny.rr.com>
Date:	Tue, 04 May 2010 14:42:59 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: How to write marker info in MMIO trace from kernel

On Tue, 2010-05-04 at 13:36 -0500, Larry Finger wrote:
> Stephen,
> 
> I hope you are the correct person for this question.
> 
> I would like to write information into the MMIO trace file similar to
> what the user space write to /sys/.../trace_marker would accomplish,
> however, I want to do it in place of printk statements in the driver I'm
> tracing. Do you have any suggestions on how to do this? I have tools to
> merge the trace dump with dmesg output, but the latter lags behind and I
> do not get good correlation.

You can use "trace_printk()". I think that is what you are looking for.

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