From: Eugene Loh <eugene.loh@oracle.com>
To: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH v2] test: stack_fbt
Date: Wed, 20 Nov 2024 15:28:40 -0500 [thread overview]
Message-ID: <2aed49d4-d529-de2c-87ba-42873b3ecfda@oracle.com> (raw)
In-Reply-To: <Zz43EAAB87FOttWG@oracle.com>
On 11/20/24 14:22, Kris Van Hees wrote:
> On Thu, Nov 07, 2024 at 06:28:41PM -0500, eugene.loh--- via DTrace-devel wrote:
>> From: Eugene Loh <eugene.loh@oracle.com>
>>
>> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
> Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>
>
> ... with small changes as shown below.
>
>> diff --git a/test/unittest/stack/tst.stack_fbt.sh b/test/unittest/stack/tst.stack_fbt.sh
>> new file mode 100755
>> @@ -0,0 +1,122 @@
>> +#!/bin/bash
>> +#
>> +# This test verifies the nusdtprobes option.
> Surely this is a copy'n'paste error and should be removed?
Goodness. Yes. Good thing that at least one of us is reading this
stuff! Oops.
> Or rather, it
> should be replaced with a message that actually states what this test
> exercises/verifies?
>
> Shall I make it:
>
> Test the stack action with default stack depth and depth 3.
Thanks. Well put.
>> +
>> +dtrace=$1
>> +
>> +# Set up test directory.
>> +
>> +DIRNAME=$tmpdir/stack_fbt.$$.$RANDOM
>> +mkdir -p $DIRNAME
>> +cd $DIRNAME
>> +
>> +# Use DTrace to capture stack() at vfs_write:entry.
>> +
>> +$dtrace $dt_flags $nusdt -wqn '
> I assume $nusdt should not be used here.
Sigh. Right.
prev parent reply other threads:[~2024-11-20 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 23:28 [PATCH v2] test: stack_fbt eugene.loh
2024-11-20 19:22 ` [DTrace-devel] " Kris Van Hees
2024-11-20 19:38 ` Kris Van Hees
2024-11-20 20:39 ` Eugene Loh
2024-11-20 20:53 ` Kris Van Hees
2024-11-20 20:28 ` Eugene Loh [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=2aed49d4-d529-de2c-87ba-42873b3ecfda@oracle.com \
--to=eugene.loh@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
/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