linux-kernel - Re: [PATCH] ftrace: use a global counter for the global clock

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: <1316179491.26295.38.camel@gandalf.stny.rr.com>
Date:	Fri, 16 Sep 2011 09:24:51 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, mingo <mingo@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ftrace:  use a global counter for the global clock

On Fri, 2011-09-16 at 09:23 -0400, Steven Rostedt wrote:
> On Fri, 2011-09-16 at 14:36 +0200, Peter Zijlstra wrote:
> > On Fri, 2011-09-16 at 08:18 -0400, Steven Rostedt wrote:
> > > +       return atomic64_add_return(1, &trace_counter);
> > 
> > Oh, fwiw I modified mine to increment by 1000 because we're showing us
> > in the trace output, 1000 lines with the same 'time'-stamp is slightly
> > confusing even though you know the order is absolutely right...
> 
> 
> Or I could change it so that if counter clock is set, just show that
> field as a counter too.
> 

Hmm, as I have other things to work on. I think I'll take your
suggestion of the 1000 increment for now ;)

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