From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 1/2] kvm: arm64: handle single-step during SError exceptions
Date: Thu, 23 Nov 2017 13:33:27 +0100 [thread overview]
Message-ID: <20171123123327.GY28855@cbox> (raw)
In-Reply-To: <20171123121134.11050-2-alex.bennee@linaro.org>
On Thu, Nov 23, 2017 at 12:11:33PM +0000, Alex Benn?e wrote:
> When an SError arrives during single-step it may be delivered before
> the step completes.
nit: this is not entirely accurate wording comparing with the ARM ARM,
which says that the step would be completed, but you'll now have both a
pending debug exception and a pending SError interrupt at the same time,
and the architecture doesn't prevent the SError from being taken first.
I can fix this up on commit though.
> In that case the DBG_SPSR_SS bit will have flipped
> as the instruction executed. After handling the abort in handle_exit()
> we test to see if the bit is clear and we were single-stepping before
> deciding if we need to exit to user space.
>
> Signed-off-by: Alex Benn?e <alex.bennee@linaro.org>
Thanks!
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
> ---
> arch/arm64/kvm/handle_exit.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c
> index 3e645ec9e751..3ba8c4a3bcff 100644
> --- a/arch/arm64/kvm/handle_exit.c
> +++ b/arch/arm64/kvm/handle_exit.c
> @@ -28,6 +28,7 @@
> #include <asm/kvm_emulate.h>
> #include <asm/kvm_mmu.h>
> #include <asm/kvm_psci.h>
> +#include <asm/debug-monitors.h>
>
> #define CREATE_TRACE_POINTS
> #include "trace.h"
> @@ -250,7 +251,12 @@ int handle_exit(struct kvm_vcpu *vcpu, struct kvm_run *run,
> return 1;
> case ARM_EXCEPTION_EL1_SERROR:
> kvm_inject_vabt(vcpu);
> - return 1;
> + /* We may still need to return for single-step */
> + if (!(*vcpu_cpsr(vcpu) & DBG_SPSR_SS)
> + && kvm_arm_handle_step_debug(vcpu, run))
> + return 0;
> + else
> + return 1;
> case ARM_EXCEPTION_TRAP:
> return handle_trap_exceptions(vcpu, run);
> case ARM_EXCEPTION_HYP_GONE:
> --
> 2.15.0
>
next prev parent reply other threads:[~2017-11-23 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 12:11 [PATCH v1 0/2] Additional single-step-cases Alex Bennée
2017-11-23 12:11 ` [PATCH v1 1/2] kvm: arm64: handle single-step during SError exceptions Alex Bennée
2017-11-23 12:33 ` Christoffer Dall [this message]
2017-11-23 12:11 ` [PATCH v1 2/2] kvm: arm64: handle single-step of hyp emulated mmio instructions Alex Bennée
2017-11-23 12:39 ` Christoffer Dall
2017-11-29 16:18 ` [PATCH v1 0/2] Additional single-step-cases Marc Zyngier
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=20171123123327.GY28855@cbox \
--to=cdall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).