[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1480476287-232878-1-git-send-email-athorlton@sgi.com>
Date: Tue, 29 Nov 2016 21:24:45 -0600
From: Alex Thorlton <athorlton@....com>
To: linux-kernel@...r.kernel.org
Cc: Alex Thorlton <athorlton@....com>, Russ Anderson <rja@....com>,
David Vrabel <david.vrabel@...rix.com>,
Juergen Gross <jgross@...e.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>, x86@...nel.org,
xen-devel@...ts.xenproject.org
Subject: [RFC PATCH v2] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries
Here's the second round of my patches to fix up the problems that we're
seeing with the XENMEM_machine_memory_map hypercall. These few simple
changes, to give xen_e820_map some extra space, get things working fine
on our large machine.
This version of the patchset adds a patch to remove the #ifdef
CONFIG_EFI conditional around the definition of E820_X_MAX, so that it's
always slightly larger than E820MAX. I've also tweaked the code that
works on xen_e820_map to use ARRAY_SIZE(xen_e820_map) instead of using
E820_X_MAX directly, as suggested by Boris.
As always, I appreciate any input that others can give!
- Alex
Alex Thorlton (2):
x86: Make E820_X_MAX unconditionally larger than E820MAX
xen/x86: Increase xen_e820_map to E820_X_MAX possible entries
arch/x86/include/asm/e820.h | 8 +++-----
arch/x86/xen/setup.c | 6 +++---
2 files changed, 6 insertions(+), 8 deletions(-)
--
1.8.5.6
Powered by blists - more mailing lists