From: Andrew Jones <drjones@redhat.com>
To: kvmarm@lists.cs.columbia.edu, qemu-devel@nongnu.org,
ard.biesheuvel@linaro.org, christoffer.dall@linaro.org,
marc.zyngier@arm.com, peter.maydell@linaro.org
Cc: pbonzini@redhat.com, lersek@redhat.com, agraf@suse.de,
catalin.marinas@arm.com
Subject: [Qemu-devel] [RFC PATCH 6/6] KVM: ARM: no need for kvm_arch_flush_incoherent
Date: Fri, 6 Mar 2015 13:52:33 -0500 [thread overview]
Message-ID: <1425667953-3566-7-git-send-email-drjones@redhat.com> (raw)
In-Reply-To: <1425667953-3566-1-git-send-email-drjones@redhat.com>
kvm_arch_flush_incoherent makes things too slow, and we don't
need it. Userspace can flush for us, as the necessary cache
maintenance instruction is not (necessarily) privileged.
Signed-off-by: Andrew Jones <drjones@redhat.com>
---
arch/arm/kvm/mmu.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/kvm/mmu.c b/arch/arm/kvm/mmu.c
index 2f45db9cd436a..b2d87587a9d79 100644
--- a/arch/arm/kvm/mmu.c
+++ b/arch/arm/kvm/mmu.c
@@ -1822,6 +1822,11 @@ int kvm_arch_create_memslot(struct kvm *kvm, struct kvm_memory_slot *slot,
void kvm_arch_flush_incoherent(struct kvm *kvm, struct kvm_memory_slot *slot)
{
+ /*
+ * We no longer need this function, now that userspace does the
+ * flushing.
+ */
+#if 0
if (slot->flags & KVM_MEM_READONLY) {
/*
* Readonly memory shouldn't be changing, and we do a
@@ -1840,6 +1845,7 @@ void kvm_arch_flush_incoherent(struct kvm *kvm, struct kvm_memory_slot *slot)
*/
coherent_cache_memslot(slot, true);
+#endif
}
void kvm_arch_invalidate_incoherent(struct kvm *kvm, struct kvm_memory_slot *slot)
--
1.8.3.1
next prev parent reply other threads:[~2015-03-06 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 18:49 [Qemu-devel] the arm cache coherency cluster Andrew Jones
2015-03-06 18:52 ` [Qemu-devel] [RFC PATCH 0/6] flush/invalidate on entry/exit Andrew Jones
2015-03-06 18:52 ` [Qemu-devel] [RFC PATCH 1/6] kvm: promote KVM_MEMSLOT_INCOHERENT to uapi Andrew Jones
2015-03-06 18:52 ` [Qemu-devel] [RFC PATCH 2/6] KVM: Introduce incoherent cache maintenance API Andrew Jones
2015-03-06 18:52 ` [Qemu-devel] [RFC PATCH 3/6] KVM: ARM: change __coherent_cache_guest_page interface Andrew Jones
2015-03-06 18:52 ` [Qemu-devel] [RFC PATCH 4/6] KVM: ARM: extend __coherent_cache_guest_page Andrew Jones
2015-03-06 18:52 ` [Qemu-devel] [RFC PATCH 5/6] KVM: ARM: implement kvm_*_incoherent_memory_regions Andrew Jones
2015-03-06 18:52 ` Andrew Jones [this message]
2015-03-06 18:53 ` [Qemu-devel] [RFC PATCH 0/6] support KVM_MEM_INCOHERENT Andrew Jones
2015-03-06 18:53 ` [Qemu-devel] [RFC PATCH 1/6] memory: add incoherent cache flag Andrew Jones
2015-03-06 18:53 ` [Qemu-devel] [RFC PATCH 2/6] HACK: linux header update Andrew Jones
2015-03-06 18:53 ` [Qemu-devel] [PATCH 3/6] kvm-all: put kvm_mem_flags to more work Andrew Jones
2015-03-06 18:53 ` [Qemu-devel] [RFC PATCH 4/6] kvm-all: set KVM_MEM_INCOHERENT Andrew Jones
2015-03-06 18:53 ` [Qemu-devel] [RFC PATCH 5/6] vga: flag vram as incoherent Andrew Jones
2015-03-06 18:53 ` [Qemu-devel] [RFC/WIP PATCH 6/6] memory: add clear_cache_to_poc Andrew Jones
2015-03-11 19:21 ` Andrew Jones
2015-03-18 19:00 ` [Qemu-devel] the arm cache coherency cluster Andrew Jones
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=1425667953-3566-7-git-send-email-drjones@redhat.com \
--to=drjones@redhat.com \
--cc=agraf@suse.de \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=lersek@redhat.com \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).