public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Thelen <jthelen-sJ/iWh9BUns@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Joseph Thelen <jthelen-sJ/iWh9BUns@public.gmane.org>,
	Alex Thorlton <athorlton-sJ/iWh9BUns@public.gmane.org>,
	Matt Fleming
	<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
	Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
	x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [RFC PATCH] x86/efi: Auto enable EFI memmap on SGI UV systems
Date: Thu,  2 Jun 2016 15:50:34 -0500	[thread overview]
Message-ID: <1464900635-11957-1-git-send-email-jthelen@sgi.com> (raw)

The intent here is to automatically enable the EFI memory map entries
on SGI UV systems, which can have more than 128 E820 entries and
will cause headaches if the EFI memory map entries are not added.

The assumption is made that the community would prefer that this change
be a UV specific quirk, as opposed to automatically adding the EFI
memory map entries whenever more then 128 E820 entries exist. If this
assumption is incorrect, the patch can be changed to check the number
of E820 entries rather than for whether or not the system is a UV.

Cc: Alex Thorlton <athorlton-sJ/iWh9BUns@public.gmane.org>
Cc: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
Cc: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Cc: Ingo Molnar <mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org

Joseph Thelen (1):
  x86/efi: Auto enable EFI memmap on SGI UV systems

 arch/x86/platform/efi/efi.c | 43 +++++++++++++++++++++++++++++++++++++++----
 1 file changed, 39 insertions(+), 4 deletions(-)

-- 
1.8.5.6

             reply	other threads:[~2016-06-02 20:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 20:50 Joseph Thelen [this message]
2016-06-02 20:50 ` [PATCH] x86/efi: Auto enable EFI memmap on SGI UV systems Joseph Thelen
     [not found]   ` <1464900635-11957-2-git-send-email-jthelen-sJ/iWh9BUns@public.gmane.org>
2016-06-08 11:12     ` Ingo Molnar
     [not found]       ` <20160608111223.GA5772-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-14 22:19         ` Joseph Thelen
2016-06-08 12:36     ` Matt Fleming
     [not found]       ` <20160608123623.GW2658-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-06-14 22:34         ` Joseph Thelen
     [not found]           ` <20160614223448.GC172952-7ppMa7wkY9tKToyKb8PD+Zs2JHu2awxn0E9HWUfgJXw@public.gmane.org>
2016-06-17 20:57             ` Joseph Thelen

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=1464900635-11957-1-git-send-email-jthelen@sgi.com \
    --to=jthelen-sj/iwh9buns@public.gmane.org \
    --cc=athorlton-sJ/iWh9BUns@public.gmane.org \
    --cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
    --cc=mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
    --cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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