]> xenbits.xensource.com Git - people/julieng/linux-arm.git/commitdiff
arm/kvm: Introduce a new VMID allocator
authorJulien Grall <julien.grall@arm.com>
Wed, 19 Dec 2018 15:33:24 +0000 (15:33 +0000)
committerJulien Grall <julien.grall@arm.com>
Thu, 20 Jun 2019 12:45:12 +0000 (13:45 +0100)
A follow-up patch will replace the KVM VMID allocator with the arm64 ASID
allocator.

To avoid as much as possible duplication, the arm KVM code will directly
compile arch/arm64/lib/asid.c. The header is a verbatim to copy to
avoid breaking the assumption that architecture port has self-containers
headers.

Signed-off-by: Julien Grall <julien.grall@arm.com>
Cc: Russell King <linux@armlinux.org.uk>
---
    I hit a warning when compiling the ASID code:

linux/arch/arm/kvm/../../arm64/lib/asid.c:17: warning: "ASID_MASK" redefined
 #define ASID_MASK(info)   (~GENMASK((info)->bits - 1, 0))

In file included from linux/include/linux/mm_types.h:18,
                 from linux/include/linux/mmzone.h:21,
                 from linux/include/linux/gfp.h:6,
                 from linux/include/linux/slab.h:15,
                 from linux/arch/arm/kvm/../../arm64/lib/asid.c:11:
linux/arch/arm/include/asm/mmu.h:26: note: this is the location of the previous definition
 #define ASID_MASK ((~0ULL) << ASID_BITS)

I haven't yet resolved because I am not sure of the best way to go.
AFAICT ASID_MASK is only used in mm/context.c. So I am wondering whether
it would be acceptable to move the define.

    Changes in v2:
        - Re-use arm64/lib/asid.c rather than duplication the code.

arch/arm/include/asm/lib_asid.h [new file with mode: 0644]
arch/arm/kvm/Makefile

diff --git a/arch/arm/include/asm/lib_asid.h b/arch/arm/include/asm/lib_asid.h
new file mode 100644 (file)
index 0000000..79bce46
--- /dev/null
@@ -0,0 +1,81 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#ifndef __ARM_LIB_ASID_H__
+#define __ARM_LIB_ASID_H__
+
+#include <linux/atomic.h>
+#include <linux/compiler.h>
+#include <linux/cpumask.h>
+#include <linux/percpu.h>
+#include <linux/spinlock.h>
+
+struct asid_info
+{
+       atomic64_t      generation;
+       unsigned long   *map;
+       atomic64_t __percpu     *active;
+       u64 __percpu            *reserved;
+       u32                     bits;
+       /* Lock protecting the structure */
+       raw_spinlock_t          lock;
+       /* Which CPU requires context flush on next call */
+       cpumask_t               flush_pending;
+       /* Number of ASID allocated by context (shift value) */
+       unsigned int            ctxt_shift;
+       /* Callback to locally flush the context. */
+       void                    (*flush_cpu_ctxt_cb)(void);
+       /* Callback to call when a context is updated */
+       void                    (*update_ctxt_cb)(void *ctxt);
+};
+
+#define NUM_ASIDS(info)                        (1UL << ((info)->bits))
+#define NUM_CTXT_ASIDS(info)           (NUM_ASIDS(info) >> (info)->ctxt_shift)
+
+#define active_asid(info, cpu) *per_cpu_ptr((info)->active, cpu)
+
+void asid_new_context(struct asid_info *info, atomic64_t *pasid,
+                     unsigned int cpu, void *ctxt);
+
+/*
+ * Check the ASID is still valid for the context. If not generate a new ASID.
+ *
+ * @pasid: Pointer to the current ASID batch
+ * @cpu: current CPU ID. Must have been acquired throught get_cpu()
+ */
+static inline void asid_check_context(struct asid_info *info,
+                                      atomic64_t *pasid, unsigned int cpu,
+                                      void *ctxt)
+{
+       u64 asid, old_active_asid;
+
+       asid = atomic64_read(pasid);
+
+       /*
+        * The memory ordering here is subtle.
+        * If our active_asid is non-zero and the ASID matches the current
+        * generation, then we update the active_asid entry with a relaxed
+        * cmpxchg. Racing with a concurrent rollover means that either:
+        *
+        * - We get a zero back from the cmpxchg and end up waiting on the
+        *   lock. Taking the lock synchronises with the rollover and so
+        *   we are forced to see the updated generation.
+        *
+        * - We get a valid ASID back from the cmpxchg, which means the
+        *   relaxed xchg in flush_context will treat us as reserved
+        *   because atomic RmWs are totally ordered for a given location.
+        */
+       old_active_asid = atomic64_read(&active_asid(info, cpu));
+       if (old_active_asid &&
+           !((asid ^ atomic64_read(&info->generation)) >> info->bits) &&
+           atomic64_cmpxchg_relaxed(&active_asid(info, cpu),
+                                    old_active_asid, asid))
+               return;
+
+       asid_new_context(info, pasid, cpu, ctxt);
+}
+
+int asid_allocator_init(struct asid_info *info,
+                       u32 bits, unsigned int asid_per_ctxt,
+                       void (*flush_cpu_ctxt_cb)(void),
+                       void (*update_ctxt_cb)(void *ctxt));
+
+#endif /* __ARM_LIB_ASID_H__ */
index 531e59f5be9c8f77370b926f5b77f2f8189e77ca..6ab49bd845319dfbba5e1c726f07de682f640522 100644 (file)
@@ -40,3 +40,4 @@ obj-y += $(KVM)/arm/vgic/vgic-its.o
 obj-y += $(KVM)/arm/vgic/vgic-debug.o
 obj-y += $(KVM)/irqchip.o
 obj-y += $(KVM)/arm/arch_timer.o
+obj-y += ../../arm64/lib/asid.o