linux-kernel - LTTng 0.51, improved timestamping

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-next>] [day] [month] [year] [list]

Message-ID: <20081106074543.GA18558@Krystal>
Date:	Thu, 6 Nov 2008 02:45:43 -0500
From:	Mathieu Desnoyers <compudj@...stal.dyndns.org>
To:	ltt-dev@...ts.casi.polymtl.ca
Cc:	linux-kernel@...r.kernel.org
Subject: LTTng 0.51, improved timestamping

Hi,

LTTng 0.51 for 2.6.27.4 does the following :

It improves timestamping on architectures with non-synchronized TSCs in
LTTng 0.51. I also now use per-cpu timers to do some time-related stuff
I previously used IPIs for. It involves being more closely tied to the
CPU hotplug callbacks.

I also replaced x86 tsc_sync.c test by LTTng architecture independent
test. (this will be posted separately on LKML for 2.6.28-rc3 tomorrow
along with the "tracer clock" patchset).

The event trap_entry, syscall_entry, irq_entry, softirq entry, exit and
raise now use smaller fields (2 bytes), which should be enough to encode
the IDs for all architectures. This will principally make a difference
with non-aligned tracing for most of those events.

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
--
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/