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: <c62985530810130110r5ba73d04wec70e597abd48126@mail.gmail.com>
Date:	Mon, 13 Oct 2008 10:10:42 +0200
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	"Arjan van de Ven" <arjan@...ux.intel.com>
Subject: Re: [PATCH 4/5] tracing/fastboot: Add a time field on the sched_switch entry

2008/10/12 Frédéric Weisbecker <fweisbec@...il.com>:
> 2008/10/12 Steven Rostedt <rostedt@...dmis.org>:
>> You can tap into the context switch trace_point too, and have that record
>> a special trace entry for you instead.

Another thing I could do: when a sched switch entry occurs, I could
send a special timestamp entry that
fits my needs just before the commit of the sched entry, only if the
current tracer is the boot tracer. This way I can output
the appropriate timestamp just before output the sched entry.

What do you think?
--
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