Good investigation. I really appreciate that. Now, it seems we need OVMF pkg owner to check when 0x9c000 are corrupted, and why. Thank you Yao Jiewen -----Original Message----- From: Paolo Bonzini [mailto:paolo.bonzini@xxxxxxxxx] On Behalf Of Paolo Bonzini Sent: Friday, December 06, 2013 10:29 PM To: Yao, Jiewen Cc: edk2-devel@xxxxxxxxxxxxxxxxxxxxx; KVM devel mailing list Subject: Re: [edk2] apparent KVM problem with LRET in TianoCore S3 resume trampoline Il 06/12/2013 14:46, Yao, Jiewen ha scritto: > Hi Paolo > I am a little confused here. You said "Still, indeed it's OVMF's fault." and "Still an EDK2 problem." ?????? Sorry for the confusion. I wrote OVMF/EDK2 interchangeably, just to say "not KVM". > EDKII BIOS should always create 1:1 mapping virtual-physical address. But I am not clear about OS waking vector. > For "EPT_VIOLATION rip 0xffffffff81000110.", is that happen in EDKII BIOS or in OS waking vector? That's after the OS waking vector is invoked. But that memory was corrupted by EDKII/OVMF before the OS waking vector is invoked. Paolo > All in all, I have interesting to know one thing at first: > Is OVMF crash in BIOS before jump to OS waking vector? Or is OVMF crash inside OS waking vector? > > Thank you -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
