From: Steven Rostedt <rostedt@goodmis.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
linux-trace-kernel@vger.kernel.org, maz@kernel.org,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix trace remotes read with an offline CPU
Date: Wed, 1 Apr 2026 10:31:59 -0400 [thread overview]
Message-ID: <20260401103159.747ae168@gandalf.local.home> (raw)
In-Reply-To: <20260401025003.3258729-1-vdonnefort@google.com>
On Wed, 1 Apr 2026 03:50:01 +0100
Vincent Donnefort <vdonnefort@google.com> wrote:
> This small series is fixing non-consuming read of a trace remote when the
> trace_buffer is created after a CPU is offline.
>
> It also extends hotplug testing coverage to include this test case.
>
> I have based this series on top of kvmarm/next which contains the hypervisor
> tracing patches.
>
> Vincent Donnefort (2):
> tracing: Non-consuming read for trace remotes with an offline CPU
> tracing: selftests: Extend hotplug testing for trace remotes
This looks fine to me. Since they only affect the new remote code and will
not conflict with anything I'm doing, they can go on top of the KVM patches
in the arm64 tree.
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
for the series.
Thanks,
-- Steve
next prev parent reply other threads:[~2026-04-01 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 2:50 [PATCH 0/2] Fix trace remotes read with an offline CPU Vincent Donnefort
2026-04-01 2:50 ` [PATCH 1/2] tracing: Non-consuming read for trace remotes " Vincent Donnefort
2026-04-01 2:50 ` [PATCH 2/2] tracing: selftests: Extend hotplug testing for trace remotes Vincent Donnefort
2026-04-01 14:31 ` Steven Rostedt [this message]
2026-04-01 15:08 ` [PATCH 0/2] Fix trace remotes read with an offline CPU Marc Zyngier
2026-04-01 15:16 ` 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=20260401103159.747ae168@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=maz@kernel.org \
--cc=mhiramat@kernel.org \
--cc=vdonnefort@google.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