From: Juergen Gross <jgross@suse.com>
To: Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Cc: Russ Anderson <rja@sgi.com>,
David Vrabel <david.vrabel@citrix.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: [RFC PATCH v3] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries
Date: Thu, 8 Dec 2016 06:50:22 +0100 [thread overview]
Message-ID: <ed498aea-127a-246c-79e8-67ade61ba0ce@suse.com> (raw)
In-Reply-To: <1480960154-211541-1-git-send-email-athorlton@sgi.com>
On 05/12/16 18:49, Alex Thorlton wrote:
> This is the third pass at my patchset to fix up our problems with
> XENMEM_machine_memory_map on large systems. The only changes on this
> pass were to flesh out the comment above the E820_X_MAX definition, and
> to add Juergen's Reviewed-by to the second patch.
>
> Let me know if anyone has any questions/comments!
>
> 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 | 12 ++++++++----
> arch/x86/xen/setup.c | 6 +++---
> 2 files changed, 11 insertions(+), 7 deletions(-)
>
Ingo, do you have any preferences through which tree those patches
should go? I'd like to have at least patch 2 in 4.10, so I could take
it through the Xen tree.
Juergen
next prev parent reply other threads:[~2016-12-08 5:50 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
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 ` Juergen Gross [this message]
2016-12-09 3:46 ` [RFC PATCH v3] " 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=ed498aea-127a-246c-79e8-67ade61ba0ce@suse.com \
--to=jgross@suse.com \
--cc=athorlton@sgi.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.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;
as well as URLs for NNTP newsgroup(s).