[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20250218220629.6a352d70e0350b01e662d782@kernel.org>
Date: Tue, 18 Feb 2025 22:06:29 +0900
From: Masami Hiramatsu (Google) <mhiramat@...nel.org>
To: Mike Rapoport <rppt@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>
Subject: Re: [PATCH v3 1/2] mm/memblock: Add reserved memory release
function
On Tue, 18 Feb 2025 13:34:51 +0200
Mike Rapoport <rppt@...nel.org> wrote:
> On Tue, Feb 18, 2025 at 11:47:11AM +0200, Mike Rapoport wrote:
> > On Tue, Feb 18, 2025 at 05:42:57PM +0900, Masami Hiramatsu wrote:
> > > Hi Mike,
> > >
> > >
> > > Thanks! but I can not use free_reserved_area() here because it uses
> > > virt_to_page(). Here we only know the physical address in the map.
> > > I think we can use free_reserved_page() instead. Is that OK?
> >
> > For reserve_mem ranges virt_to_phys() will work, they are allocated from the
>
> I meant phys_to_virt() of course :)
Ah, I got it :). Let me update it.
Thanks!
>
> > memory that is covered by the direct map.
>
> --
> Sincerely yours,
> Mike.
--
Masami Hiramatsu (Google) <mhiramat@...nel.org>
Powered by blists - more mailing lists