public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Combine instrumentation menus in kernel/Kconfig.instrumentation
Date: Tue, 18 Sep 2007 21:06:28 -0400	[thread overview]
Message-ID: <20070919010627.GA24174@Krystal> (raw)
In-Reply-To: <14754.1190151939@turing-police.cc.vt.edu>

[-- Attachment #1: Type: text/plain, Size: 1686 bytes --]

* Valdis.Kletnieks@vt.edu (Valdis.Kletnieks@vt.edu) wrote:
> On Tue, 18 Sep 2007 17:12:59 EDT, Mathieu Desnoyers said:
> 
> > +++ linux-2.6-lttng/kernel/Kconfig.instrumentation	2007-09-18 13:18:17.000
> 000000 -0400
> > @@ -0,0 +1,40 @@
> > +menuconfig INSTRUMENTATION
> > +	bool "Instrumentation Support"
> > +	default y
> > +	---help---
> > +	  Say Y here to get to see options related to performance measurement,
> > +	  debugging, and testing. This option alone does not add any kernel code.
> > +
> > +	  If you say N, all options in this submenu will be skipped and disabled.
> 
> OK, I'll bite - given the mention of 'debugging' there, do we want to go for
> broke and *also* suck in the 'Kernel Hacking' menu as well?

Instrumentation primarity aims at debugging user-space applications by
giving the ability to extract information across execution layers, hence
being a feature useful to users, not only kernel hackers. Therefore I
strongly doubt that it belongs to the kernel hacking submenu. It today's
world, where we face complex user-space problems involving
multithreaded, multiprocesses applications, the kernel and
hypervisors, running on many cores, this kind of tool has proven useful
to many, not only kernel developers. Please have a look at the
papers (especially the OLS2007 paper) linked on http://ltt.polymtl.ca as a
starting point if you are intereted in the question.

But yes, it can also be useful to kernel debugging, amongst other
things.

Mathieu


-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-09-19  1:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18 21:12 [PATCH] Combine instrumentation menus in kernel/Kconfig.instrumentation Mathieu Desnoyers
2007-09-18 21:45 ` Valdis.Kletnieks
2007-09-19  1:06   ` Mathieu Desnoyers [this message]
2007-09-19  5:57     ` Valdis.Kletnieks
2007-09-19 11:20       ` Mathieu Desnoyers
2007-09-19 11:33         ` Robert P. J. Day
2007-09-19 11:45           ` Mathieu Desnoyers
  -- strict thread matches above, loose matches on Subject: below --
2007-09-17 18:45 Mathieu Desnoyers
2007-09-18 18:37 ` Randy Dunlap

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=20070919010627.GA24174@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    /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