linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: n.nikolaev@virtualopensystems.com (Nikolay Nikolaev)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 2/5] ARM: on IO mem abort - route the call to KVM MMIO bus
Date: Mon, 24 Nov 2014 23:26:51 +0200	[thread overview]
Message-ID: <20141124212651.10605.58116.stgit@i3820> (raw)
In-Reply-To: <20141124212240.10605.46770.stgit@i3820>

On IO memory abort, try to handle the MMIO access thorugh the KVM
registered read/write callbacks. This is done by invoking the relevant
kvm_io_bus_* API.

Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
---
 arch/arm/kvm/mmio.c |   33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/arch/arm/kvm/mmio.c b/arch/arm/kvm/mmio.c
index 4cb5a93..81230da 100644
--- a/arch/arm/kvm/mmio.c
+++ b/arch/arm/kvm/mmio.c
@@ -162,6 +162,36 @@ static int decode_hsr(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,
 	return 0;
 }
 
+/**
+ * kvm_handle_mmio - handle an in-kernel MMIO access
+ * @vcpu:	pointer to the vcpu performing the access
+ * @run:	pointer to the kvm_run structure
+ * @mmio:	pointer to the data describing the access
+ *
+ * returns true if the MMIO access has been performed in kernel space,
+ * and false if it needs to be emulated in user space.
+ */
+static bool handle_kernel_mmio(struct kvm_vcpu *vcpu, struct kvm_run *run,
+		struct kvm_exit_mmio *mmio)
+{
+	int ret;
+
+	if (mmio->is_write) {
+		ret = kvm_io_bus_write(vcpu, KVM_MMIO_BUS, mmio->phys_addr,
+				mmio->len, &mmio->data);
+
+	} else {
+		ret = kvm_io_bus_read(vcpu, KVM_MMIO_BUS, mmio->phys_addr,
+				mmio->len, &mmio->data);
+	}
+	if (!ret) {
+		kvm_prepare_mmio(run, mmio);
+		kvm_handle_mmio_return(vcpu, run);
+	}
+
+	return !ret;
+}
+
 int io_mem_abort(struct kvm_vcpu *vcpu, struct kvm_run *run,
 		 phys_addr_t fault_ipa)
 {
@@ -200,6 +230,9 @@ int io_mem_abort(struct kvm_vcpu *vcpu, struct kvm_run *run,
 	if (vgic_handle_mmio(vcpu, run, &mmio))
 		return 1;
 
+	if (handle_kernel_mmio(vcpu, run, &mmio))
+		return 1;
+
 	kvm_prepare_mmio(run, &mmio);
 	return 0;
 }

  parent reply	other threads:[~2014-11-24 21:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 21:26 [RFC PATCH 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM Nikolay Nikolaev
2014-11-24 21:26 ` [RFC PATCH 1/5] KVM: redesing kvm_io_bus_ API to pass VCPU structure to the callbacks Nikolay Nikolaev
2014-11-26 17:03   ` Eric Auger
2014-11-24 21:26 ` Nikolay Nikolaev [this message]
2014-11-27 10:19   ` [RFC PATCH 2/5] ARM: on IO mem abort - route the call to KVM MMIO bus Eric Auger
2014-11-29 11:28   ` Christoffer Dall
2014-12-05 12:06     ` Nikolay Nikolaev
2015-01-12 16:21       ` Eric Auger
2015-01-23 22:38         ` Nikolay Nikolaev
2014-11-29 11:29   ` Christoffer Dall
2014-11-24 21:26 ` [RFC PATCH 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend Nikolay Nikolaev
2014-11-27 10:51   ` Eric Auger
2014-11-29  7:14   ` Shannon Zhao
2014-11-29 13:58     ` Nikolay Nikolaev
2014-11-29 11:29   ` Christoffer Dall
2014-11-29 11:29   ` Christoffer Dall
2014-11-29 13:54     ` Nikolay Nikolaev
2014-12-05 12:10       ` Nikolay Nikolaev
2014-12-08 10:51         ` Christoffer Dall
2014-11-29 11:29   ` Christoffer Dall
2014-11-24 21:27 ` [RFC PATCH 4/5] ARM: enable linking against eventfd and irqchip Nikolay Nikolaev
2014-11-26 16:58   ` Eric Auger
2014-11-29  7:18   ` Shannon Zhao
2014-11-29 13:49     ` Nikolay Nikolaev
2014-11-29 14:32       ` Christoffer Dall
2014-11-29 11:29   ` Christoffer Dall
2014-12-05 12:14     ` Nikolay Nikolaev
2014-11-24 21:27 ` [RFC PATCH 5/5] ARM: enable KVM_CAP_IOEVENTFD Nikolay Nikolaev
2014-11-27 11:01 ` [RFC PATCH 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM Eric Auger

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=20141124212651.10605.58116.stgit@i3820 \
    --to=n.nikolaev@virtualopensystems.com \
    --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).