[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260113130526.GE812923@nvidia.com>
Date: Tue, 13 Jan 2026 09:05:26 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Mike Rapoport <rppt@...nel.org>
Cc: Jason Miu <jasonmiu@...gle.com>, Alexander Graf <graf@...zon.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Baoquan He <bhe@...hat.com>, Changyuan Lyu <changyuanl@...gle.com>,
David Matlack <dmatlack@...gle.com>,
David Rientjes <rientjes@...gle.com>,
Pasha Tatashin <pasha.tatashin@...een.com>,
Pratyush Yadav <pratyush@...nel.org>, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v4 1/2] kho: Adopt radix tree for preserved memory
tracking
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
Powered by blists - more mailing lists