From: Nick Alcock <nick.alcock@oracle.com>
To: "eugene.loh--- via DTrace-devel" <dtrace-devel@oss.oracle.com>
Cc: dtrace@lists.linux.dev, eugene.loh@oracle.com
Subject: Re: [DTrace-devel] [PATCH 3/3] test: Mimic dtrace arithmetic more closely for avg/stddev
Date: Wed, 16 Jul 2025 14:22:53 +0100 [thread overview]
Message-ID: <87ms94mfrm.fsf@esperi.org.uk> (raw)
In-Reply-To: <20250501182252.27772-3-eugene.loh@oracle.com> (eugene loh's message of "Thu, 1 May 2025 14:22:52 -0400")
On 1 May 2025, eugene loh stated:
> From: Eugene Loh <eugene.loh@oracle.com>
>
> The multicpus test checks that data from multiple CPUs is aggregated
> properly. Operations like avg() and stddev() require division.
> DTrace uses integer division, while awk does not.
Oops!
> for example, CPUs are not numbered consecutively. More typically,
> there may be a problem that the profile probe is not firing on every
> expected CPU. So a test failure probably was a sign of a problem,
> but that's a different problem, one beyond the scope of this test.
... is there anything else that tests for those other problems?
> Signed-off-by: Eugene Loh <eugene.loh@oracle.com>
Reviewed-by: Nick Alcock <nick.alcock@oracle.com>
next prev parent reply other threads:[~2025-07-16 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 18:22 [PATCH 1/3] Cache per-CPU agg map IDs eugene.loh
2025-05-01 18:22 ` [PATCH 2/3] test: Convert tick-* probes to ioctl:entry for tst.trunc[quant].d eugene.loh
2025-07-16 13:21 ` Nick Alcock
2025-05-01 18:22 ` [PATCH 3/3] test: Mimic dtrace arithmetic more closely for avg/stddev eugene.loh
2025-07-16 13:22 ` Nick Alcock [this message]
2025-07-16 19:51 ` [DTrace-devel] " Eugene Loh
2025-07-16 13:20 ` [DTrace-devel] [PATCH 1/3] Cache per-CPU agg map IDs Nick Alcock
2025-07-16 18:42 ` Eugene Loh
2025-07-16 19:10 ` Kris Van Hees
2025-07-16 20:05 ` 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=87ms94mfrm.fsf@esperi.org.uk \
--to=nick.alcock@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