From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@lists.casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ltt-dev] LTTng 0.51, improved timestamping
Date: Thu, 6 Nov 2008 08:10:34 -0500 [thread overview]
Message-ID: <20081106131034.GA29679@Krystal> (raw)
In-Reply-To: <20081106074543.GA18558@Krystal>
disable tsc synth when ! trace clock ?
tsc synth get/put ?
amd64 :
- single cpu -> tsc_is_sync : no force on unstable tsc ?
- hotplug out all cpus, recheck
* Mathieu Desnoyers (compudj@krystal.dyndns.org) wrote:
> 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
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev@lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2008-11-06 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 7:45 LTTng 0.51, improved timestamping Mathieu Desnoyers
2008-11-06 13:10 ` Mathieu Desnoyers [this message]
2008-11-06 13:13 ` [ltt-dev] " Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081106131034.GA29679@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox