On Fri, 2013-12-13 at 15:12 +0000, Gao, Liming wrote: > David: > You mean IA32 Thunk breaks the real hardware, but X64 Thunk doesn't > it. Could you explain it in more detail?
My hardware is 32-bit only :) In fact even if that were not true, I don't think the X64 code would break it. The "problem" with the hardware is that I really have to use a far JMP instruction after clearing CR0.PE to enter real mode — which is what the SDM requires anyway! In the IA32 code, that requirement is violated because we do a bunch of other stuff followed by a far RET. My hardware doesn't like that. There are other SDM violations in the IA32 code, but none that are actually hurting me on real hardware right now. X64 has a different set of SDM violations. It *does* use a far JMP, but it isn't the first instruction after clearing CR0.PE, as it should be. These other violations in both IA32 and X64 code do need fixing, but they aren't on my critical path *right* now. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
