public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Schilling <schilling@fokus.fraunhofer.de>
To: linux-kernel@vger.kernel.org
Subject: Re: DTrace-like analysis possible with future Linux kernels?
Date: Tue, 24 Aug 2004 06:14:06 +0200	[thread overview]
Message-ID: <412AC08E.nailBG411JOFC@burner> (raw)

Christoph Halder wrote:

>True, to europeans this sounds far too overenthusiastic - almost like a 
>commercial - and will most certainly lead to the impression, that the 
>article is not very serious.
>
>Europeans try to write serious articles VERY neutral - any personal 
>opinion(s) will only be a short statement at the very end of the article.

No, it is definitely not overestimated.

It is more likely to rather be the opposite and you will find this out if you
try to use dtrace or attend a demo.

Dou you know of any other system where you can say:

	Print me a strack trace with symbols for all processes on this
	computer (even stripped ones) that call gettimeofday() within the
	next few seconds.

Note that you do not need a special kernel, no reboot, no restart of 
applications.

There are a lot more possibilities including tracing kernel routines on a 
production kernel but it would take too long to describe them....

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de		(uni)  If you don't have iso-8859-1
       schilling@fokus.fraunhofer.de	(work) chars I am J"org Schilling
 URL:  http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily

             reply	other threads:[~2004-08-24  4:14 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-24  4:14 Joerg Schilling [this message]
2004-08-28 19:15 ` DTrace-like analysis possible with future Linux kernels? Alan Cox
     [not found] <2wAWW-12a-11@gated-at.bofh.it>
2004-08-24 13:04 ` Pascal Schmidt
2004-08-24 13:07   ` Joerg Schilling
     [not found] <2v3Ad-5tc-29@gated-at.bofh.it>
     [not found] ` <2v4w9-6aQ-5@gated-at.bofh.it>
     [not found]   ` <2vxeJ-4kg-3@gated-at.bofh.it>
     [not found]     ` <2vZNN-7AT-33@gated-at.bofh.it>
     [not found]       ` <2w5q4-34M-1@gated-at.bofh.it>
     [not found]         ` <2w9Dq-65C-13@gated-at.bofh.it>
2004-08-23 18:19           ` Andi Kleen
     [not found] <2ptdY-42Y-55@gated-at.bofh.it>
     [not found] ` <2uPdM-380-11@gated-at.bofh.it>
     [not found]   ` <2uUwL-6VP-11@gated-at.bofh.it>
     [not found]     ` <2uWfh-8jo-29@gated-at.bofh.it>
     [not found]       ` <2uXl0-Gt-27@gated-at.bofh.it>
     [not found]         ` <2vge2-63k-15@gated-at.bofh.it>
     [not found]           ` <2vgQF-6Ai-39@gated-at.bofh.it>
     [not found]             ` <2vipq-7O8-15@gated-at.bofh.it>
     [not found]               ` <2vj2b-8md-9@gated-at.bofh.it>
     [not found]                 ` <2vDtS-bq-19@gated-at.bofh.it>
2004-08-21 15:01                   ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Pascal Schmidt
2004-08-21 15:57                     ` Joerg Schilling
2004-08-22 11:56                       ` Joerg Schilling
2004-08-22 13:13                         ` Pascal Schmidt
2004-08-22 16:00                           ` Christer Weinigel
2004-08-22 16:32                             ` Joerg Schilling
2004-08-22 17:18                               ` Christer Weinigel
2004-08-22 19:22                                 ` DTrace-like analysis possible with future Linux kernels? Joerg Schilling
2004-08-22 19:26                             ` PATCH: cdrecord: avoiding scsi device numbering for ide devices Tonnerre
2004-08-22 20:14                               ` DTrace-like analysis possible with future Linux kernels? Joerg Schilling
2004-08-22 20:33                                 ` Tonnerre
2004-08-22 20:38                                   ` Alan Cox
2004-08-22 20:43                                   ` Joerg Schilling
2004-08-22 21:37                                     ` Christer Weinigel
2004-08-23 11:44                                       ` Joerg Schilling
2004-08-23 17:40                                 ` Horst von Brand
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19 22:22 Miles Lane
2004-08-19 23:01 ` Karim Yaghmour
2004-08-19 23:23 ` Julien Oster
2004-08-19 22:33   ` Alan Cox
2004-08-20 10:08     ` Alex Bennee
2004-08-20 11:21       ` Robert Schwebel
2004-08-20  0:23   ` Florian Weimer
2004-08-20 13:34     ` Alexander Nyberg
2004-08-20 13:46       ` Florian Weimer
2004-08-20 16:46         ` David S. Miller
2004-08-21  6:03   ` Tomasz Kłoczko
2004-08-21  6:12     ` David S. Miller
2004-08-21  6:22       ` Tomasz Kłoczko
2004-08-21 12:12     ` Julien Oster
2004-08-21 13:27       ` Tomasz Kłoczko
2004-08-21 21:49       ` Bryan Cantrill
2004-08-23 23:08         ` Christoph Halder
2004-08-22 11:35     ` Alan Cox
2004-08-22 18:27       ` Tomasz Kłoczko
2004-08-22 18:46         ` Alan Cox
2004-08-23 17:34           ` Tomasz Kłoczko
2004-08-22 23:03         ` John Levon
2004-08-23 19:48       ` Robert Milkowski
2004-08-24  0:39         ` David S. Miller
2004-08-28 19:16         ` Alan Cox
2004-08-29  0:14           ` Tomasz Kłoczko
2004-08-29  5:30             ` David S. Miller
2004-08-29 10:45               ` Tomasz Kłoczko
2004-08-29 17:46                 ` David S. Miller
2004-08-29 10:53               ` Robert Milkowski
2004-08-29 10:29           ` Robert Milkowski
2004-08-31 20:16   ` Timothy Miller

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=412AC08E.nailBG411JOFC@burner \
    --to=schilling@fokus.fraunhofer.de \
    --cc=linux-kernel@vger.kernel.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