From: Paolo Bonzini <pbonzini@redhat.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>
Cc: "edk2-devel@lists.sourceforge.net"
<edk2-devel@lists.sourceforge.net>,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [edk2] apparent KVM problem with LRET in TianoCore S3 resume trampoline
Date: Fri, 06 Dec 2013 15:29:12 +0100 [thread overview]
Message-ID: <52A1DF38.7030908@redhat.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50010F704A@SHSMSX102.ccr.corp.intel.com>
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
next prev parent reply other threads:[~2013-12-06 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:12 [edk2] apparent KVM problem with LRET in TianoCore S3 resume trampoline Laszlo Ersek
2013-12-05 16:50 ` Laszlo Ersek
2013-12-05 17:42 ` Paolo Bonzini
2013-12-05 18:29 ` Laszlo Ersek
2013-12-06 12:03 ` Paolo Bonzini
2013-12-06 13:31 ` Paolo Bonzini
2013-12-06 13:46 ` Yao, Jiewen
2013-12-06 14:29 ` Paolo Bonzini [this message]
2013-12-06 14:47 ` Yao, Jiewen
2013-12-06 14:51 ` Paolo Bonzini
2013-12-06 13:31 ` Yao, Jiewen
2013-12-08 17:43 ` Laszlo Ersek
2013-12-08 22:15 ` Laszlo Ersek
2013-12-05 22:38 ` Laszlo Ersek
2013-12-05 22:53 ` Andrew Fish
2013-12-07 16:25 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52A1DF38.7030908@redhat.com \
--to=pbonzini@redhat.com \
--cc=edk2-devel@lists.sourceforge.net \
--cc=jiewen.yao@intel.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox