From: Juergen Gross <jgross@suse.com>
To: William Kucharski <william.kucharski@oracle.com>
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
Subject: Re: [PATCH 1/2] x86: respect memory size limiting via mem= parameter
Date: Wed, 23 Jan 2019 15:39:11 +0100 [thread overview]
Message-ID: <222a2429-957c-c6cd-3f46-06a627bbbd5e@suse.com> (raw)
In-Reply-To: <69D0866F-77A7-4529-A01E-12395106E22D@oracle.com>
On 23/01/2019 15:35, William Kucharski wrote:
>
>
>> 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.
Fine with me. Will change.
Juergen
next prev parent reply other threads:[~2019-01-23 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 8:06 [PATCH 0/2] x86: respect memory size limits Juergen Gross
2019-01-22 8:06 ` [PATCH 1/2] x86: respect memory size limiting via mem= parameter Juergen Gross
2019-01-23 14:35 ` William Kucharski
2019-01-23 14:39 ` Juergen Gross [this message]
2019-01-22 8:06 ` [PATCH 2/2] x86/xen: dont add memory above max allowed allocation Juergen Gross
2019-01-22 8:52 ` [Xen-devel] " Jan Beulich
2019-01-22 8:52 ` Jan Beulich
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=222a2429-957c-c6cd-3f46-06a627bbbd5e@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=william.kucharski@oracle.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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