linux-kernel - Re: [PATCH v2 1/3] tracing,x86: add a TSC trace

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, 18 Sep 2012 14:46:43 -0700
From:	David Sharp <dhsharp@...gle.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH v2 1/3] tracing,x86: add a TSC trace_clock

On Wed, Sep 12, 2012 at 6:23 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> This change will require an ack from one of the x86 maintainers.
>
> For reference to this patch, please see this thread:
>
>  https://lkml.org/lkml/2012/9/11/572
>
> On Wed, 2012-09-12 at 16:31 -0700, David Sharp wrote:
>> In order to promote interoperability between userspace tracers and ftrace,
>> add a trace_clock that reports raw TSC values which will then be recorded
>> in the ring buffer. Userspace tracers that also record TSCs are then on
>> exactly the same time base as the kernel and events can be unambiguously
>> interlaced.
>>
>> Tested: Enabled a tracepoint and the "tsc" trace_clock and saw very large
>> timestamp values.
>>
>> v2:
>> Move arch-specific bits out of generic code.
>
> As Masami pointed out, please add a SOB to your patches.

Sorry about that. I guess that's what happens when I rush before going
on vacation. Apparently I did `git format-patch --signoff` the first
time instead of in the commit.
--
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/