All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Theodore Tso <tytso@mit.edu>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	systemtap@sourceware.org,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: Re: [PATCH] systemtap: add parser for simple markers
Date: Sat, 12 Jul 2008 19:06:37 -0400	[thread overview]
Message-ID: <20080712230637.GA1976@redhat.com> (raw)
In-Reply-To: <1215893086.3360.25.camel@localhost.localdomain>

Hi -

> This is the systemtap piece that allows you to use simple markers as
> probe points for people who want to play around with the
> functionality. [...]

Clever.  We can include support for this as soon as kernel-side
simple_mark widget go upstream.

(For completeness, the code would need test cases, docs, and desirably
support for wildcarding as in probe kernel.simple_mark("*").)


- FChE

  reply	other threads:[~2008-07-12 23:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1215638551.3444.39.camel__22002.9595810503$1215638656$gmane$org@localhost.localdomain>
2008-07-10  2:29 ` [RFC] simple dprobe like markers for the kernel Frank Ch. Eigler
2008-07-10 13:49   ` James Bottomley
2008-07-10 14:22     ` Frank Ch. Eigler
2008-07-10 14:43       ` James Bottomley
2008-07-10 15:30         ` Theodore Tso
2008-07-10 15:57           ` James Bottomley
2008-07-10 18:18           ` Frank Ch. Eigler
2008-07-12 18:22           ` [PATCH] " James Bottomley
2008-07-12 20:04             ` [PATCH] systemtap: add parser for simple markers James Bottomley
2008-07-12 23:06               ` Frank Ch. Eigler [this message]
2008-07-14 16:26             ` [PATCH] simple dprobe like markers for the kernel Masami Hiramatsu
2008-07-14 22:02               ` James Bottomley

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=20080712230637.GA1976@redhat.com \
    --to=fche@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=systemtap@sourceware.org \
    --cc=tytso@mit.edu \
    /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.