[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee1907a1-2f04-cfa3-9f09-75b94994e88b@intel.com>
Date: Thu, 28 Sep 2023 06:22:54 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>,
Baoquan He <bhe@...hat.com>
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
ebiederm@...ssion.com, akpm@...ux-foundation.org,
stanislav.kinsburskii@...il.com, corbet@....net,
linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
linux-mm@...ck.org, kys@...rosoft.com, jgowans@...zon.com,
wei.liu@...nel.org, arnd@...db.de, gregkh@...uxfoundation.org,
graf@...zon.de, pbonzini@...hat.com
Subject: Re: [RFC PATCH v2 0/7] Introduce persistent memory pool
On 9/27/23 09:13, Stanislav Kinsburskii wrote:
> Once deposited, these pages can't be accessed by Linux anymore and thus
> must be preserved in "used" state across kexec, as hypervisor state is
> unware of kexec.
If Linux can't access them, they're not RAM any more. I'd much rather
remove them from the memory map and move on with life rather than
implement a bunch of new ABI that's got to be handed across kernels.
Powered by blists - more mailing lists