From: Nix <nix@esperi.org.uk>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 03/20] ctf: give shared kernel types a synthetic module owner
Date: Fri, 06 Nov 2026 12:40:35 +0000 [thread overview]
Message-ID: <874iduuo8s.fsf@esperi.org.uk> (raw)
In-Reply-To: <307cf8d7cbf63295d5448222112686f5@oracle.com>
On 30 Oct 2026, Kris Van Hees stated:
> Store the shared dictionary in shared_ctf->dm_ctfp and remove dt_shared_ctf
> from the DTrace handle.
This is effectively reversing a change I made ten years ago :P because
having it as a separate module was too problematic given that it didn't
correspond to a *real* module any more (in particular, we don't want
people to be able to look it up by name with `, etc.)
As far as I could tell, all the advantages of being a module were
actually disadvantages for the shared dict, and no advantages were left.
It's not actually a module, and none of the things you can do to modules
should be doable on the shared CTF, and it didn't make the code simpler
to conflate the two either.
So... what benefits does this bring?
--
NULL && (void)
next prev parent reply other threads:[~2026-11-06 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:36 [PATCH 03/20] ctf: give shared kernel types a synthetic module owner Kris Van Hees
2026-11-06 12:40 ` Nix [this message]
2026-11-06 21:13 ` 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=874iduuo8s.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.