From: Dave.Martin@arm.com (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] arm64: neon: replace generic definition of may_use_simd()
Date: Thu, 3 Aug 2017 17:23:19 +0100 [thread overview]
Message-ID: <1501777403-9782-2-git-send-email-Dave.Martin@arm.com> (raw)
In-Reply-To: <1501777403-9782-1-git-send-email-Dave.Martin@arm.com>
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
In preparation of modifying the logic that decides whether kernel mode
NEON is allowable, which is required for SVE support, introduce an
implementation of may_use_simd() that reflects the current reality, i.e.,
that SIMD is allowed in any context.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Reviewed-by: Dave Martin <Dave.Martin@arm.com>
---
arch/arm64/include/asm/Kbuild | 1 -
arch/arm64/include/asm/simd.h | 23 +++++++++++++++++++++++
2 files changed, 23 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/include/asm/simd.h
diff --git a/arch/arm64/include/asm/Kbuild b/arch/arm64/include/asm/Kbuild
index f81c7b6..2326e39 100644
--- a/arch/arm64/include/asm/Kbuild
+++ b/arch/arm64/include/asm/Kbuild
@@ -20,7 +20,6 @@ generic-y += rwsem.h
generic-y += segment.h
generic-y += serial.h
generic-y += set_memory.h
-generic-y += simd.h
generic-y += sizes.h
generic-y += switch_to.h
generic-y += trace_clock.h
diff --git a/arch/arm64/include/asm/simd.h b/arch/arm64/include/asm/simd.h
new file mode 100644
index 0000000..96959b5
--- /dev/null
+++ b/arch/arm64/include/asm/simd.h
@@ -0,0 +1,23 @@
+/*
+ * Copyright (C) 2017 Linaro Ltd. <ard.biesheuvel@linaro.org>
+ *
+ * This program is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 as published
+ * by the Free Software Foundation.
+ */
+
+#ifndef __ASM_SIMD_H
+#define __ASM_SIMD_H
+
+#include <linux/types.h>
+
+/*
+ * may_use_simd - whether it is allowable at this time to issue SIMD
+ * instructions or access the SIMD register file
+ */
+static __must_check inline bool may_use_simd(void)
+{
+ return true;
+}
+
+#endif
--
2.1.4
next prev parent reply other threads:[~2017-08-03 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 16:23 [PATCH 0/5] Simplify kernel-mode NEON Dave Martin
2017-08-03 16:23 ` Dave Martin [this message]
2017-08-03 16:23 ` [PATCH 2/5] arm64: neon: Add missing header guard in <asm/neon.h> Dave Martin
2017-08-03 16:23 ` [PATCH 3/5] arm64: fpsimd: Consistently use __this_cpu_ ops where appropriate Dave Martin
2017-08-03 16:23 ` [PATCH 4/5] arm64: neon: Allow EFI runtime services to use FPSIMD in irq context Dave Martin
2017-08-03 16:23 ` [PATCH 5/5] arm64: neon: Remove support for nested or hardirq kernel-mode NEON Dave Martin
2017-08-07 11:23 ` Catalin Marinas
2017-08-07 11:31 ` Ard Biesheuvel
2017-08-07 11:35 ` Catalin Marinas
2017-08-04 12:08 ` [PATCH 0/5] Simplify " Catalin Marinas
2017-08-04 12:22 ` Catalin Marinas
2017-08-04 12:25 ` Ard Biesheuvel
2017-08-04 12:41 ` Dave P Martin
2017-08-04 13:12 ` Catalin Marinas
2017-08-04 13:21 ` Ard Biesheuvel
2017-08-04 13:26 ` Dave P Martin
2017-08-04 14:05 ` Catalin Marinas
2017-08-04 14:25 ` Dave Martin
2017-08-04 14:50 ` Catalin Marinas
2017-08-04 14:00 ` Catalin Marinas
2017-08-04 14:04 ` Ard Biesheuvel
2017-08-04 13:22 ` Dave Martin
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=1501777403-9782-2-git-send-email-Dave.Martin@arm.com \
--to=dave.martin@arm.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).