In previous patch, we have umasked the Abort/SError bit for Xen
in most of its running time. So in some use-cases, we have to
check whether the abort is enabled in current context. For example,
while we want to synchronize SErrors, we have to confirm the abort
is enabled. Otherwise synchronize SErrors is pointless.
Signed-off-by: Wei Chen <wei.c...@arm.com>
---
v3->v4:
Use one local_abort_is_enabled for ARM32 and ARM64.
---
xen/include/asm-arm/system.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/xen/include/asm-arm/system.h b/xen/include/asm-arm/system.h
index 2eb96e8..b94e56f 100644
--- a/xen/include/asm-arm/system.h
+++ b/xen/include/asm-arm/system.h
@@ -51,6 +51,13 @@
# error "unknown ARM variant"
#endif
+static inline int local_abort_is_enabled(void)
+{
+ unsigned long flags;
+ local_save_flags(flags);
+ return !(flags & PSR_ABT_MASK);
+}
+
#define arch_fetch_and_add(x, v) __sync_fetch_and_add(x, v)
extern struct vcpu *__context_switch(struct vcpu *prev, struct vcpu *next);
--
2.7.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
