linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: add EFI stub
Date: Thu, 5 Dec 2013 15:28:06 +0000	[thread overview]
Message-ID: <20131205152806.GC974@darko.cambridge.arm.com> (raw)
In-Reply-To: <1386254603.1861.120.camel@deneb.redhat.com>

On Thu, Dec 05, 2013 at 02:43:23PM +0000, Mark Salter wrote:
> On Thu, 2013-12-05 at 14:18 +0000, Catalin Marinas wrote:
> > On Fri, Nov 29, 2013 at 10:05:10PM +0000, Mark Salter wrote:
> > > This patch adds PE/COFF header fields to the start of the Image
> > > so that it appears as an EFI application to EFI firmware. An EFI
> > > stub is included to allow direct booting of the kernel Image. Due
> > > to EFI firmware limitations, only little endian kernels with 4K
> > > page sizes are supported at this time.
> > 
> > I don't fully understand the EFI firmware limitations but for big endian
> > we could have the EFI_STUB wrapper in little endian and get the kernel
> > to switch to big endian once booted. The image header should always be
> > little endian.
> 
> That would be fun. :) You'd also have to switch back and forth to make
> EFI runtime services calls.

OK, we'll have to live with this restriction.

> > And I have to dig further into the 4K limitation (or you could give a
> > quick summary ;)).
> 
> Just that the current UEFI spec mandates 4K pages for UEFI. So if UEFI
> maps two 4k pages with different attributes and those two pages are
> within the same 64k kernel page, there'd be a problem. I'd be better if
> UEFI used 64k pages, then the kernel could easily use 4k or 64k.

For server space, we may see some people asking for 64K pages. But I
don't know whether there are any UEFI plans here.

Thanks.

-- 
Catalin

  reply	other threads:[~2013-12-05 15:28 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 22:05 [PATCH 0/3] arm64: Add EFI stub and runtime services support Mark Salter
     [not found] ` < 1385762712-17043-2-git-send-email-msalter@redhat.com>
2013-11-29 22:05 ` [PATCH 1/3] arm64: add EFI stub Mark Salter
2013-12-03 18:38   ` Will Deacon
2013-12-03 19:31     ` Roy Franz
2013-12-03 19:31     ` Mark Salter
2013-12-05 14:18   ` Catalin Marinas
2013-12-05 14:43     ` Mark Salter
2013-12-05 15:28       ` Catalin Marinas [this message]
2013-12-06 12:25         ` Grant Likely
2013-12-06 13:34           ` Mark Salter
2013-12-06 13:38             ` Leif Lindholm
2013-12-06 13:51               ` Mark Salter
2013-12-06 14:55     ` Mark Salter
2013-12-16 15:46       ` Catalin Marinas
2013-12-06 12:12   ` Grant Likely
2013-11-29 22:05 ` [PATCH 2/3] doc: arm64: add description of EFI stub support Mark Salter
2013-12-05 12:53   ` Grant Likely
2013-11-29 22:05 ` [PATCH 3/3] arm64: add EFI runtime services Mark Salter
2013-12-05 15:25   ` Catalin Marinas
2013-12-05 15:52     ` Mark Salter
2013-12-05 15:59       ` Catalin Marinas
2013-12-06 14:34     ` Mark Salter
2013-12-09 13:52   ` Leif Lindholm
2013-12-10 17:58     ` Mark Salter

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=20131205152806.GC974@darko.cambridge.arm.com \
    --to=catalin.marinas@arm.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).