public inbox for kernel-hardening@lists.openwall.com
 help / color / mirror / Atom feed
From: Emese Revfy <re.emese@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: pageexec@freemail.hu, spender@grsecurity.net,
	kernel-hardening@lists.openwall.com, mmarek@suse.com,
	keescook@chromium.org, linux@rasmusvillemoes.dk,
	fengguang.wu@intel.com, dvyukov@google.com,
	linux-kernel@vger.kernel.org, david.brown@linaro.org,
	yamada.masahiro@socionext.com
Subject: [kernel-hardening] [PATCH v6 3/6] The GCC plugin infrastructure supports the arm and arm64 architectures too
Date: Thu, 7 Apr 2016 23:15:12 +0200	[thread overview]
Message-ID: <20160407231512.23220f5c92914e4db75420c1@gmail.com> (raw)
In-Reply-To: <20160407231023.5f1307ffc79f0cdd880eedb7@gmail.com>

The GCC plugin infrastructure now supports the arm and arm64 architectures too.

Signed-off-by: David Brown <david.brown@linaro.org>
---
 arch/arm/Kconfig   | 1 +
 arch/arm64/Kconfig | 1 +
 2 files changed, 2 insertions(+)

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 0846026..8f57eb6 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -55,6 +55,7 @@ config ARM
 	select HAVE_FUNCTION_GRAPH_TRACER if (!THUMB2_KERNEL)
 	select HAVE_FUNCTION_TRACER if (!XIP_KERNEL)
 	select HAVE_GENERIC_DMA_COHERENT
+	select HAVE_GCC_PLUGINS
 	select HAVE_HW_BREAKPOINT if (PERF_EVENTS && (CPU_V6 || CPU_V6K || CPU_V7))
 	select HAVE_IDE if PCI || ISA || PCMCIA
 	select HAVE_IRQ_TIME_ACCOUNTING
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 4f43622..22c9473 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -72,6 +72,7 @@ config ARM64
 	select HAVE_FTRACE_MCOUNT_RECORD
 	select HAVE_FUNCTION_TRACER
 	select HAVE_FUNCTION_GRAPH_TRACER
+	select HAVE_GCC_PLUGINS
 	select HAVE_GENERIC_DMA_COHERENT
 	select HAVE_HW_BREAKPOINT if PERF_EVENTS
 	select HAVE_IRQ_TIME_ACCOUNTING
-- 
2.4.1

  parent reply	other threads:[~2016-04-07 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-07 21:10 [kernel-hardening] [PATCH v6 0/6] Introduce GCC plugin infrastructure Emese Revfy
2016-04-07 21:11 ` [kernel-hardening] [PATCH v6 1/6] Shared library support Emese Revfy
2016-04-07 21:13 ` [kernel-hardening] [PATCH v6 2/6] GCC plugin infrastructure Emese Revfy
2016-04-13  2:35   ` [kernel-hardening] " Masahiro Yamada
2016-04-21 16:55     ` Kees Cook
2016-04-07 21:15 ` Emese Revfy [this message]
2016-04-07 21:16 ` [kernel-hardening] [PATCH v6 4/6] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-04-07 21:17 ` [kernel-hardening] [PATCH v6 5/6] Documentation for the GCC plugin infrastructure Emese Revfy
2016-04-07 21:19 ` [kernel-hardening] [PATCH v6 6/6] Add sancov plugin Emese Revfy
2016-04-12 17:46 ` [kernel-hardening] Re: [PATCH v6 0/6] Introduce GCC plugin infrastructure David Brown
2016-04-12 18:27   ` Kees Cook
2016-04-12 18:41     ` David Brown
2016-04-12 19:46       ` Kees Cook
2016-04-12 21:26         ` PaX Team
2016-04-12 18:52     ` Emese Revfy
2016-04-12 19:47       ` Kees Cook

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=20160407231512.23220f5c92914e4db75420c1@gmail.com \
    --to=re.emese@gmail.com \
    --cc=david.brown@linaro.org \
    --cc=dvyukov@google.com \
    --cc=fengguang.wu@intel.com \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mmarek@suse.com \
    --cc=pageexec@freemail.hu \
    --cc=spender@grsecurity.net \
    --cc=yamada.masahiro@socionext.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