From: Akihiro Suda <suda.kyoto@gmail.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org, Linux x86 <x86@kernel.org>
Subject: Re: [PATCH] efi: bump efistub version from 1.1 to 3.0 for VZLinuxBootLoader compatibility
Date: Sat, 3 Jun 2023 19:50:15 +0900 [thread overview]
Message-ID: <CAG8fp8TXA2UG+tS8F5KhSW7Xi1o7oHk0kQTs=Z8JpDU5VStjfQ@mail.gmail.com> (raw)
In-Reply-To: <CAMj1kXHAt69QqFdZDOTFKNLvAYuY9cwrVFgE+eDNZ8FSQA-45w@mail.gmail.com>
> > > On x86, it incorporates a BIOS style loader that does not implement or expose EFI to the loaded kernel.
> >
> > AFAICS, it does not seem to use real mode BIOS.
> >
>
> I never mentioned real mode, did I?
Sorry, I just misinterpreted "BIOS style loader".
2023年6月3日(土) 7:52 Ard Biesheuvel <ardb@kernel.org>:
>
> On Fri, 2 Jun 2023 at 22:30, Akihiro Suda <suda.kyoto@gmail.com> wrote:
> >
> > > > I'll queue this as a fix, but I'm going to tweak the comment (and the
> > > > commit log) a bit, if you don't mind
> >
> > Thank you for rewriting my comments, but the new comments seem
> > slightly incorrect:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=36e4fc57fc1619f462e669e939209c45763bc8f5
> >
> > > efi: Bump stub image version for macOS HVF compatibility
> >
> > The commit is about Virtualization.framework, not about
> > Hypervisor.framework (HVF).
> >
> > Virtualization.framework = high-level VMM, similar to QEMU
> > (/usr/bin/qemu-system-*)
> > Hypervisor.framework = low-level VMM, similar to kvm.ko
> >
> > > The macOS hypervisor framework includes a host-side VMM called VZLinuxBootLoader
> >
> > VZLinuxBootLoader is a part of Virtualization.framework, not
> > Hypervisor.framework.
> > Also, VZLinuxBootLoader is not a VMM; it is just an API for loading
> > vmlinuz into Virtualization.framework.
> > (similar to the `-kernel` and the `-initrd` flags of QEMU)
> >
>
> Apologies for these mistakes. Unfortunately, this patch has been
> merged now so there is nothing we can do about it.
>
> > > On x86, it incorporates a BIOS style loader that does not implement or expose EFI to the loaded kernel.
> >
> > AFAICS, it does not seem to use real mode BIOS.
> >
>
> I never mentioned real mode, did I?
prev parent reply other threads:[~2023-06-03 10:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 7:58 [PATCH] efi: bump efistub version from 1.1 to 3.0 for VZLinuxBootLoader compatibility Akihiro Suda
2023-05-28 18:48 ` Ard Biesheuvel
2023-05-29 0:51 ` Akihiro Suda
2023-06-02 20:29 ` Akihiro Suda
2023-06-02 22:52 ` Ard Biesheuvel
2023-06-03 10:50 ` Akihiro Suda [this message]
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='CAG8fp8TXA2UG+tS8F5KhSW7Xi1o7oHk0kQTs=Z8JpDU5VStjfQ@mail.gmail.com' \
--to=suda.kyoto@gmail.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).