From: alex.bennee@linaro.org (Alex Bennée)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] KVM: arm64: don't single-step for non-emulated faults
Date: Wed, 7 Nov 2018 17:10:31 +0000 [thread overview]
Message-ID: <20181107171031.22573-1-alex.bennee@linaro.org> (raw)
Not all faults handled by handle_exit are instruction emulations. For
example a ESR_ELx_EC_IABT will result in the page tables being updated
but the instruction that triggered the fault hasn't actually executed
yet. We use the simple heuristic of checking for a changed PC before
seeing if kvm_arm_handle_step_debug wants to claim we stepped an
instruction.
Signed-off-by: Alex Benn?e <alex.bennee@linaro.org>
---
arch/arm64/kvm/handle_exit.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c
index e5e741bfffe1..b8252e72f882 100644
--- a/arch/arm64/kvm/handle_exit.c
+++ b/arch/arm64/kvm/handle_exit.c
@@ -214,6 +214,7 @@ static exit_handle_fn kvm_get_exit_handler(struct kvm_vcpu *vcpu)
static int handle_trap_exceptions(struct kvm_vcpu *vcpu, struct kvm_run *run)
{
int handled;
+ unsigned long old_pc = *vcpu_pc(vcpu);
/*
* See ARM ARM B1.14.1: "Hyp traps on instructions
@@ -233,7 +234,8 @@ static int handle_trap_exceptions(struct kvm_vcpu *vcpu, struct kvm_run *run)
* kvm_arm_handle_step_debug() sets the exit_reason on the kvm_run
* structure if we need to return to userspace.
*/
- if (handled > 0 && kvm_arm_handle_step_debug(vcpu, run))
+ if (handled > 0 && *vcpu_pc(vcpu) != old_pc &&
+ kvm_arm_handle_step_debug(vcpu, run))
handled = 0;
return handled;
--
2.17.1
next reply other threads:[~2018-11-07 17:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 17:10 Alex Bennée [this message]
2018-11-07 17:39 ` [RFC PATCH] KVM: arm64: don't single-step for non-emulated faults Peter Maydell
2018-11-07 17:53 ` Peter Maydell
2018-11-08 12:26 ` Alex Bennée
2018-11-07 18:01 ` Mark Rutland
2018-11-07 18:08 ` Mark Rutland
2018-11-08 12:40 ` Alex Bennée
2018-11-08 13:51 ` Mark Rutland
2018-11-08 14:28 ` Alex Bennée
2018-11-08 14:38 ` Peter Maydell
2018-11-09 11:56 ` Mark Rutland
2018-11-09 12:24 ` Alex Bennée
2018-11-09 12:49 ` Mark Rutland
2018-11-09 12:56 ` Peter Maydell
2018-11-09 13:29 ` Mark Rutland
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=20181107171031.22573-1-alex.bennee@linaro.org \
--to=alex.bennee@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).