From: "Richard W.M. Jones" <rjones@redhat.com>
To: Josh Stone <jistone@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Flushing systemtap output without restarting (was: Re: Rapidly running systemtap causing hangs or oops)
Date: Thu, 23 Jun 2011 12:45:00 -0000 [thread overview]
Message-ID: <20110623124516.GI18438@amd.home.annexia.org> (raw)
In-Reply-To: <20110623101217.GH18438@amd.home.annexia.org>
On Thu, Jun 23, 2011 at 11:12:17AM +0100, Richard W.M. Jones wrote:
> It certainly looks like they run asynch, because my actual output
> (sometimes) looks like:
>
> 1308822714.015994546: mount
> 1308822714.424888519: mount
> 1308822714.43626: module("ext2").statement("ext2_mount@fs/ext2/super.c:1378")
> 1308822714.43634: module("ext2").statement("ext2_mount@fs/ext2/super.c:1379")
> 1308822714.442957: module("ext2").statement("ext2_mount@fs/ext2/super.c:1378")
> 1308822714.442965: module("ext2").statement("ext2_mount@fs/ext2/super.c:1379")
Damn, it's the stupidest mistakes which are the easiest to
overlook.
In fact the ordering (by time) is *correct*. It just appears wrong
because I didn't format the microsecond field with leading zeroes (%06d) ...
Thanks everyone, I will keep going down the timestamp route.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2011-06-23 12:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 23:00 Rapidly running systemtap causing hangs or oops Richard W.M. Jones
2011-06-22 23:52 ` Josh Stone
2011-06-23 7:51 ` Richard W.M. Jones
2011-06-23 10:12 ` Flushing systemtap output without restarting (was: Re: Rapidly running systemtap causing hangs or oops) Richard W.M. Jones
2011-06-23 12:45 ` Richard W.M. Jones [this message]
2011-06-23 14:13 ` Rapidly running systemtap causing hangs or oops Frank Ch. Eigler
2011-06-23 16:16 ` Josh Stone
2011-06-23 16:28 ` Richard W.M. Jones
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=20110623124516.GI18438@amd.home.annexia.org \
--to=rjones@redhat.com \
--cc=jistone@redhat.com \
--cc=systemtap@sourceware.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).