From: Kris Van Hees <kris.van.hees@oracle.com>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 13/38] Hide dtrace_actdesc_t until it is needed
Date: Thu, 18 Jul 2024 17:28:12 -0400 [thread overview]
Message-ID: <ZpmI7O/iYc9xaWz2@oracle.com> (raw)
In-Reply-To: <4518310b-abf9-2e8b-e2de-8ad358adab00@oracle.com>
On Thu, Jul 18, 2024 at 05:06:00PM -0400, Eugene Loh wrote:
> On 7/18/24 16:02, Kris Van Hees wrote:
>
> > On Thu, Jun 27, 2024 at 01:34:30AM -0400, eugene.loh@oracle.com wrote:
> > > From: Eugene Loh <eugene.loh@oracle.com>
> > >
> > > Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
> > I think you should just get rid of it. Worst case, we can always revert the
> > patch. But this type is only used in code that we do not plan to revive since
> > we no longer do DOF the same way as the older version. Even if we were to
> > re-implement the functionality to save compiled probe programs to file, it
> > would look very different and certainly not be action-based but rather BPF
> > code based.
>
> It would seem to me that the declaration (this patch) and the code that uses
> it should go together. So, are you saying the inoperative code that
> references this declaration should also be removed? It would seem funny to
> me to remove the declaration (this patch) while (admittedly inoperative)
> code that references it is left alone.
That is a valid point - in which case I think that (for this patch series),
this is not a relevant patch and thus should be dropped. Instead, a work item
ought to be added to either get rid of (most of) dt_dof.c and related code, or
to actually implement it in a way that makes sense (i.e. do something useful
and be in line with the new implementation of DTrace).
> >
> > > ---
> > > include/dtrace/enabling.h | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/include/dtrace/enabling.h b/include/dtrace/enabling.h
> > > index f1ec444c..2562c87b 100644
> > > --- a/include/dtrace/enabling.h
> > > +++ b/include/dtrace/enabling.h
> > > @@ -43,6 +43,8 @@ typedef struct dtrace_probedesc {
> > > const char *prb; /* probe name */
> > > } dtrace_probedesc_t;
> > > +#ifdef FIXME
> > > +This type is used only in #ifdef FIXME code.
> > > typedef struct dtrace_actdesc {
> > > struct dtrace_difo *dtad_difo; /* pointer to DIF object */
> > > dtrace_actkind_t dtad_kind; /* kind of action */
> > > @@ -50,6 +52,7 @@ typedef struct dtrace_actdesc {
> > > uint64_t dtad_arg; /* action argument */
> > > uint64_t dtad_uarg; /* user argument */
> > > } dtrace_actdesc_t;
> > > +#endif
> > > typedef struct dtrace_ecbdesc {
> > > dtrace_probedesc_t dted_probe; /* probe description */
> > > --
> > > 2.18.4
> > >
next prev parent reply other threads:[~2024-07-18 21:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 5:34 eugene.loh
2024-06-27 5:34 ` [PATCH 01/38] Move comment closer to the code it describes eugene.loh
2024-06-27 5:34 ` [PATCH 02/38] Move dt_spec_buf_data_t and dt_spec_buf_t into dt_consume.c eugene.loh
2024-07-18 6:54 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 03/38] Get rid of apparently orphaned status[2] eugene.loh
2024-07-18 6:59 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 04/38] Get rid of apparently orphaned bufdesc stuff eugene.loh
2024-07-18 18:28 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 05/38] Get rid of unneeded enabling_defines.h eugene.loh
2024-07-18 18:35 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 06/38] Get rid of unused dtrace_repldesc_t eugene.loh
2024-07-18 18:34 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 07/38] Clean up prp/pprp/uprp variable names eugene.loh
2024-07-18 18:48 ` Kris Van Hees
2024-07-18 20:19 ` Eugene Loh
2024-06-27 5:34 ` [PATCH 08/38] Fix comment in dt_probe.c eugene.loh
2024-07-18 18:49 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 09/38] Fix comments that hardwire DBUF_ offsets eugene.loh
2024-07-18 19:04 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 10/38] Fix comments in dt_cg.c eugene.loh
2024-07-18 19:28 ` Kris Van Hees
2024-07-18 20:29 ` Eugene Loh
2024-06-27 5:34 ` [PATCH 11/38] USDT module names may contain dots; but forbid "." and ".." names eugene.loh
2024-07-18 19:23 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 12/38] USDT module names may contain dots; remove incorrect check eugene.loh
2024-07-18 19:24 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 13/38] Hide dtrace_actdesc_t until it is needed eugene.loh
2024-07-18 20:02 ` Kris Van Hees
2024-07-18 21:06 ` Eugene Loh
2024-07-18 21:28 ` Kris Van Hees [this message]
2024-07-18 22:36 ` Eugene Loh
2024-06-27 5:34 ` [PATCH 14/38] Remove orphaned dtrace_hdl_t component dt_maxformat eugene.loh
2024-07-18 20:03 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 15/38] Remove orphaned dtrace_hdl_t component dt_prov_usdt eugene.loh
2024-07-18 20:03 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 16/38] Move dt_probe_clause_t to be available outside of dt_probe.c eugene.loh
2024-07-18 20:19 ` Kris Van Hees
2024-06-27 5:34 ` [PATCH 17/38] Add a provider-specific probe_add_clause handle eugene.loh
2024-07-18 20:49 ` Kris Van Hees
2024-07-19 4:00 ` Eugene Loh
2024-06-27 5:34 ` [PATCH 18/38] Add a provider-specific probe_add_clause for underlying probes eugene.loh
2024-07-18 20:50 ` Kris Van Hees
2024-07-19 4:00 ` 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=ZpmI7O/iYc9xaWz2@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