From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH v4] trace: print alloca pointers as actual pointer values
Date: Wed, 17 Sep 2025 16:03:33 +0100 [thread overview]
Message-ID: <87h5x1p1dm.fsf@esperi.org.uk> (raw)
In-Reply-To: <SJ0PR10MB56721752C4BEB7A65080065EC214A@SJ0PR10MB5672.namprd10.prod.outlook.com> (Kris Van Hees's message of "Tue, 16 Sep 2025 14:26:45 -0400")
On 16 Sep 2025, Kris Van Hees verbalised:
> Because alloca pointers are stored internally as offsets into the
> scratchmem area, they were printed as small integers. They are
> now printed as actual pointer values into kernel space.
>
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
So... the change is to generate real pointers for children of alloca
nodes too, and scalarize more aggressively? I don't really see what the
second part has to do with this change (and more specifically why it
didn't cause problems before now).
--
NULL && (void)
next prev parent reply other threads:[~2025-09-17 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 18:26 [PATCH v4] trace: print alloca pointers as actual pointer values Kris Van Hees
2025-09-16 22:53 ` Eugene Loh
2025-09-17 15:03 ` Nick Alcock [this message]
2025-09-17 15:29 ` Kris Van Hees
2025-09-18 13:01 ` Nick Alcock
2025-09-18 14:45 ` 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=87h5x1p1dm.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 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.