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: <1273013889.22438.8.camel@gandalf.stny.rr.com>
Date:	Tue, 04 May 2010 18:58:09 -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 17:27 -0500, Larry Finger wrote:

> Thanks for the info. One other question - when I write only mmiotrace to
> the current_tracer, the trace_printk() stuff does not end up in the
> buffer. I can get it by using the "sysprof" tracer, but that has a lot
> of stuff I do not want. Did I miss some configuration? My list of
> available tracers is "blk kmemtrace mmiotrace wakeup_rt wakeup function
> sysprof sched_switch nop".

Ug, that's because the mmiotrace handles its own prints and ignores
anything it does not know about. Here, try this patch:

-- Steve

diff --git a/kernel/trace/trace_mmiotrace.c b/kernel/trace/trace_mmiotrace.c
index 017fa37..8652f28 100644
--- a/kernel/trace/trace_mmiotrace.c
+++ b/kernel/trace/trace_mmiotrace.c
@@ -282,7 +282,7 @@ static enum print_line_t mmio_print_line(struct trace_iterator *iter)
 	case TRACE_PRINT:
 		return mmio_print_mark(iter);
 	default:
-		return TRACE_TYPE_HANDLED; /* ignore unknown entries */
+		return TRACE_TYPE_UNHANDLED;
 	}
 }
 


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