From: Avi Kivity <avi@redhat.com>
To: Neo Jia <neojia@gmail.com>
Cc: ewheeler <kvm@ew.ewheeler.org>, kvm@vger.kernel.org
Subject: Re: how to debug unhandled vm exit: 0x11?
Date: Fri, 01 Oct 2010 16:29:25 +0200 [thread overview]
Message-ID: <4CA5F045.4010308@redhat.com> (raw)
In-Reply-To: <AANLkTimdwyL07KwOA4LEvB=ETizd5cV+OboF58wycLUv@mail.gmail.com>
On 10/01/2010 08:16 AM, Neo Jia wrote:
> On Wed, Sep 29, 2010 at 1:38 AM, Avi Kivity<avi@redhat.com> wrote:
> > On 09/28/2010 08:40 PM, Neo Jia wrote:
> >>
> >> I found the instruction that caused this problem:
> >>
> >> emulation failed (failure) rip 71f14651 66 0f 7f 07
> >>
> >> And according to Intel, this is a MOVDQA. So, do we already have this
> >> instruction emulated as I am using a pretty old version of KVM
> >> (release 88)? If yes, could you point me to the file I need to look at
> >> for that specific patch?
> >>
> >
> > movdqa is not emulated.
>
> I am going to give a try to emulate this instruction. BTW, do we have
> any unit test for those emulated x86 instruction sets?
Indeed we do:
http://git.kernel.org/?p=virt/kvm/kvm-unit-tests.git;a=summary
Check out x86/emulator.c.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-10-01 14:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 16:01 how to debug unhandled vm exit: 0x11? Neo Jia
2010-07-26 16:14 ` Avi Kivity
2010-07-26 17:58 ` ewheeler
2010-07-27 10:04 ` Avi Kivity
2010-09-28 18:40 ` Neo Jia
2010-09-28 18:46 ` Neo Jia
2010-09-29 8:38 ` Avi Kivity
2010-10-01 6:16 ` Neo Jia
2010-10-01 14:29 ` Avi Kivity [this message]
2010-10-11 5:46 ` Neo Jia
2010-10-11 6:30 ` Avi Kivity
2010-10-11 6:49 ` Neo Jia
2010-10-11 14:27 ` Avi Kivity
2010-10-11 14:31 ` Avi Kivity
2010-10-11 15:00 ` Avi Kivity
2010-10-12 4:09 ` Neo Jia
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=4CA5F045.4010308@redhat.com \
--to=avi@redhat.com \
--cc=kvm@ew.ewheeler.org \
--cc=kvm@vger.kernel.org \
--cc=neojia@gmail.com \
/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