From: Ingo Molnar <mingo@kernel.org>
To: Alex Thorlton <athorlton@sgi.com>
Cc: linux-kernel@vger.kernel.org, Russ Anderson <rja@sgi.com>,
David Vrabel <david.vrabel@citrix.com>,
Ingo Molnar <mingo@redhat.com>, Juergen Gross <jgross@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
x86@kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH 1/2] x86: Make E820_X_MAX unconditionally larger than E820MAX
Date: Wed, 30 Nov 2016 07:21:48 +0100 [thread overview]
Message-ID: <20161130062148.GA11684@gmail.com> (raw)
In-Reply-To: <1480476287-232878-2-git-send-email-athorlton@sgi.com>
* Alex Thorlton <athorlton@sgi.com> wrote:
> It's really not necessary to limit E820_X_MAX to 128 in the non-EFI
> case. This commit drops E820_X_MAX's dependency on CONFIG_EFI, so that
> E820_X_MAX is always at least slightly larger than E820MAX.
>
> The real motivation behind this is actually to prevent some issues in
> the Xen kernel, where the XENMEM_machine_memory_map hypercall can
> produce an e820 map larger than 128 entries, even on systems where the
> original e820 table was quite a bit smaller than that, depending on how
> many IOAPICs are installed on the system.
>
> Signed-off-by: Alex Thorlton <athorlton@sgi.com>
> Suggested-by: Ingo Molnar <mingo@redhat.com>
> Cc: Russ Anderson <rja@sgi.com>
> Cc: David Vrabel <david.vrabel@citrix.com>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Juergen Gross <jgross@suse.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: Denys Vlasenko <dvlasenk@redhat.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Cc: x86@kernel.org
> Cc: xen-devel@lists.xenproject.org
> ---
> arch/x86/include/asm/e820.h | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/include/asm/e820.h b/arch/x86/include/asm/e820.h
> index 476b574..aa00d33 100644
> --- a/arch/x86/include/asm/e820.h
> +++ b/arch/x86/include/asm/e820.h
> @@ -1,13 +1,15 @@
> #ifndef _ASM_X86_E820_H
> #define _ASM_X86_E820_H
>
> -#ifdef CONFIG_EFI
> +/*
> + * We need to make sure that E820_X_MAX is defined
> + * before we include uapi/asm/e820.h
> + */
> #include <linux/numa.h>
> #define E820_X_MAX (E820MAX + 3 * MAX_NUMNODES)
What we need an explanation for in the comment is what does this stand for (what
does the 'X' mean?), and what is the magic 3*MAX_NUMNODES about?
Thanks,
Ingo
next prev parent reply other threads:[~2016-11-30 6:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 0:11 [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries Alex Thorlton
2016-11-15 6:33 ` Juergen Gross
2016-11-15 7:15 ` Jan Beulich
[not found] ` <582AC427020000780011EA7E@suse.com>
2016-11-15 7:36 ` Juergen Gross
2016-11-15 8:01 ` Jan Beulich
[not found] ` <582ACEDE020000780011EAC9@suse.com>
2016-11-15 8:42 ` Juergen Gross
2016-11-15 9:45 ` Jan Beulich
[not found] ` <582AE72D020000780011EBB2@suse.com>
2016-11-15 9:55 ` Juergen Gross
2016-11-15 10:44 ` Jan Beulich
[not found] ` <582AF51F020000780011ECB4@suse.com>
2016-11-15 11:07 ` Juergen Gross
2016-11-15 11:12 ` Jan Beulich
2016-11-15 15:22 ` Alex Thorlton
2016-11-16 6:06 ` Juergen Gross
2016-11-30 3:24 ` [RFC PATCH v2] " Alex Thorlton
2016-11-30 3:24 ` [PATCH 1/2] x86: Make E820_X_MAX unconditionally larger than E820MAX Alex Thorlton
2016-11-30 6:21 ` Ingo Molnar [this message]
2016-12-01 18:37 ` Alex Thorlton
2016-11-30 3:24 ` [PATCH 2/2] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries Alex Thorlton
2016-11-30 5:18 ` Juergen Gross
2016-12-05 17:49 ` [RFC PATCH v3] " Alex Thorlton
2016-12-05 17:49 ` [PATCH 1/2] x86: Make E820_X_MAX unconditionally larger than E820MAX Alex Thorlton
2016-12-09 10:12 ` Juergen Gross
2016-12-05 17:49 ` [PATCH 2/2] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries Alex Thorlton
2016-12-09 10:12 ` Juergen Gross
2016-12-08 5:50 ` [RFC PATCH v3] " Juergen Gross
2016-12-09 3:46 ` Ingo Molnar
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=20161130062148.GA11684@gmail.com \
--to=mingo@kernel.org \
--cc=athorlton@sgi.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--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