From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees via DTrace-devel <dtrace-devel@oss.oracle.com>
Cc: dtrace@lists.linux.dev, Kris Van Hees <kris.van.hees@oracle.com>
Subject: Re: [DTrace-devel] [PATCH 1/2] dlib: remove obsolete dt_dlib_add_probe_var()
Date: Fri, 21 Mar 2025 15:04:55 +0000 [thread overview]
Message-ID: <87msde4e7c.fsf@esperi.org.uk> (raw)
In-Reply-To: <834ff39378a30c154da54c67f4093dde.kris.van.hees@oracle.com> (Kris Van Hees via DTrace-devel's message of "Fri, 21 Mar 2025 10:42:21 -0400")
On 21 Mar 2025, Kris Van Hees via DTrace-devel outgrape:
> The dt_dlib_add_probe_var() function was added to allow for relcoation
> processing filling in probe ids for dependent probes, but since the
> probe ids are known at code generation time, there is no need for this.
I guess this is removing a relocation/fixup which was always the
identity transformation (prp->desc->id being reset to itself at reloc
resolution time).
If so...
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
--
NULL && (void)
prev parent reply other threads:[~2025-03-21 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 14:42 [PATCH 1/2] dlib: remove obsolete dt_dlib_add_probe_var() Kris Van Hees
2025-03-21 15:04 ` 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=87msde4e7c.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox