public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Thorsten Blum <thorsten.blum@toblux.com>
Subject: Re: [GIT PULL] ring-buffer: Updates for 6.11
Date: Tue, 16 Jul 2024 16:28:06 -0400	[thread overview]
Message-ID: <886acd97-e837-4bff-a8e2-26638525cab5@efficios.com> (raw)
In-Reply-To: <20240716161105.0aa6bfe1@rorschach.local.home>

On 2024-07-16 16:11, Steven Rostedt wrote:
> On Tue, 16 Jul 2024 16:05:26 -0400
> Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
> 
>> On 2024-07-16 15:51, Steven Rostedt wrote:
>>>
>>>
>>> Linus,
>>>
>>> tracing/ring-buffer: Have persistent buffer across reboots
>>
>> Hi Steven,
>>
>> Perhaps I'm missing something here, but we discussed previously that
>> you would document the fact that users of this feature are expected
>> to run the same kernel before/after reboot.
>>
>> Looking at this PR, I fail to find that documentation, or in fact
>> any documentation at all. Is this something that was overlooked ?
> 
> Hmm, was that for this code, or the one that used the reserved_mem
> change, which isn't in this pull request, as it depends on the code
> that is going through the mm tree.
> 
> Technically it can work with different kernels (I have even done that).
> But yeah, it isn't guaranteed to work in such cases. But that is just a
> documentation update.

If the documentation just ends up being in a different PR, I have no
objection.

Thanks,

Mathieu


-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com


  reply	other threads:[~2024-07-16 20:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 19:51 [GIT PULL] ring-buffer: Updates for 6.11 Steven Rostedt
2024-07-16 20:05 ` Mathieu Desnoyers
2024-07-16 20:11   ` Steven Rostedt
2024-07-16 20:28     ` Mathieu Desnoyers [this message]
2024-07-19 14:32   ` Steven Rostedt
2024-07-19 14:59     ` Mathieu Desnoyers
2024-07-19 16:19       ` Steven Rostedt
2024-07-19 18:05         ` Mathieu Desnoyers
2024-07-19 18:16           ` Steven Rostedt
2024-07-29 22:32 ` 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=886acd97-e837-4bff-a8e2-26638525cab5@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=thorsten.blum@toblux.com \
    --cc=torvalds@linux-foundation.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