From: Nam Cao <namcao@linutronix.de>
To: Gabriele Monaco <gmonaco@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] verification/rvgen/ltl: Support per-cpu monitor generation
Date: Fri, 08 Aug 2025 07:12:16 +0200 [thread overview]
Message-ID: <87o6sqpfbj.fsf@yellow.woof> (raw)
In-Reply-To: <6754c61d60fc161963d0625a4b647a241b363fc5.camel@redhat.com>
Gabriele Monaco <gmonaco@redhat.com> writes:
> I get you're trying to be more type-agnostic, but I believe this
> /online/ is a bit imprecise, unless you register a hotplug handler and
> just initialise the online CPUs (much of an overkill I'd say).
> What about something like "this is false if the monitor exists already
> before the monitor is enabled"
Sorry, after re-reading this one day later, I am still not sure why you
says "online" is imprecise. Due to hotplug, CPUs can become online and
offline.
The current implementation ignore hotplug and initialize all possible
CPUs as if they are all oneline. But if hotplug becomes important in the
future, I may add a CPU hotplug handler.
> Other than that it looks good to me.
>
> Reviewed-by: Gabriele Monaco <gmonaco@redhat.com>
Thanks!
Nam
next prev parent reply other threads:[~2025-08-08 5:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 8:01 [PATCH v2 0/5] rv: LTL per-cpu monitor type and real-time scheduling monitor Nam Cao
2025-08-06 8:01 ` [PATCH v2 1/5] rv/ltl: Prepare for other monitor types Nam Cao
2025-08-06 8:01 ` [PATCH v2 2/5] rv/ltl: Support per-cpu monitors Nam Cao
2025-08-07 13:28 ` Gabriele Monaco
2025-08-06 8:01 ` [PATCH v2 3/5] verification/rvgen/ltl: Support per-cpu monitor generation Nam Cao
2025-08-07 13:06 ` Gabriele Monaco
2025-08-08 5:12 ` Nam Cao [this message]
2025-08-08 6:21 ` Gabriele Monaco
2025-08-08 6:30 ` Nam Cao
2025-08-06 8:01 ` [PATCH v2 4/5] sched: Add task enqueue/dequeue trace points Nam Cao
2025-08-15 13:40 ` Peter Zijlstra
2025-08-15 13:52 ` Peter Zijlstra
2025-08-21 7:05 ` Nam Cao
2025-08-21 8:43 ` K Prateek Nayak
2025-08-19 7:49 ` Nam Cao
2025-08-19 8:24 ` Peter Zijlstra
2025-08-06 8:01 ` [PATCH v2 5/5] rv: Add rts monitor Nam Cao
2025-08-06 20:28 ` kernel test robot
2025-08-07 13:33 ` Gabriele Monaco
2025-08-08 5:13 ` Nam Cao
2025-08-07 14:34 ` Gabriele Monaco
2025-08-08 5:29 ` Nam Cao
2025-08-08 7:30 ` Gabriele Monaco
2025-08-15 13:48 ` Peter Zijlstra
2025-08-19 7:54 ` Nam Cao
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=87o6sqpfbj.fsf@yellow.woof \
--to=namcao@linutronix.de \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/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.