public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: devel@edk2.groups.io, pedro.falcato@gmail.com
Cc: Andrew Fish <afish@apple.com>,
	 "Kinney, Michael D" <michael.d.kinney@intel.com>,
	Ray Ni <ray.ni@intel.com>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [edk2-devel] Side effects of enabling PML5 in EFI
Date: Wed, 10 May 2023 11:17:55 +0200	[thread overview]
Message-ID: <pitmz4if6srumff322u264l2hkr534ictq3zu2sepetoj7khch@6vcncx3jvl73> (raw)
In-Reply-To: <CAKbZUD346-0qU2E2dVXY7M9ev-GGfU=9OYFc8DwE53ndHyzOiw@mail.gmail.com>

On Tue, May 09, 2023 at 06:24:03PM +0100, Pedro Falcato wrote:
> Hi all,
> 
> (+CC people vaguely related to the EFI spec, the PML5 implementation
> and kernel EFI boot code)
> 
> As a result of the latest 5-level paging patches, I've been looking
> into how tiano supports PML5.
> This raised a question: Doesn't enabling PML5 in-firmware break
> compatibility with non-PML5-aware bootloaders and kernels?

kernels yes, bootloaders probably not (unless the bootloader not the
kernel calls exitbootservices).

> So, how is any of this supposed to work?

edk2 is relatively late to the party, so with everybody else supporting
5-level paging already it might not be much of an issue in practice even
though there is no compatibility handling (I know of) in edk2.

When running your operating system museum in virtual machines you have
the option to just turn off 5-level paging support in the virtual cpu.

take care,
  Gerd


  reply	other threads:[~2023-05-10  9:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 17:24 Side effects of enabling PML5 in EFI Pedro Falcato
2023-05-10  9:17 ` Gerd Hoffmann [this message]
2023-05-10  9:34   ` [edk2-devel] " Ni, Ray
2023-05-10 16:38     ` Pedro Falcato
2023-05-11  3:36       ` Ni, Ray
2023-05-10 16:31   ` Pedro Falcato
2023-05-10  9:41 ` Ard Biesheuvel
2023-05-10 16:51   ` Pedro Falcato

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-list 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=pitmz4if6srumff322u264l2hkr534ictq3zu2sepetoj7khch@6vcncx3jvl73 \
    --to=devel@edk2.groups.io \
    /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