public inbox for dtrace@lists.linux.dev
 help / color / mirror / Atom feed
From: Eugene Loh <eugene.loh@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [DTrace-devel] [PATCH] bpf: allocate the buffers BPF map to fit highest CPU id
Date: Fri, 12 Dec 2025 14:16:04 -0500	[thread overview]
Message-ID: <79ffaee2-6f7f-4c08-74b6-866fec007c99@oracle.com> (raw)
In-Reply-To: <aTupZ395993j8Wu4@oracle.com>

This patch is clearly a step in the right direction (fixes a bug), and I 
do not want perfection to be the enemy of good here. So, if you're 
willing to add some remarks to the commit message that describe some of 
the issues we're discussing here -- and, quite frankly, even if you're 
not -- I'm good with this patch.

And...

On 12/12/25 00:34, Kris Van Hees wrote:

> On Fri, Dec 12, 2025 at 12:14:20AM -0500, Eugene Loh wrote:
>> On 12/11/25 23:36, Kris Van Hees wrote:
>>> I am not entirely sure we *can* test this properly specialized configs.  The
>>> problem came to light on a configuration that conveniently demonstrated the
>>> problem because of a large gap of unavailable CPUs (0-127 possible, but only
>>> 0-7,100-127 were online).  Because in that situation, it is quite likely that
>>> the CPU on which the events we are interested in occur falls beyond the end
>>> of the buffers BPF map.
>> I think at some level we agree that it is possible to test but that it can
>> be hard to do so (automated, regular, etc.).
> Yes, but quite difficult and very specialized.

Difficult?  It's outside of our normal routine, but we can get access to 
such systems and we could devise tests.  The problem is not that such 
testing is more challenging than other things we have to do, but only 
that we have too many other things to do.

Specialized?  The distinction between on-line and possible CPUs shows up 
in a number of places in the code.

Anyhow, yeah, let's try our best *and* not beat ourselves up on this one.

And, of course, thanks for fixing this problem.

      reply	other threads:[~2025-12-12 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 22:22 [PATCH] bpf: allocate the buffers BPF map to fit highest CPU id Kris Van Hees
2025-12-11 23:16 ` [DTrace-devel] " Eugene Loh
2025-12-12  4:36   ` Kris Van Hees
2025-12-12  5:14     ` Eugene Loh
2025-12-12  5:34       ` Kris Van Hees
2025-12-12 19:16         ` Eugene Loh [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=79ffaee2-6f7f-4c08-74b6-866fec007c99@oracle.com \
    --to=eugene.loh@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