From: Christoph Hellwig <hch@infradead.org>
To: Dave Jones <davej@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Paul Mundt <lethal@linux-sh.org>, Greg KH <greg@kroah.com>,
zanussi@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] relay: Migrate from relayfs to a generic relay API.
Date: Mon, 20 Feb 2006 16:03:13 +0000 [thread overview]
Message-ID: <20060220160313.GA31846@infradead.org> (raw)
In-Reply-To: <20060219225437.GE7974@redhat.com>
On Sun, Feb 19, 2006 at 05:54:37PM -0500, Dave Jones wrote:
> On Sun, Feb 19, 2006 at 10:48:20PM +0000, Christoph Hellwig wrote:
> > On Sun, Feb 19, 2006 at 05:29:43PM -0500, Dave Jones wrote:
> > > systemtap uses kprobes to export data through relayfs.
> >
> > systemtap has never been anywhere near mainline despit me telling the
> > ibm folks to get the non-braindead parts in, so it simply doesn't matter.
>
> the kernel bits that matter are generated at runtime.
> I don't see anything particularly interesting in the source tree
> that is worthwhile submitting.
Various helpers to write kprobes in C, instead of the funky limited
functionality scripting language of the day.
But anyway, if systemtap folks really need a relayfs filesystem type
they're totally free under the gpl to grab the code Paul posted to
recreate relayfs ontop of kernel/relay.c and include it in their codebase,
no need to bloat the kernel tree with unused code.
next prev parent reply other threads:[~2006-02-20 16:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 21:07 [PATCH 0/5] relay: Migrate from relayfs to a generic relay API Paul Mundt
2006-02-19 21:07 ` [PATCH 1/5] sysfs: relay channel buffers as sysfs attributes Paul Mundt
2006-02-23 10:59 ` Maneesh Soni
2006-02-24 8:34 ` Paul Mundt
2006-02-24 9:35 ` Maneesh Soni
2006-02-19 21:08 ` [PATCH 2/5] relay: Consolidate relayfs core into kernel/relay.c Paul Mundt
2006-02-19 21:08 ` [PATCH 3/5] sysfs: Update relay file support for generic relay API Paul Mundt
2006-02-19 21:08 ` [PATCH 4/5] relayfs: Remove relayfs in favour of CONFIG_RELAY Paul Mundt
2006-02-19 21:09 ` [PATCH 5/5] relay: relay header cleanup Paul Mundt
2006-02-19 21:21 ` [PATCH 0/5] relay: Migrate from relayfs to a generic relay API Dave Jones
2006-02-19 21:27 ` Paul Mundt
2006-02-19 21:54 ` [PATCH] relayfs: Convert to " Paul Mundt
2006-02-19 22:09 ` Christoph Hellwig
2006-02-19 22:08 ` [PATCH 0/5] relay: Migrate from relayfs to a " Christoph Hellwig
2006-02-19 22:13 ` Dave Jones
2006-02-19 22:17 ` Christoph Hellwig
2006-02-19 22:29 ` Dave Jones
2006-02-19 22:48 ` Christoph Hellwig
2006-02-19 22:54 ` Dave Jones
2006-02-20 16:03 ` Christoph Hellwig [this message]
2006-02-20 20:05 ` Frank Ch. Eigler
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=20060220160313.GA31846@infradead.org \
--to=hch@infradead.org \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--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.