* Matthew Garrett <[email protected]> wrote:
> On Thu, Jun 20, 2013 at 11:13:21AM +0200, Ingo Molnar wrote:
>
> > Cool - and supposedly this will work in a Mac environment as well? Would
> > be very nice to avoid fundamentally fragile system specific quirks for
> > something as fundamental as the EFI runtime memory mapping model ...
>
> Apple is the only case where I'd expect there to be an issue, since they
> only started supporting booting Windows via UEFI on very recent systems.
> However, unless they're actually sniffing the page tables on UEFI entry,
> I can't see any way that this could break things???
Agreed - I was susprised to see that the runtime was able to _break_ in
any way due to 1:1: my assumption was that it can only get better.
But I did not realize that the 1:1 boot flag also changed what was passed
down, which probably explains the breakages.
I'd even argue to not do this whole boot flag thing at all - just
standardize on the Windows compatibility model as closely as possible.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
