public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 11 Oct 2010 16:31:05 +0200	[thread overview]
Message-ID: <4CB31FA9.7080407@redhat.com> (raw)
In-Reply-To: <4CB31EEB.7000306@redhat.com>

  On 10/11/2010 04:27 PM, Avi Kivity wrote:
>  On 10/11/2010 08:49 AM, Neo Jia wrote:
>> On Sun, Oct 10, 2010 at 11:30 PM, Avi Kivity<avi@redhat.com>  wrote:
>> >    On 10/11/2010 07:46 AM, Neo Jia wrote:
>> >>
>> >>  BTW, I have a question about saving FPU, especially those XMM
>> >>  registers. I don't see an explicit save FPU after exiting guest 
>> due to
>> >>  an exception (MMIO writes). The only thing I saw about fpu operation
>> >>  is fpu restore right before loading guest.
>> >>
>> >>  Is there anything I missed here?
>> >
>> >  kvm_put_guest_fpu.
>>
>> I found that function and it will be called by vcpu_put eventually
>> inside kvm_arch_vcpu_ioctl_run, but kvm_mmu_page_fault is called much
>> earlier than that inside kvm exit exception handler. so, the fxsave
>> data for the guest image might not be saved at that moment, when I am
>> going to emulate this instruction?
>
> Just call it when you want to be sure it is in memory.
>

btw, I just found an old branch of mine that implements movdqa, I'll see 
if I can refresh and repost it.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-10-11 14:31 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
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 [this message]
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=4CB31FA9.7080407@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