From: Jason Gunthorpe <jgg@nvidia.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Jason Miu <jasonmiu@google.com>, Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Changyuan Lyu <changyuanl@google.com>,
David Matlack <dmatlack@google.com>,
David Rientjes <rientjes@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 1/2] kho: Adopt radix tree for preserved memory tracking
Date: Tue, 13 Jan 2026 09:05:26 -0400 [thread overview]
Message-ID: <20260113130526.GE812923@nvidia.com> (raw)
In-Reply-To: <aWYt0gBHxDCKqj9Q@kernel.org>
On Tue, Jan 13, 2026 at 01:34:42PM +0200, Mike Rapoport wrote:
> For example mshv intends to use kho_radix_tree to track the hypervisor
> memory and there unpreserving will be a part of the normal flow.
I do not think this is a good idea.
Nothing should be touching KHO until a kexec sequence is started. KHO
calls should WARN_ON prior to this point. If a kexec sequence aborts
then the entire radix tree should be discarded and it should go back
to WARN_ON'ing KHO calls.
Jason
next prev parent reply other threads:[~2026-01-13 13:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 0:11 [PATCH v4 0/2] Make KHO Stateless Jason Miu
2026-01-09 0:11 ` [PATCH v4 1/2] kho: Adopt radix tree for preserved memory tracking Jason Miu
2026-01-12 10:15 ` Mike Rapoport
2026-01-12 14:39 ` Jason Gunthorpe
2026-01-13 11:34 ` Mike Rapoport
2026-01-13 13:05 ` Jason Gunthorpe [this message]
2026-01-13 14:46 ` Mike Rapoport
2026-01-13 14:58 ` Jason Gunthorpe
2026-01-13 16:16 ` Pasha Tatashin
2026-01-13 5:33 ` Jason Miu
2026-01-09 0:11 ` [PATCH v4 2/2] kho: Remove finalize state and clients Jason Miu
2026-01-12 10:25 ` Mike Rapoport
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=20260113130526.GE812923@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.com \
--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