public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: David Howells <dhowells@redhat.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Does anything ever enter through startup_64 in head_64.S?
Date: Wed, 7 Dec 2016 15:24:34 +0000	[thread overview]
Message-ID: <20161207152434.GB5462@codeblueprint.co.uk> (raw)
In-Reply-To: <21775.1481123477@warthog.procyon.org.uk>

On Wed, 07 Dec, at 03:11:17PM, David Howells wrote:
> Hi Matt,
> 
> Does anything ever enter the kernel through startup_64 in head_64.S?[*]  Do
> all 64-bit mode entries always enter through one of the EFI entry points?
 
Which head_64.S? There are two ;-)

Assuming you mean startup_64 in boot/compressed/head_64.S, then the
answer is "yes". 64-bit BIOS boot loaders will jump there.

I'm fairly sure it's possible to boot that way on EFI too, you just
lose some of the newer functionality that is dependent on the EFI boot
stub. But I don't remember the last time I tried it.

In general, we've always tried to maintain backwards compat, but you
don't get the new features without switching to the EFI entry points.

Whether or not any distros are still using the old 0x200 entry point
for EFI is a good question, though.

  reply	other threads:[~2016-12-07 15:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07 15:11 Does anything ever enter through startup_64 in head_64.S? David Howells
2016-12-07 15:24 ` Matt Fleming [this message]
2016-12-07 16:47   ` David Howells

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=20161207152434.GB5462@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=dhowells@redhat.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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