From: "Jérémy Fanguède" <j.fanguede@virtualopensystems.com>
To: kvmarm@lists.cs.columbia.edu
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org,
"Christoffer Dall" <christoffer.dall@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Jérémy Fanguède" <j.fanguede@virtualopensystems.com>,
tech@virtualopensystems.com,
linux-arm-kernel@lists.infradead.org
Subject: [Qemu-devel] [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl
Date: Tue, 5 May 2015 11:13:11 +0200 [thread overview]
Message-ID: <1430817191-6231-1-git-send-email-j.fanguede@virtualopensystems.com> (raw)
To maintain cache coherency on ARM, we may need a mechanism to flush
the data cache.
This patch implements KVM_FLUSH_DCACHE_GPA vm ioctl which flushes the
data cache at a specified address range. The input argument is a
struct kvm_mem_addr containing the guest physical address and the
length.
Signed-off-by: Jérémy Fanguède <j.fanguede@virtualopensystems.com>
---
arch/arm/kvm/arm.c | 13 +++++++++++++
include/uapi/linux/kvm.h | 6 ++++++
2 files changed, 19 insertions(+)
diff --git a/arch/arm/kvm/arm.c b/arch/arm/kvm/arm.c
index d9631ec..8638fd2 100644
--- a/arch/arm/kvm/arm.c
+++ b/arch/arm/kvm/arm.c
@@ -886,6 +886,19 @@ long kvm_arch_vm_ioctl(struct file *filp,
return 0;
}
+ case KVM_FLUSH_DCACHE_GPA: {
+ struct kvm_mem_addr mem_addr;
+ hva_t hva;
+ gpa_t gpa;
+
+ if (copy_from_user(&mem_addr, argp, sizeof(mem_addr)))
+ return -EFAULT;
+
+ gpa = mem_addr.addr;
+ hva = gfn_to_hva(kvm, gpa_to_gfn(gpa)) | (gpa & ~PAGE_MASK);
+ kvm_flush_dcache_to_poc((void *)hva, mem_addr.len);
+ return 0;
+ }
default:
return -EINVAL;
}
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index 4b60056..3bc599e 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -978,6 +978,11 @@ struct kvm_arm_device_addr {
__u64 addr;
};
+struct kvm_mem_addr {
+ __u64 addr;
+ __u32 len;
+};
+
/*
* Device control API, available with KVM_CAP_DEVICE_CTRL
*/
@@ -1199,6 +1204,7 @@ struct kvm_s390_ucas_mapping {
/* Available with KVM_CAP_S390_IRQ_STATE */
#define KVM_S390_SET_IRQ_STATE _IOW(KVMIO, 0xb5, struct kvm_s390_irq_state)
#define KVM_S390_GET_IRQ_STATE _IOW(KVMIO, 0xb6, struct kvm_s390_irq_state)
+#define KVM_FLUSH_DCACHE_GPA _IOW(KVMIO, 0xb7, struct kvm_mem_addr)
#define KVM_DEV_ASSIGN_ENABLE_IOMMU (1 << 0)
#define KVM_DEV_ASSIGN_PCI_2_3 (1 << 1)
--
1.9.1
next reply other threads:[~2015-05-05 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 9:13 Jérémy Fanguède [this message]
2015-05-06 14:12 ` [Qemu-devel] [RFC] ARM/ARM64: KVM: Implement KVM_FLUSH_DCACHE_GPA ioctl Christoffer Dall
2015-05-07 10:50 ` Jérémy Fanguède
2015-05-07 11:20 ` Christoffer Dall
2015-05-07 14:50 ` Jérémy Fanguède
2015-05-07 15:34 ` Christoffer Dall
2015-05-07 16:56 ` Jérémy Fanguède
2015-05-07 17:01 ` Paolo Bonzini
2015-05-15 11:43 ` Laszlo Ersek
2015-05-15 15:12 ` Christoffer Dall
2015-05-15 15:24 ` Paolo Bonzini
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=1430817191-6231-1-git-send-email-j.fanguede@virtualopensystems.com \
--to=j.fanguede@virtualopensystems.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=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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;
as well as URLs for NNTP newsgroup(s).