From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [edk2] apparent KVM problem with LRET in TianoCore S3 resume trampoline Date: Fri, 06 Dec 2013 15:29:12 +0100 Message-ID: <52A1DF38.7030908@redhat.com> References: <52A0A5E0.3090802@redhat.com> <52A0BB05.8010703@redhat.com> <52A0C5F4.3040603@redhat.com> <52A1BCFE.4020100@redhat.com> <52A1D197.60701@redhat.com> <74D8A39837DF1E4DA445A8C0B3885C50010F704A@SHSMSX102.ccr.corp.intel.com> Reply-To: edk2-devel@lists.sourceforge.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: "edk2-devel@lists.sourceforge.net" , KVM devel mailing list To: "Yao, Jiewen" Return-path: In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50010F704A@SHSMSX102.ccr.corp.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: edk2-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org 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 ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk