mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: ltt-dev@lists.casi.polymtl.ca
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: LTTng 0.52, scheduler instrumentation
Date: Thu, 6 Nov 2008 20:08:22 -0500	[thread overview]
Message-ID: <20081107010821.GA23269@Krystal> (raw)

Hi,

I just released LTTng 0.52 for 2.6.27.4. It fixes the stuff I dreamt
about this morning. ;-)

Ingo what do you think about this first point ?

- I now only use 2 bytes to encode the task->state field in the trace.
  However it seems that 1 byte would be enough (bitmask of values 0 to
  127), except that -1 is used for "unrunnable". But when it's
  unrunnable, it should "never" be reach scheduler events, right ?

Changelog :
- Add kernel command line : force_tsc_sync=1 to force tsc
  synchronization at boot.
- Supports AMD64 X2 box with unsynchronized TSCs very well. Includes
  a warning that tells users to try
  force_tsc_sync=1 idle=poll and to disable PowerNow or Speedstep to get
  synchronized timestamp counters on x86. This workaround works very
  well.
- Default to no LTT alignment for traces if
  HAVE_EFFICIENT_UNALIGNED_ACCESS is selected.
- Fixed mixed up irq entry field names in (appeared in 0.51).

Some testing would be required with virtualization to see how it
behaves.

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

                 reply	other threads:[~2008-11-07  1:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20081107010821.GA23269@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    /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

all inboxes | Powered by JetHome®