[PATCH 3/3] arm64: kvm: Fix single step for guest skipped instructions
Alex Bennée
alex.bennee at linaro.org
Tue Oct 3 08:48:56 PDT 2017
Julien Thierry <julien.thierry at arm.com> writes:
> On 03/10/17 15:57, Alex Bennée wrote:
>>
>> Julien Thierry <julien.thierry at arm.com> writes:
>>
>>> On 31/08/17 15:01, Christoffer Dall wrote:
<snip>
>>>>>>>>>>> On 30/08/17 19:53, Christoffer Dall wrote:
>>>>>>>>>>>> Hi Julien,
>>>>>>>>>>>>
>>>>>>>>>>>> [cc'ing Alex Bennée here who wrote the debug code for arm64]
>>>>>>>>>>>>
<snip>
>>>>> I can try to detail the comment in kvm_arm_setup_debug when we set SPSR,
>>>>> hopefully making things clearer when seeing that part of the code.
>>>>>
>>>>
>>>> I also think we need to improve the comment in the world-switch return
>>>> path, and I'd like Alex to weigh in here before we merge this. He's
>>>> back from holiday on Monday.
>>>>
>>>
>>> Ping Alex?
>>
>> Sorry for the delay getting back to you. I had flagged the email but
>> with holidays and conferences in the way it fell off my queue.
>>
>
> No problem, thanks for looking at it.
>
>> So to summarise as I understand things:
>>
>> Host User Space | Host KVM | Host Hyp | Guest VM |
>>
>> Enable Debug(SS)
>> KVM_RUN ----------->
>> Guest SPSR.SS set
>> --> World Switch ->
>> Insn Trap to Hyp
>> World Switch <-
>> (SS not cleared)
>> <--
>> Insn Emulated
>> pc += 4
>> -->
>> World Switch
>> (SS still set)
>> ->
>> Insn +4 SS
>> <-
>> World Switch
>> (SS cleared)
>>
>> <--
>> Guest exit (debug)
>> <--
>> See SS did 2 insns?
>>
>> Do I understand the problem you are trying to fix correctly?
>
> Yes that's the issue. The debugger is not made aware of the
> emulated/skipped instruction and the hypervisor jumps back into the
> guest.
>
> Clearing SS before jumping back to the guest will simply trigger a
> debug exception as soon as we ERET from EL2 to EL1 (so we end up just
> getting back to EL2).
Why don't we just exit KVM after we've emulated the instruction if we
are under debug? After all at this point whatever needed to be done is
done and the guest debug code can get on with life.
I understand there is the problem of exiting for an MMIO emulation but
maybe that complexity should be handled by userspace ("render unto
userspace the things that are userspaces") and it can decide to lift the
step ioctl if appropriate.
I guess I should have a look at the series. Are you re-basing anytime
soon? It looks like it currently has a few minor merge conflicts with
current master.
--
Alex Bennée
More information about the linux-arm-kernel
mailing list