From: David Hildenbrand <david@redhat.com>
To: Dave Hansen <dave.hansen@intel.com>,
Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
Baoquan He <bhe@redhat.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
ebiederm@xmission.com, akpm@linux-foundation.org,
stanislav.kinsburskii@gmail.com, corbet@lwn.net,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, kys@microsoft.com, jgowans@amazon.com,
wei.liu@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org,
graf@amazon.de, pbonzini@redhat.com
Subject: Re: [RFC PATCH v2 0/7] Introduce persistent memory pool
Date: Thu, 28 Sep 2023 19:35:32 +0200 [thread overview]
Message-ID: <fa924c8d-c954-5612-37eb-43e1976a1b7b@redhat.com> (raw)
In-Reply-To: <ee1907a1-2f04-cfa3-9f09-75b94994e88b@intel.com>
On 28.09.23 15:22, Dave Hansen wrote:
> 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.
The motivation of handling kexec (faster?) in a hyper-v domain doesn't
sound particularly compelling got me for such features. If you inflated
memory, just don't allow to kexec. It's been broken for years IIUC.
Maybe the other use cases are more "relevant".
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-09-28 17:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01828.123092517290700465@us-mta-156.us.mimecast.lan>
2023-09-27 5:44 ` Baoquan He
2023-09-27 16:13 ` Stanislav Kinsburskii
2023-09-28 13:22 ` Dave Hansen
2023-09-27 23:25 ` Stanislav Kinsburskii
2023-09-28 17:29 ` Dave Hansen
2023-09-28 0:02 ` Stanislav Kinsburskii
2023-09-28 18:00 ` Dave Hansen
2023-09-28 0:38 ` Stanislav Kinsburskii
2023-09-28 19:16 ` Dave Hansen
2023-09-28 2:46 ` Stanislav Kinsburskii
2023-09-29 10:13 ` Shutemov, Kirill
2023-09-28 9:16 ` Stanislav Kinsburskii
[not found] ` <64208.123092816192300612@us-mta-483.us.mimecast.lan>
2023-09-28 23:56 ` Baoquan He
2023-09-28 7:18 ` Stanislav Kinsburskii
2023-09-28 17:35 ` David Hildenbrand [this message]
2023-09-28 17:37 ` Dave Hansen
2023-09-28 18:12 ` [EXTERNAL] " KY Srinivasan
[not found] ` <58146.123092712145601339@us-mta-73.us.mimecast.lan>
2023-09-28 10:25 ` Baoquan He
2023-09-27 22:44 ` Stanislav Kinsburskii
2023-09-28 17:29 ` David Hildenbrand
2023-09-25 21:27 Stanislav Kinsburskii
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=fa924c8d-c954-5612-37eb-43e1976a1b7b@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=graf@amazon.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jgowans@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=skinsburskii@linux.microsoft.com \
--cc=stanislav.kinsburskii@gmail.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=x86@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