[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250803153607.2bf1b32e@gandalf.local.home>
Date: Sun, 3 Aug 2025 15:36:07 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org, Peter
Zijlstra <peterz@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, Juri
Lelli <juri.lelli@...hat.com>, Vincent Guittot
<vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>,
Mel Gorman <mgorman@...e.de>, Tejun Heo <tj@...nel.org>, Valentin Schneider
<vschneid@...hat.com>, Shrikanth Hegde <sshegde@...ux.ibm.com>
Subject: Re: [GIT PULL] Scheduler updates for v6.17
On Sun, 3 Aug 2025 15:24:11 -0400
Steven Rostedt <rostedt@...dmis.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@...ce
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
Powered by blists - more mailing lists