From: "Laurent Vivier (Bull)" <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [PATCH 0/5] Split the emulator: decode & execute
Date: Mon, 17 Sep 2007 21:08:01 +0200 [thread overview]
Message-ID: <46EED091.2090404@bull.net> (raw)
In-Reply-To: <46EEB971.9000507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity wrote:
> Laurent Vivier wrote:
>> Avi Kivity wrote:
...
>>> Interesting. I don't see how an instruction fetch can fail on
>>> uniprocessor. Can you give details of the failure?
>>>
>>> Instruction fetches can fail on SMP so a fix is certainly needed.
>>>
>> OK, I spoke too fast.
>>
>> x86_decode_insn() fails because it is not able to decode:
>>
>> 0xffffffff8110b7ef <__copy_user_nocache+47>: movnti %r11,(%rdi)
>> or
>> 0xffffffff8110b7ef <__copy_user_nocache+47>: 0x4c 0x0f 0xc3
0x1f
>>
>> 0x4c is decoded as a REX prefix.
>> 0x0f is decoded as a Two-byte opcode
>> but 0xc3 is unknown in twobyte_table, so we exit because of an
unrecognized
>> opcode ("Cannot emulate").
>>
>>
>
> Not being able to emulate is sometimes legitimate. In the case of
> writing to a write-protected guest page table, we simply
> un-write-protect it and go back to the guest (which should now execute
> the instruction natively).
>
> Perhaps the logic that deals with this (the call to
> kvm_mmu_unprotect_page_virt() in emulate_instruction()) was broken by
> your changes.
>
In fact this case is managed in the error cases of
emulate_instruction(). My first patch removes this management for
instruction decoding because I supposed it cannot generate such errors.
So what I proposed in my last email seems to be the good solution :
emulate_instruction()
...
r = x86_decode_insn(&vcpu->emulate_ctxt, &emulate_ops);
if (r == 0)
r = x86_emulate_insn(&vcpu->emulate_ctxt, &emulate_ops);
...
if (r) {
if (kvm_mmu_unprotect_page_virt(vcpu, cr2))
return EMULATE_DONE;
if (!vcpu->mmio_needed) {
kvm_report_emulation_failure(vcpu, "mmio");
return EMULATE_FAIL;
}
return EMULATE_DO_MMIO;
}
...
Regards,
Laurent
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-17 19:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 16:39 [PATCH 0/5] Split the emulator: decode & execute Laurent Vivier
[not found] ` <46D5A151.80000-6ktuUTfB/bM@public.gmane.org>
2007-08-31 20:26 ` Andi Kleen
[not found] ` <200708312226.23678.ak-l3A5Bk7waGM@public.gmane.org>
2007-09-01 14:19 ` Avi Kivity
2007-09-09 12:15 ` Avi Kivity
[not found] ` <46E3E3D4.1050206-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-12 11:31 ` Laurent Vivier
[not found] ` <46E7CDF5.8050403-6ktuUTfB/bM@public.gmane.org>
2007-09-12 11:40 ` Avi Kivity
2007-09-14 16:14 ` Laurent Vivier
[not found] ` <46EAB36E.2060004-6ktuUTfB/bM@public.gmane.org>
2007-09-14 16:57 ` Avi Kivity
[not found] ` <46EABD97.5060503-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-17 16:14 ` Laurent Vivier
[not found] ` <46EEA801.20404-6ktuUTfB/bM@public.gmane.org>
2007-09-17 17:29 ` Avi Kivity
[not found] ` <46EEB971.9000507-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-17 19:08 ` Laurent Vivier (Bull) [this message]
[not found] ` <46EED091.2090404-6ktuUTfB/bM@public.gmane.org>
2007-09-17 19:16 ` Avi Kivity
[not found] ` <46EED2A2.8090803-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-17 19:59 ` Laurent Vivier
[not found] ` <46EEDC92.80304-6ktuUTfB/bM@public.gmane.org>
2007-09-18 5:59 ` Avi Kivity
[not found] ` <46EF695D.1020203-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-18 7:40 ` Laurent Vivier
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=46EED091.2090404@bull.net \
--to=laurent.vivier-6ktuutfb/bm@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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