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: <1255439904.7113.1545.camel@gandalf.stny.rr.com>
Date:	Tue, 13 Oct 2009 09:18:24 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	mingo@...hat.com, hpa@...or.com, mathieu.desnoyers@...ymtl.ca,
	anton@...ba.org, linux-kernel@...r.kernel.org,
	peterz@...radead.org, zhaolei@...fujitsu.com,
	xiaoguangrong@...fujitsu.com, fweisbec@...il.com,
	tglx@...utronix.de, kosaki.motohiro@...fujitsu.com,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:timers/tracing] hrtimer: Add tracepoint for hrtimers

On Tue, 2009-10-13 at 09:17 -0400, Steven Rostedt wrote:
> On Tue, 2009-10-13 at 09:08 +0200, Ingo Molnar wrote:
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> > 
> 
> > > (unsigned long long)(((ktime_t) { .tv64 = REC->expires }).tv64)
> > > 
> > > Is not easy. It's basically implementing a C interpreter :-(
> > 
> > Btw., what i suggested quite some time ago was that we should bind 
> > tracepoints by emitting C source code stubs, which tools can then build 
> > and link in, using gcc.
> 
> Yeah, and I thought about that too. But that kills any chance of running
> the trace on one box (non x86) and reading it on another (x86). And that
> is one of my goals for this.

I'd love to see the kernel code for having this also understand ktime_t.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ