From: "Martin Bligh" <mbligh@google.com>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "Masami Hiramatsu" <mhiramat@redhat.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Mathieu Desnoyers" <compudj@krystal.dyndns.org>,
"Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
darren@dvhart.com, "Frank Ch. Eigler" <fche@redhat.com>,
systemtap-ml <systemtap@sources.redhat.com>
Subject: Re: Unified tracing buffer
Date: Tue, 23 Sep 2008 21:02:00 -0000 [thread overview]
Message-ID: <33307c790809231402o24c93820tcfbf80d116c729c3@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0809232157580.2038@apollo.tec.linutronix.de>
>> I think the tolerance is about 500 cycles. If that's not sufficient, I guess
>> we'll have to either live with some slight misordering (which people have
>> pointed out is kind of inevitable anyway) on these broken machines?
>> It was sufficient for what we were using it for, but maybe not for everyone.
>
> Well, I dont care about the trace reordering at all. I care about user
> space visible time going backwards issues observed via the
> gettimeofday vsyscall. 500 cycles should be fine, I doubt that we can
> migrate in less than that :)
Right, that's what we were interested in.
> I guess you try this only for machines where the TSC runs with
> constant frequency, right ?
We don't do DVFS on the 'broken' TSC machines, just halt.
But yes, it's selective
next prev parent reply other threads:[~2008-09-23 21:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <33307c790809191433w246c0283l55a57c196664ce77@mail.gmail.com>
2008-09-22 19:47 ` Masami Hiramatsu
2008-09-22 20:14 ` Martin Bligh
2008-09-22 22:27 ` Masami Hiramatsu
2008-09-22 23:12 ` Darren Hart
2008-09-23 0:06 ` Masami Hiramatsu
2008-09-22 23:17 ` Martin Bligh
2008-09-23 0:07 ` Masami Hiramatsu
2008-09-23 0:13 ` Martin Bligh
2008-09-23 14:51 ` Masami Hiramatsu
2008-09-23 15:09 ` Mathieu Desnoyers
2008-09-23 15:32 ` Masami Hiramatsu
2008-09-23 16:02 ` Linus Torvalds
2008-09-23 17:07 ` Masami Hiramatsu
2008-09-23 17:33 ` Thomas Gleixner
2008-09-23 19:03 ` Masami Hiramatsu
2008-09-23 19:37 ` Thomas Gleixner
2008-09-23 19:39 ` Martin Bligh
2008-09-23 19:42 ` Thomas Gleixner
2008-09-23 19:51 ` Martin Bligh
2008-09-23 20:05 ` Thomas Gleixner
2008-09-23 21:02 ` Martin Bligh [this message]
2008-09-23 20:06 ` Masami Hiramatsu
2008-09-23 20:09 ` Thomas Gleixner
2008-09-23 15:48 ` Linus Torvalds
2008-09-23 0:41 ` Linus Torvalds
2008-09-23 1:28 ` Roland Dreier
2008-09-23 1:40 ` Steven Rostedt
2008-09-23 2:08 ` Mathieu Desnoyers
2008-09-23 2:27 ` Darren Hart
2008-09-23 2:32 ` Mathieu Desnoyers
2008-09-23 3:29 ` Linus Torvalds
2008-09-23 3:42 ` Mathieu Desnoyers
2008-09-23 4:06 ` Linus Torvalds
2008-09-23 3:44 ` Steven Rostedt
2008-09-23 4:12 ` Masami Hiramatsu
2008-09-23 4:18 ` Martin Bligh
2008-09-23 15:25 ` Masami Hiramatsu
2008-09-23 10:54 ` Steven Rostedt
2008-09-23 4:20 ` Linus Torvalds
2008-09-23 14:13 ` Mathieu Desnoyers
2008-09-23 2:31 ` Mathieu Desnoyers
2008-09-23 3:07 ` Masami Hiramatsu
2008-09-23 14:38 ` KOSAKI Motohiro
2008-09-23 15:04 ` Frank Ch. Eigler
2008-09-23 15:23 ` Masami Hiramatsu
2008-09-23 18:04 ` KOSAKI Motohiro
2008-09-23 18:29 ` Martin Bligh
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=33307c790809231402o24c93820tcfbf80d116c729c3@mail.gmail.com \
--to=mbligh@google.com \
--cc=compudj@krystal.dyndns.org \
--cc=darren@dvhart.com \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=rostedt@goodmis.org \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).