From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3 1/2] mm/memblock: Add reserved memory release function
Date: Tue, 18 Feb 2025 22:06:29 +0900 [thread overview]
Message-ID: <20250218220629.6a352d70e0350b01e662d782@kernel.org> (raw)
In-Reply-To: <Z7RwWyD67BxWPnK8@kernel.org>
On Tue, 18 Feb 2025 13:34:51 +0200
Mike Rapoport <rppt@kernel.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@kernel.org>
next prev parent reply other threads:[~2025-02-18 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 14:46 [PATCH v3 0/2] tracing: Make persistent ring buffer freeable Masami Hiramatsu (Google)
2025-02-11 14:47 ` [PATCH v3 1/2] mm/memblock: Add reserved memory release function Masami Hiramatsu (Google)
2025-02-11 17:52 ` Steven Rostedt
2025-02-11 23:39 ` Masami Hiramatsu
2025-02-18 7:24 ` Mike Rapoport
2025-02-18 8:42 ` Masami Hiramatsu
2025-02-18 9:47 ` Mike Rapoport
2025-02-18 11:34 ` Mike Rapoport
2025-02-18 13:06 ` Masami Hiramatsu [this message]
2025-02-11 14:47 ` [PATCH v3 2/2] tracing: Freeable reserved ring buffer Masami Hiramatsu (Google)
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=20250218220629.6a352d70e0350b01e662d782@kernel.org \
--to=mhiramat@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.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