All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: "S. P. Prasanna" <prasanna@in.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	Douglas Niehaus <niehaus@eecs.ku.edu>,
	Tom Zanussi <zanussi@us.ibm.com>,
	Paul Mundt <lethal@linux-sh.org>, Jes Sorensen <jes@sgi.com>,
	Richard J Moore <richardj_moore@uk.ibm.com>,
	William Cohen <wcohen@redhat.com>,
	"Martin J. Bligh" <mbligh@mbligh.org>,
	Michel Dagenais <michel.dagenais@polymtl.ca>,
	systemtap@sources.redhat.com, ltt-dev@shafik.org
Subject: Re: [PATCH] Linux Kernel Markers 0.2 for Linux 2.6.17
Date: Tue, 19 Sep 2006 16:05:14 -0400	[thread overview]
Message-ID: <20060919200514.GB9459@Krystal> (raw)
In-Reply-To: <20060919083900.GE23836@in.ibm.com>

Hi,

* S. P. Prasanna (prasanna@in.ibm.com) wrote:
> I think having so many config options is not a good idea, you can group them
> and reduce the number of config options.
> 

Then we would have to determine what the scenarios are. The problem is to cover
all interesting instrumentation mixes efficiently.

I think it could be a good enough list :

Fprobes only
Dynamic + Fprobes (supports dynamic probes and uses fprobes for non probable
                   code)
Dynamic only
Printk only

Which would be expressed in the following menu :

choice Marker behavior
  * Inactive
  * Dynamic probes
  * Function probes (Fprobes)
  * Dynamic probes complemented with Fprobes
  * Printk

if selected "Dynamic probes" or "Dynamic probes complemented with Fprobes"
  choice2 Dynamic probes behavior
    * Kprobes
    * Jprobes

Any thoughts ?

Mathieu


OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 

  reply	other threads:[~2006-09-19 20:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 18:34 [PATCH] Linux Kernel Markers 0.2 for Linux 2.6.17 Mathieu Desnoyers
2006-09-19  8:39 ` S. P. Prasanna
2006-09-19 20:05   ` Mathieu Desnoyers [this message]
2006-09-19 18:51 ` Randy.Dunlap
2006-09-19 19:13   ` Mathieu Desnoyers
2006-09-19 19:23 ` Frank Ch. Eigler
2006-09-19 19:36   ` Mathieu Desnoyers
2006-09-19 19:45     ` Frank Ch. Eigler
2006-09-19 20:28       ` Mathieu Desnoyers
2006-09-19 21:07         ` Frank Ch. Eigler
2006-09-19 22:11           ` Karim Yaghmour
2006-09-20 13:20             ` Frank Ch. Eigler
2006-09-20 13:38               ` Mathieu Desnoyers
2006-09-20 14:57                 ` Mathieu Desnoyers
2006-09-20 15:53                   ` Frank Ch. Eigler
2006-09-20 16:37                     ` Mathieu Desnoyers
2006-09-20 17:14                     ` Mathieu Desnoyers
2006-09-20 13:46               ` Mathieu Desnoyers

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=20060919200514.GB9459@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hch@infradead.org \
    --cc=jes@sgi.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=mbligh@mbligh.org \
    --cc=michel.dagenais@polymtl.ca \
    --cc=mingo@redhat.com \
    --cc=niehaus@eecs.ku.edu \
    --cc=prasanna@in.ibm.com \
    --cc=richardj_moore@uk.ibm.com \
    --cc=systemtap@sources.redhat.com \
    --cc=tglx@linutronix.de \
    --cc=wcohen@redhat.com \
    --cc=zanussi@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.