linux-kernel - Re: [RFC PATCH v3 4/4] trace: Trace log handler for logging into STM blocks

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: <20150708132207.GA23380@gmail.com>
Date:	Wed, 8 Jul 2015 15:22:08 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Chunyan Zhang <zhang.chunyan@...aro.org>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>, mingo@...hat.com,
	Mathieu Poirier <mathieu.poirier@...aro.org>,
	Serge Broslavsky <serge.broslavsky@...aro.org>,
	broonie@...nel.org,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
	Lyra Zhang <zhang.lyra@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v3 4/4] trace: Trace log handler for logging into STM
 blocks


* Chunyan Zhang <zhang.chunyan@...aro.org> wrote:

> >> +++ b/include/trace/perf.h
> >> @@ -175,6 +175,7 @@ trace_event_raw_event_##call(void *__data, proto)                 \
> >>       { assign; }                                                     \
> >>                                                                       \
> >>       trace_event_buffer_commit(&fbuffer);                            \
> >> +     trace_event_stm_log(&fbuffer);                                  \
> >
> > This makes every trace event slower.
> 
> It doesn't actually, you may decide if enable this feature, the trace event will 
> not be slowed if STM_TRACE_EVENT is not selected.

It slows down everyone if a distro enables this feature - that's not acceptable.

Thanks,

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