[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250402102842.238a03f3@gandalf.local.home>
Date: Wed, 2 Apr 2025 10:28:42 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mike Rapoport <rppt@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, Linus
Torvalds <torvalds@...ux-foundation.org>, Masami Hiramatsu
<mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>, Mathieu
Desnoyers <mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Vincent Donnefort <vdonnefort@...gle.com>,
Vlastimil Babka <vbabka@...e.cz>, Jann Horn <jannh@...gle.com>
Subject: Re: [PATCH v5 2/4] tracing: Have reserve_mem use phys_to_virt() and
separate from memmap buffer
On Wed, 2 Apr 2025 12:24:12 +0300
Mike Rapoport <rppt@...nel.org> wrote:
> > The reserve_mem kernel command line option may pass back a physical
> > address, but the memory is still part of the normal memory just like
> > using memblock_reserve() would be. This means that the physical memory
>
> ... using memblock_alloc() would be
Heh, I looked for examples of code that used free_reserved_area() and found
initramfs.c which uses memblock_reserve(), which is why I picked that.
I'll update.
Thanks for reviewing Mike!
-- Steve
Powered by blists - more mailing lists