All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace-devel@oss.oracle.com, dtrace@lists.linux.dev
Subject: Re: [DTrace-devel] [PATCH] test: add -l and -lv tests for stapsdt probes
Date: Wed, 06 Aug 2025 17:57:28 +0100	[thread overview]
Message-ID: <87jz3gl75z.fsf@esperi.org.uk> (raw)
In-Reply-To: <SJ0PR10MB56723A5B7174C2DF77C01DC2C22DA@SJ0PR10MB5672.namprd10.prod.outlook.com> (Kris Van Hees via DTrace-devel's message of "Wed, 06 Aug 2025 12:04:56 -0400")

On 6 Aug 2025, Kris Van Hees via DTrace-devel stated:

> The stapsdt support in DTrace provides limited support for argument data
> for probes.  The number of arguments passed to a probe and their native
> type (signed or unsigned int of size 1, 2, 4, or 8 bytes) is discoverable.
>
> Signed-off-by: Kris Van Hees
> <kris.van.hees@oracle.com>

Bit of a linefeed there. ;)

Bit annoying there's so much repetition, but it's really not worth
optimizing that, and it's no worse than any of the others in this area.

Reviewed-by: Nick Alcock <nick.alcock@oracle.com>

-- 
NULL && (void)

      reply	other threads:[~2025-08-06 16:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-06 16:04 [PATCH] test: add -l and -lv tests for stapsdt probes Kris Van Hees
2025-08-06 16:57 ` Nick Alcock [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=87jz3gl75z.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=kris.van.hees@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.