From: William Kucharski <william.kucharski@oracle.com>
To: Juergen Gross <jgross@suse.com>
Cc: kernel list <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
Subject: Re: [PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation
Date: Wed, 30 Jan 2019 03:59:52 -0700 [thread overview]
Message-ID: <C4A55B5E-47A5-454A-AB90-AB52DF42CD88@oracle.com> (raw)
In-Reply-To: <20190130082233.23840-3-jgross@suse.com>
> On Jan 30, 2019, at 1:22 AM, Juergen Gross <jgross@suse.com> wrote:
>
> +#ifdef CONFIG_MEMORY_HOTPLUG
> + /*
> + * Don't allow adding memory not in E820 map while
> + * booting the system. Once the balloon driver is up
> + * it will remove that restriction again.
> + */
> + max_mem_size = xen_e820_table.entries[i].addr +
> + xen_e820_table.entries[i].size;
> +#endif
> }
>
> if (!discard)
Reviewed-by: William Kucharski <william.kucharski@oracle.com>
next prev parent reply other threads:[~2019-01-30 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 8:22 [PATCH v2 0/2] x86: respect memory size limits Juergen Gross
2019-01-30 8:22 ` [PATCH v2 1/2] x86: respect memory size limiting via mem= parameter Juergen Gross
2019-02-11 12:06 ` Ingo Molnar
2019-02-11 12:14 ` [Xen-devel] " Juergen Gross
2019-02-11 12:23 ` Ingo Molnar
2019-02-11 12:35 ` Juergen Gross
2019-01-30 8:22 ` [PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation Juergen Gross
2019-01-30 10:59 ` William Kucharski [this message]
2019-02-01 18:46 ` Boris Ostrovsky
2019-02-07 6:32 ` Juergen Gross
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=C4A55B5E-47A5-454A-AB90-AB52DF42CD88@oracle.com \
--to=william.kucharski@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.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=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