Linux DTrace development list
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: eugene.loh@oracle.com
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH 04/14] Track uprobe provider descriptions
Date: Tue, 4 Jun 2024 17:10:24 -0400	[thread overview]
Message-ID: <Zl+CwFHv6bSJTNHw@oracle.com> (raw)
In-Reply-To: <20240604181113.11505-5-eugene.loh@oracle.com>

On Tue, Jun 04, 2024 at 02:11:03PM -0400, eugene.loh--- via DTrace-devel wrote:
> From: Eugene Loh <eugene.loh@oracle.com>
> 
> A uprobe will have to decide which of its clauses to run for a
> given pid.  For now, keep the provider description for each clause.
> There are many shortcomings to the way this is done in this patch,
> but it is quick and dirty and helps us bootstrap real support.
> Clean this up later, probably turning it into a growable array.

This is the wrong way to look at it, I think.  The underlying concept is that
DTrace supports specifying probes that do not match anything yet (-Z).  Those
are called retained enablings and they can exist for more than just uprobes.
So this needs to be more generic.

We also shouldn't do this non-discriminately for all clauses all the time.
Obviously, when -Z is not used, there is no point in doing this because there
cannot be a match-after-start.  Even when -Z is specified, you might be able
to determine whether the probe specification for a probe matches perfectly
or whether it needs to be retained for match-after-start.

So, let's put some thought into designing this in the more generic case, so
that we can avoid going down a rabbit hole that gets tough to recover from.

(And whatever we store the retained enablings in probably should be added to
 dtrace_hdl_t after dt_enablings.)

> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
> ---
>  libdtrace/dt_cc.c   | 1 +
>  libdtrace/dt_impl.h | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/libdtrace/dt_cc.c b/libdtrace/dt_cc.c
> index d1ee3843..6bff7e0f 100644
> --- a/libdtrace/dt_cc.c
> +++ b/libdtrace/dt_cc.c
> @@ -215,6 +215,7 @@ dt_compile_one_clause(dtrace_hdl_t *dtp, dt_node_t *cnp, dt_node_t *pnp)
>  	 */
>  	dt_cg(yypcb, cnp);
>  	sdp->dtsd_clause = dt_clause_create(dtp, dt_as(yypcb));
> +	dtp->dt_uprovdescs[dtp->dt_clause_nextid - 1] = strdup(pnp->dn_desc->prv);
>  
>  	assert(yypcb->pcb_stmt == sdp);
>  	if (dtrace_stmt_add(yypcb->pcb_hdl, yypcb->pcb_prog, sdp) != 0)
> diff --git a/libdtrace/dt_impl.h b/libdtrace/dt_impl.h
> index 01313ff3..1bf79d80 100644
> --- a/libdtrace/dt_impl.h
> +++ b/libdtrace/dt_impl.h
> @@ -310,6 +310,7 @@ struct dtrace_hdl {
>  	dt_pcb_t *dt_pcb;	/* pointer to current parsing control block */
>  	ulong_t dt_gen;		/* compiler generation number */
>  	uint_t dt_clause_nextid; /* next ID to use for programs */
> +	char *dt_uprovdescs[256]; /* uprobe provider descriptor per clause... FIXME turn this into a growable array */
>  	dt_list_t dt_programs;	/* linked list of dtrace_prog_t's */
>  	dt_list_t dt_xlators;	/* linked list of dt_xlator_t's */
>  	dt_list_t dt_enablings;	/* list of (to be) enabled probes */
> -- 
> 2.18.4
> 
> 
> _______________________________________________
> DTrace-devel mailing list
> DTrace-devel@oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/dtrace-devel

  reply	other threads:[~2024-06-04 21:10 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 18:10 "proof of concept" for systemwide USDT eugene.loh
2024-06-04 18:11 ` [PATCH 01/14] Move comment closer to the code it describes eugene.loh
2024-06-04 18:21   ` [DTrace-devel] " Kris Van Hees
2024-06-04 18:11 ` [PATCH 02/14] Clean up prp/uprp variable names eugene.loh
2024-06-04 18:44   ` [DTrace-devel] " Kris Van Hees
2024-06-05 18:18     ` Eugene Loh
2024-06-04 18:11 ` [PATCH 03/14] Let USDT module names contain dots eugene.loh
2024-06-04 20:42   ` [DTrace-devel] " Kris Van Hees
2024-06-04 22:30     ` Eugene Loh
2024-06-07 18:48       ` Nick Alcock
2024-06-07 22:22         ` Eugene Loh
2024-06-04 18:11 ` [PATCH 04/14] Track uprobe provider descriptions eugene.loh
2024-06-04 21:10   ` Kris Van Hees [this message]
2024-06-07 21:40     ` [DTrace-devel] " Eugene Loh
2024-06-07 22:16       ` Kris Van Hees
2024-06-10 21:23         ` Eugene Loh
2024-06-10 21:31           ` Kris Van Hees
2024-06-04 18:11 ` [PATCH 05/14] Add a hook for a provider-specific "update" function eugene.loh
2024-06-04 21:38   ` [DTrace-devel] " Kris Van Hees
2024-06-10 22:14     ` Eugene Loh
2024-06-04 18:11 ` [PATCH 06/14] Add clauses to per-uprobe list eugene.loh
2024-06-04 18:11 ` [PATCH 07/14] Create the BPF uprobes map eugene.loh
2024-06-05  4:33   ` [DTrace-devel] " Kris Van Hees
2024-06-10 20:55     ` Eugene Loh
2024-06-04 18:11 ` [PATCH 08/14] Use uprobes map to call clauses conditionally eugene.loh
2024-06-04 18:11 ` [PATCH 09/14] Systemwide USDT WIP eugene.loh
2024-06-04 18:11 ` [PATCH 10/14] Fix the consumer's picture of the EPID eugene.loh
2024-06-04 18:11 ` [PATCH 11/14] Back out the previous patch eugene.loh
2024-06-04 18:11 ` [PATCH 12/14] Fix comments that hardwire DBUF_ offsets eugene.loh
2024-06-04 18:11 ` [PATCH 13/14] Clean up some comments eugene.loh
2024-06-04 18:11 ` [PATCH 14/14] Have the consumer get the PRID from the output buffer eugene.loh

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=Zl+CwFHv6bSJTNHw@oracle.com \
    --to=kris.van.hees@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox