Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
Subject: Re: [PATCH v3 1/2] x86: respect memory size limiting via mem=
 parameter
From:   William Kucharski <william.kucharski@oracle.com>
In-Reply-To: <20190214104240.24428-2-jgross@suse.com>
Date:   Thu, 14 Feb 2019 04:00:37 -0700
Cc:     linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
        x86@kernel.org, linux-mm@kvack.org, boris.ostrovsky@oracle.com,
        sstabellini@kernel.org, hpa@zytor.com, tglx@linutronix.de,
        mingo@redhat.com, bp@alien8.de
Content-Transfer-Encoding: 7bit
Message-Id: <A93A19ED-0121-4E88-B24E-1593BEBD3384@oracle.com>
References: <20190214104240.24428-1-jgross@suse.com>
 <20190214104240.24428-2-jgross@suse.com>
To:     Juergen Gross <jgross@suse.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Feb 14, 2019, at 3:42 AM, Juergen Gross <jgross@suse.com> wrote:
> 
> When limiting memory size via kernel parameter "mem=" this should be
> respected even in case of memory made accessible via a PCI card.
> 
> Today this kind of memory won't be made usable in initial memory
> setup as the memory won't be visible in E820 map, but it might be
> added when adding PCI devices due to corresponding ACPI table entries.
> 
> Not respecting "mem=" can be corrected by adding a global max_mem_size
> variable set by parse_memopt() which will result in rejecting adding
> memory areas resulting in a memory size above the allowed limit.
> 
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Acked-by: Ingo Molnar <mingo@kernel.org>

Reviewed-by: William Kucharski <william.kucharski@oracle.com>