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.2 \(3445.102.3\))
Subject: Re: [PATCH 1/2] x86: respect memory size limiting via mem= parameter
From:   William Kucharski <william.kucharski@oracle.com>
In-Reply-To: <20190122080628.7238-2-jgross@suse.com>
Date:   Wed, 23 Jan 2019 07:35:28 -0700
Cc:     kernel list <linux-kernel@vger.kernel.org>,
        xen-devel <xen-devel@lists.xenproject.org>,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@kernel.org>,
        Linux-MM <linux-mm@kvack.org>,
        Boris Ostrovsky <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: <69D0866F-77A7-4529-A01E-12395106E22D@oracle.com>
References: <20190122080628.7238-1-jgross@suse.com>
 <20190122080628.7238-2-jgross@suse.com>
To:     Juergen Gross <jgross@suse.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Jan 22, 2019, at 1:06 AM, Juergen Gross <jgross@suse.com> wrote:
> 
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index b9a667d36c55..7fc2a87110a3 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -96,10 +96,16 @@ void mem_hotplug_done(void)
> 	cpus_read_unlock();
> }
> 
> +u64 max_mem_size = -1;

This may be pedantic, but I'd rather see U64_MAX used here.