From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Mel Gorman <mgorman@suse.de>, Tejun Heo <tj@kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: Re: [GIT PULL] Scheduler updates for v6.17
Date: Sun, 3 Aug 2025 15:36:07 -0400 [thread overview]
Message-ID: <20250803153607.2bf1b32e@gandalf.local.home> (raw)
In-Reply-To: <20250803152411.7fd91614@gandalf.local.home>
On Sun, 3 Aug 2025 15:24:11 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> If your machine doesn't clear the memory on reboot, you could use the
> persistent ring buffer too:
>
> Adding to the kernel command line:
>
> reserve_mem=20M:12M:trace trace_instance=boot_mapped@trace
You can know if this works by adding the above to the kernel command line
then boot once. Do a reboot, and if the second boot dmesg has something
like:
Ring buffer meta [0] is from previous boot!
You're good to go. But if it has:
Ring buffer boot meta[0] mismatch of magic or struct size
Then it likely will not work.
-- Steve
next prev parent reply other threads:[~2025-08-03 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 6:48 Ingo Molnar
2025-07-30 3:39 ` pr-tracker-bot
2025-07-31 3:31 ` Linus Torvalds
2025-08-02 18:43 ` Linus Torvalds
2025-08-02 19:46 ` Steven Rostedt
2025-08-03 19:10 ` Linus Torvalds
2025-08-03 19:24 ` Steven Rostedt
2025-08-03 19:36 ` Steven Rostedt [this message]
2025-08-03 17:50 ` Jeff Johnson
2025-08-04 16:50 ` Steven Rostedt
2025-08-04 17:52 ` Linus Torvalds
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=20250803153607.2bf1b32e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®