On Sun, Jun 02, 2013 at 11:56:20PM +0100, Matthew Garrett wrote:
I've just run Windows 8 under a hacked up copy of OVMF that dumps
the data passed to SetVirtualAddressMap. It seems that Windows *is*
mapping the runtime services to higher addresses - so presumably the
1:1 mapping is in addition
On Mon, Jun 03, 2013 at 09:18:06AM -0700, James Bottomley wrote:
I don't entirely buy that. All EFI programs run with the physical
address map, therefore every API an EFI program uses is also tested, at
boot time only, obviously.
That seems optimistic. Windows never calls QueryVariableInfo()
On Mon, 2013-06-03 at 17:24 +0100, Matthew Garrett wrote:
On Mon, Jun 03, 2013 at 09:18:06AM -0700, James Bottomley wrote:
I don't entirely buy that. All EFI programs run with the physical
address map, therefore every API an EFI program uses is also tested, at
boot time only, obviously.
On Mon, 2013-06-03 at 17:42 +0100, Matthew Garrett wrote:
On Mon, Jun 03, 2013 at 09:35:07AM -0700, James Bottomley wrote:
On Mon, 2013-06-03 at 17:24 +0100, Matthew Garrett wrote:
That seems optimistic. Windows never calls QueryVariableInfo() during
boot services, so what makes you
On Mon, 2013-06-03 at 19:11 +0100, Matthew Garrett wrote:
The problem there is that you're saying In theory. We know that
Windows doesn't behave this way, so we have no legitimate expectation
that it'll work. We know that it doesn't on some Apple hardware.
Fine, you say we need to
From: Borislav Petkov b...@suse.de
Hi all,
this one is 64-bit only for now and it has been tested only in kvm with
OVMF.
Keeping in mind the ihnerent efi b0rkedness left and right, I'd like to
be very cautious and conservative with this and not hurry anything until
it has been actually very
I've just run Windows 8 under a hacked up copy of OVMF that dumps the
data passed to SetVirtualAddressMap. It seems that Windows *is* mapping
the runtime services to higher addresses - so presumably the 1:1 mapping
is in addition to the virtual mapping.
--
Matthew Garrett |
