From: Sam James <sam@gentoo.org>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: "eugene.loh--- via DTrace-devel" <dtrace-devel@oss.oracle.com>,
dtrace@lists.linux.dev
Subject: Re: [DTrace-devel] [PATCH 17/19] test: Add a pid-USDT test
Date: Fri, 04 Oct 2024 06:51:43 +0100 [thread overview]
Message-ID: <87h69ss9e8.fsf@gentoo.org> (raw)
In-Reply-To: <ad5e0e40-1ba7-df9c-71a6-1008c9897694@oracle.com> (Eugene Loh's message of "Fri, 4 Oct 2024 00:49:25 -0400")
Eugene Loh <eugene.loh@oracle.com> writes:
> On 8/29/24 16:32, Sam James wrote:
>> "eugene.loh--- via DTrace-devel" <dtrace-devel@oss.oracle.com> writes:
>>
>>> From: Eugene Loh <eugene.loh@oracle.com>
>>>
>>> This checks that pid entry, pid return, pid offset, USDT, and USDT
>>> is-enabled probes can all coexist. Specifically, pid offset probes
>>> can sit on the same PCs as pid entry, USDT, and USDT is-enabled
>>> probes.
>>>
>>> Note that PCs for pid return probes are apparently in the caller
>>> function. I guess that's due to using uretprobe. I'm not convinced
>>> yet that that isn't a bug. It isn't what Solaris did.
>>>
>>> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
>>> ---
>>> test/unittest/usdt/tst.pidprobes.r | 1 +
>>> test/unittest/usdt/tst.pidprobes.sh | 243 ++++++++++++++++++++++++++++
>>> 2 files changed, 244 insertions(+)
>>> create mode 100644 test/unittest/usdt/tst.pidprobes.r
>>> create mode 100755 test/unittest/usdt/tst.pidprobes.sh
>>>
>>> diff --git a/test/unittest/usdt/tst.pidprobes.r b/test/unittest/usdt/tst.pidprobes.r
>>> new file mode 100644
>>> index 00000000..2e9ba477
>>> --- /dev/null
>>> +++ b/test/unittest/usdt/tst.pidprobes.r
>>> @@ -0,0 +1 @@
>>> +success
>>> diff --git a/test/unittest/usdt/tst.pidprobes.sh b/test/unittest/usdt/tst.pidprobes.sh
>>> new file mode 100755
>>> index 00000000..7eadb9b7
>>> --- /dev/null
>>> +++ b/test/unittest/usdt/tst.pidprobes.sh
>>> @@ -0,0 +1,243 @@
>>> +#!/bin/bash
>>> +#
>>> +# Oracle Linux DTrace.
>>> +# Copyright (c) 2024, Oracle and/or its affiliates. All rights reserved.
>>> +# Licensed under the Universal Permissive License v 1.0 as shown at
>>> +# http://oss.oracle.com/licenses/upl.
>>> +#
>>> +# This test verifies that USDT and pid probes can share underlying probes.
>>> +
>>> +dtrace=$1
>>> +
>>> +# Set up test directory.
>>> +
>>> +DIRNAME=$tmpdir/pidprobes.$$.$RANDOM
>>> +mkdir -p $DIRNAME
>>> +cd $DIRNAME
>>> +
>> Let's do mktemp -d?
>
> Thanks. On the other hand, that sequence is very common in the test
> suite. Maybe there should be a massive conversion to mktemp if we
> want to go that route.
>
>>> [...]
Sure, can do. I've got some others I want to get in first.
next prev parent reply other threads:[~2024-10-04 5:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 5:25 [PATCH 01/19] Change probes from having lists of clauses to lists of stmts eugene.loh
2024-08-29 5:25 ` [PATCH 02/19] Add a hook for a provider-specific "update" function eugene.loh
2024-08-29 5:25 ` [PATCH 03/19] Widen the EPID to include the PRID eugene.loh
2024-08-29 20:28 ` [DTrace-devel] " Sam James
2024-08-29 20:38 ` Kris Van Hees
2024-08-29 5:25 ` [PATCH 04/19] Eliminate dt_pdesc eugene.loh
2024-09-03 17:47 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 05/19] Add flag to dt_pid_create_probes() eugene.loh
2024-09-18 20:33 ` Kris Van Hees
2024-09-24 20:24 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 06/19] Allow for USDT wildcards eugene.loh
2024-09-17 17:34 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 07/19] Create the BPF usdt_prids map eugene.loh
2024-08-29 5:25 ` [PATCH 08/19] Support multiple overlying probes in the uprobe trampoline eugene.loh
2024-10-24 2:42 ` Kris Van Hees
2024-10-24 13:52 ` [DTrace-devel] " Kris Van Hees
2024-10-24 23:30 ` Eugene Loh
2024-10-25 0:14 ` Kris Van Hees
2024-08-29 5:25 ` [PATCH 09/19] Use usdt_prids map to call clauses conditionally for USDT probes eugene.loh
2024-08-29 5:25 ` [PATCH 10/19] Remove the is-enabled provider eugene.loh
2024-10-24 15:18 ` Kris Van Hees
2024-10-26 1:13 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 11/19] Support USDT wildcard provider descriptions eugene.loh
2024-08-29 5:25 ` [PATCH 12/19] Increase size of BPF probes map eugene.loh
2024-08-29 20:30 ` [DTrace-devel] " Sam James
2024-10-08 22:15 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 13/19] Get rid of relocatable EPID, dt_nextepid, and dt_ddesc[] eugene.loh
2024-09-03 17:49 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 14/19] Ignore clauses in USDT trampoline if we know they are impossible eugene.loh
2024-08-29 5:25 ` [PATCH 15/19] Ignore clauses: some clauses are impossible regardless of uprp eugene.loh
2024-08-29 20:31 ` [DTrace-devel] " Sam James
2024-09-03 19:54 ` Eugene Loh
2024-09-03 20:10 ` Kris Van Hees
2024-08-29 5:25 ` [PATCH 16/19] Ignore clauses: use underlying probe's function information eugene.loh
2024-10-24 16:52 ` Kris Van Hees
2024-08-29 5:25 ` [PATCH 17/19] test: Add a pid-USDT test eugene.loh
2024-08-29 20:32 ` [DTrace-devel] " Sam James
2024-10-04 4:49 ` Eugene Loh
2024-10-04 5:51 ` Sam James [this message]
2024-08-29 5:25 ` [PATCH 18/19] test: Add a lazy USDT test eugene.loh
2024-09-28 2:11 ` Eugene Loh
2024-08-29 5:25 ` [PATCH 19/19] test: Add another USDT open/close test eugene.loh
2024-10-24 17:01 ` Kris Van Hees
2024-09-18 14:18 ` [PATCH 01/19] Change probes from having lists of clauses to lists of stmts Kris Van Hees
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=87h69ss9e8.fsf@gentoo.org \
--to=sam@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox