linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] efi/arm64: efistub: don't abort if base of DRAM is occupied
Date: Tue, 15 Jul 2014 09:11:00 -0400	[thread overview]
Message-ID: <1405429860.25580.25.camel@deneb.redhat.com> (raw)
In-Reply-To: <20140715100221.GU4179@bivouac.eciton.net>

On Tue, 2014-07-15 at 11:02 +0100, Leif Lindholm wrote:
> > @@ -273,6 +282,10 @@ static void __init free_boot_services(void)
> >                       continue;
> >               }
> >  
> > +             /* Don't free anything below kernel */
> > +             if (md->phys_addr < PHYS_OFFSET)
> > +                     continue;
> > +
> 
> Is the spin table area really allocated as BOOT_SERVICES_*?
> 

No. It is EFI_RESERVED_TYPE. But if UEFI is allowed below the kernel,
then there could be BS code/data memory which we'd want to ignore.

  parent reply	other threads:[~2014-07-15 13:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 15:25 [PATCH] efi/arm64: efistub: don't abort if base of DRAM is occupied Ard Biesheuvel
2014-07-14 15:27 ` Ard Biesheuvel
2014-07-14 18:40 ` Mark Salter
2014-07-15 10:02   ` Leif Lindholm
2014-07-15 11:05     ` Mark Rutland
2014-07-15 13:11     ` Mark Salter [this message]
2014-07-15 13:54       ` Leif Lindholm
2014-07-15 14:23         ` Mark Salter
2014-07-15 14:31           ` Mark Rutland
2014-07-15 14:49           ` Leif Lindholm
2014-07-15 15:04             ` Mark Salter
2014-07-15 15:28               ` Leif Lindholm
2014-07-16 13:13                 ` Mark Salter
2014-07-22 17:08                   ` Leif Lindholm
2014-07-22 19:28                     ` Mark Salter
2014-07-22 21:28                       ` Leif Lindholm
2014-07-15 11:00   ` Mark Rutland

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=1405429860.25580.25.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.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).