Re: [PATCH] x86/unaccepted_memory: Do not accept ranges that are no longer E820 RAM

From: Gupta, Pankaj

Date: Mon Nov 02 2026 - 07:16:12 EST



Can we just disallow memmap= when running in a confidential VM?

My experiments showed: memmap itself don't have a problem but memap with a hole is causing crash.

There might be some usecases which are already using this, e.g:

https://lore.kernel.org/all/20261029-cma-multi-v1-0-2cbced8b5cb7@xxxxxxxxxx/

Its also good to have a general safeguard to not accept memory that is not marked as RAM in e820?

Thanks,

Pankaj