From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Bristot de Oliveira <bristot@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] tracing/timerlat: Hotplug support for the user-space interface
Date: Tue, 3 Oct 2023 21:03:09 -0400 [thread overview]
Message-ID: <20231003210309.4335307d@gandalf.local.home> (raw)
In-Reply-To: <a1bbd57692c1a59458c4ee99999b7f83a29bc3c5.1695999408.git.bristot@kernel.org>
On Fri, 29 Sep 2023 17:02:46 +0200
Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
> The osnoise/per_cpu/CPU$/timerlat_fd is create for each possible
> CPU, but it might create confusion if the CPU is not online.
>
> Create the file only for online CPUs, also follow hotplug by
> creating and deleting as CPUs come and go.
>
> Fixes: e88ed227f639 ("tracing/timerlat: Add user-space interface")
Is this a fix that needs to go in now and Cc'd to stable? Or is this
something that can wait till the next merge window?
-- Steve
> Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
> ---
>
> Changes from V2:
> - Better split the code into the generic (per_cpu/cpu$)
> and timerlat (/timerlat_fd) specific function (Daniel)
> - Fixed a cpus_read_lock/unlock() usage (kbuild test)
> Link: https://lore.kernel.org/lkml/6b9a5f306e488bc77bf8521faeade420a0adf3e4.1695224204.git.bristot@kernel.org/
>
> Changes from V1:
> - Fix compilation issue when !HOTPLUG
> - Fix init interface | hotplug race
> Link: https://lore.kernel.org/lkml/b619d9fd08a3bb47018cf40afa95783844a3c1fd.1694789910.git.bristot@kernel.org/
>
> kernel/trace/trace_osnoise.c | 149 ++++++++++++++++++++++++++++-------
> 1 file changed, 121 insertions(+), 28 deletions(-)
>
>
next prev parent reply other threads:[~2023-10-04 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 15:02 [PATCH V3] tracing/timerlat: Hotplug support for the user-space interface Daniel Bristot de Oliveira
2023-10-04 1:03 ` Steven Rostedt [this message]
2023-10-04 10:02 ` Daniel Bristot de Oliveira
2023-10-04 12:17 ` Steven Rostedt
2023-10-04 12:20 ` Steven Rostedt
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=20231003210309.4335307d@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).