From: Martin Hunt <hunt@redhat.com>
To: David Wilder <dwilder@us.ibm.com>
Cc: systemTAP <systemtap@sources.redhat.com>
Subject: Re: Hooking into systemtaps relay chanell
Date: Thu, 03 May 2007 02:45:00 -0000 [thread overview]
Message-ID: <1178160315.4000.33.camel@dragon> (raw)
In-Reply-To: <4639180B.9010401@us.ibm.com>
On Wed, 2007-05-02 at 16:00 -0700, David Wilder wrote:
> Is there anyway for a probe handler to be passed pointer to the relay
> channel that systemtap is using to pass its data?
>
> I have a bit of code that is written as part of a tap set, but is not
> run as part of a probe. I would like that code to write data into
> systemtap's relay channel. So, I need to find the address of the
> channel at run time. Is this possible?
Will _stp_reserve_bytes() do what you need?
I am still tweaking our use of relayfs a bit. Writing directly to a
relayfs channel bypassing the runtime IO functions will likely not work
well or might break in the near future. If you can explain more what
you are trying to do I am sure we can work out a solution.
Martin
prev parent reply other threads:[~2007-05-03 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 22:18 David Wilder
2007-05-03 2:37 ` Frank Ch. Eigler
2007-05-03 2:45 ` Martin Hunt [this message]
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=1178160315.4000.33.camel@dragon \
--to=hunt@redhat.com \
--cc=dwilder@us.ibm.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).