Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <de2500c4-fce4-31dc-29bc-aa3007027eb9@intel.com>
Date:   Thu, 23 Jun 2022 07:06:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.1
Subject: Re: [RFC] memmap: introduce cmdline parameter "memmap=nn[KMG]$"
 without start addr
Content-Language: en-US
To:     lizhe.67@bytedance.com, tglx@linutronix.de, mingo@redhat.com,
        bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
        hpa@zytor.com
Cc:     lizefan.x@bytedance.com, linux-doc@vger.kernel.org,
        linux-kernel@vger.kernel.org
References: <20220623062402.12392-1-lizhe.67@bytedance.com>
From:   Dave Hansen <dave.hansen@intel.com>
In-Reply-To: <20220623062402.12392-1-lizhe.67@bytedance.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 6/22/22 23:24, lizhe.67@bytedance.com wrote:
> In our scenario, we need reserve or alloc large continous memory like
> 256M in machine which have different memory specification at just
> boot phase for a user land process.

Just marking the memory reserved doesn't do any good by itself.  There
must be some *other* kernel code to find this reserved area and make it
available to userspace.

It seems kinda silly to add this to the kernel without also adding the
other half of the solution.  Plus, we don't really even know what this
is for.  Are there other, better solutions?  I certainly can't offer any
because this changelog did not provide a full picture of the problem
this solves.