From: Kris Van Hees <kris.van.hees@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev,
DTrace development list <dtrace-devel@oss.oracle.com>
Subject: Re: Issue with stack) on 6.x kernels
Date: Wed, 1 May 2024 09:58:38 -0400 [thread overview]
Message-ID: <ZjJKjlD8EvNnmbhl@oracle.com> (raw)
In-Reply-To: <ZjGfUr/Zj/2taTAW@oracle.com>
On Tue, Apr 30, 2024 at 09:48:02PM -0400, Kris Van Hees wrote:
> Newer 6.x kernels (I tried 6.5.0 and 6.8.0) seem to behave differently for
> stack() than e.g. 5,15,0, Test test/unittest/aggs/tst.stack.d FAILs on those
> 6.x kernels whereas it passes on 5.15.0. I am not sure yet why there is a
> difference, but Eugene, perhaps you can take a look into this?
>
> Kris
Here is an example:
$ sudo ./build/run-dtrace -s test/unittest/aggs/tst.stack.d
[sudo] password for kvanhees:
0xffffffffc0129e86
0xffffffffc0129e86
0xffffffffc0129e86
0xffffffffc0130250
0xffffffffc0130250
0xffffffffc012b2bb
0xffffffffc012b83c
vmlinux`schedule+0x9
The strange thing is that it actually does give good results at times.
So I am not sure what is going on.
next prev parent reply other threads:[~2024-05-01 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 1:48 Issue with stack) on 6.x kernels Kris Van Hees
2024-05-01 13:58 ` Kris Van Hees [this message]
2024-05-01 17:15 ` [DTrace-devel] " Alan Maguire
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=ZjJKjlD8EvNnmbhl@oracle.com \
--to=kris.van.hees@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
/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