From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] doc: Add stapsdt provider documentation
Date: Tue, 18 Nov 2025 19:44:41 -0500 [thread overview]
Message-ID: <aR0S+YpnXNaipnez@oracle.com> (raw)
In-Reply-To: <be44a5bf-aaca-b98c-731b-9945ea837702@oracle.com>
On Tue, Nov 18, 2025 at 07:15:16PM -0500, Eugene Loh wrote:
> On 11/18/25 07:43, Alan Maguire wrote:
>
> > On 18/11/2025 04:30, eugene.loh@oracle.com wrote:
> > > From: Eugene Loh <eugene.loh@oracle.com>
> > >
> > > Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
> > looks great, a few small suggestions below, but
> >
> > Reviewed-by: Alan Maguire <alan.maguire@oracle.com>
>
> Thanks, but...
>
> > > diff --git a/doc/userguide/reference/dtrace_providers_stapsdt.md b/doc/userguide/reference/dtrace_providers_stapsdt.md
> > > + STAP_PROBE3(myprovider, myprobe, argc, argv[0], 18);
> > > + if (myprovider_myprobe_semaphore)
> > > + printf("the probe is enabled\n");
> > > + else
> > > + printf("the probe is not enabled\n");
> > I found the example a bit confusing. I would have thought:
>
> (fwiw. I think it's cool you can check it anyhow, but yeah your example
> makes more sense.)
>
> > > +Notice that the instrumented source code includes the header file
> > > +`<sys/sdt.h>`. On Oracle Linux, this file is installed
> > > +by the RPM package `systemtap-sdt-devel`, but the package also
> > > +installs `/usr/bin/dtrace`. So be sure to have `/usr/sbin`
> > > +in front of `/usr/bin` in your path, or explicitly specify
> > > +`/usr/sbin/dtrace` whenever you want to use `dtrace`.
> > > +
> > Would be good to mention that a double underscore "__" gets converted to
> > a dash (-) in provider/probe names too.
>
> ... but what does this have to do with stapsdt? I thought that was a
> general DTrace thing that would not need to be called out specially here.
I agree - this is standard in DTrace so I don't think it needs to be pointed
out. Is it done that way in systemtap as well? If so, no need to mention it.
If systemtap does *not* do that, I would mention it here because that would be
a deviation from systemtap.
prev parent reply other threads:[~2025-11-19 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 4:30 [PATCH] doc: Add stapsdt provider documentation eugene.loh
2025-11-18 12:43 ` Alan Maguire
2025-11-19 0:15 ` Eugene Loh
2025-11-19 0:44 ` Kris Van Hees [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=aR0S+YpnXNaipnez@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=alan.maguire@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@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 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.