From: Julien Thierry <julien.thierry@arm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, christoffer.dall@linaro.org,
marc.zyngier@arm.com
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] kvm: arm64: handle single-stepping trapped instructions
Date: Mon, 13 Nov 2017 11:02:59 +0000 [thread overview]
Message-ID: <f71122df-72bb-cea5-7f85-16d3374442b6@arm.com> (raw)
In-Reply-To: <20171109170021.2984-3-alex.bennee@linaro.org>
On 09/11/17 17:00, Alex Bennée wrote:
> If we are using guest debug to single-step the guest we need to ensure
> we exit after emulating the instruction. This only affects
> instructions completely emulated by the kernel. For userspace emulated
> instructions we need to exit and return to complete the emulation.
>
> The kvm_arm_handle_step_debug() helper sets up the necessary exit
> state if needed.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Julien Thierry <julien.thierry@arm.com>
>
> ---
> v2
> - use helper from patch 1
> - if (handled > 0) instead of if (handled) so errors propagate
> ---
> arch/arm64/kvm/handle_exit.c | 47 +++++++++++++++++++++++++++++++-------------
> 1 file changed, 33 insertions(+), 14 deletions(-)
>
> diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c
> index 7debb74843a0..af1c804742f6 100644
> --- a/arch/arm64/kvm/handle_exit.c
> +++ b/arch/arm64/kvm/handle_exit.c
> @@ -178,6 +178,38 @@ static exit_handle_fn kvm_get_exit_handler(struct kvm_vcpu *vcpu)
> return arm_exit_handlers[hsr_ec];
> }
>
> +/*
> + * We may be single-stepping an emulated instruction. If the emulation
> + * has been completed in-kernel we can return to userspace with a
> + * KVM_EXIT_DEBUG, otherwise the userspace needs to complete its
> + * emulation first.
> + */
> +
> +static int handle_trap_exceptions(struct kvm_vcpu *vcpu, struct kvm_run *run)
> +{
> + int handled;
> +
> + /*
> + * See ARM ARM B1.14.1: "Hyp traps on instructions
> + * that fail their condition code check"
> + */
> + if (!kvm_condition_valid(vcpu)) {
> + kvm_skip_instr(vcpu, kvm_vcpu_trap_il_is32bit(vcpu));
> + handled = 1;
> + } else {
> + exit_handle_fn exit_handler;
> +
> + exit_handler = kvm_get_exit_handler(vcpu);
> + handled = exit_handler(vcpu, run);
> + }
> +
> + /* helper sets exit_reason if we need to return to userspace */
> + if (handled > 0 && kvm_arm_handle_step_debug(vcpu, run))
> + handled = 0;
> +
> + return handled;
> +}
> +
> /*
> * Return > 0 to return to guest, < 0 on error, 0 (and set exit_reason) on
> * proper exit to userspace.
> @@ -185,8 +217,6 @@ static exit_handle_fn kvm_get_exit_handler(struct kvm_vcpu *vcpu)
> int handle_exit(struct kvm_vcpu *vcpu, struct kvm_run *run,
> int exception_index)
> {
> - exit_handle_fn exit_handler;
> -
> if (ARM_SERROR_PENDING(exception_index)) {
> u8 hsr_ec = ESR_ELx_EC(kvm_vcpu_get_hsr(vcpu));
>
> @@ -214,18 +244,7 @@ int handle_exit(struct kvm_vcpu *vcpu, struct kvm_run *run,
> kvm_inject_vabt(vcpu);
> return 1;
> case ARM_EXCEPTION_TRAP:
> - /*
> - * See ARM ARM B1.14.1: "Hyp traps on instructions
> - * that fail their condition code check"
> - */
> - if (!kvm_condition_valid(vcpu)) {
> - kvm_skip_instr(vcpu, kvm_vcpu_trap_il_is32bit(vcpu));
> - return 1;
> - }
> -
> - exit_handler = kvm_get_exit_handler(vcpu);
> -
> - return exit_handler(vcpu, run);
> + return handle_trap_exceptions(vcpu, run);
> case ARM_EXCEPTION_HYP_GONE:
> /*
> * EL2 has been reset to the hyp-stub. This happens when a guest
>
--
Julien Thierry
next prev parent reply other threads:[~2017-11-13 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171109170021.2984-1-alex.bennee@linaro.org>
2017-11-09 17:00 ` [PATCH v2 1/3] kvm: arm debug: introduce helper for single-step Alex Bennée
2017-11-10 7:47 ` [PATCH] fixup! " Alex Bennée
2017-11-13 9:32 ` [PATCH v2 1/3] " Julien Thierry
2017-11-09 17:00 ` [PATCH v2 2/3] kvm: arm64: handle single-stepping trapped instructions Alex Bennée
2017-11-13 11:02 ` Julien Thierry [this message]
2017-11-09 17:00 ` [PATCH v2 3/3] kvm: arm64: handle single-step of userspace mmio instructions Alex Bennée
2017-11-13 11:04 ` Julien Thierry
2017-11-13 14:39 ` Alex Bennée
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=f71122df-72bb-cea5-7f85-16d3374442b6@arm.com \
--to=julien.thierry@arm.com \
--cc=alex.bennee@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®