From: Sven Schnelle <svens@stackframe.org>
To: deller@gmx.de
Cc: linux-parisc@vger.kernel.org, Sven Schnelle <svens@stackframe.org>
Subject: [PATCH v3 5/6] compiler.h: add CC_USING_PATCHABLE_FUNCTION_ENTRY
Date: Wed, 5 Jun 2019 22:32:21 +0200 [thread overview]
Message-ID: <20190605203222.6194-6-svens@stackframe.org> (raw)
In-Reply-To: <20190605203222.6194-1-svens@stackframe.org>
This can be used for architectures implementing dynamic
ftrace via -fpatchable-function-entry.
Signed-off-by: Sven Schnelle <svens@stackframe.org>
---
include/linux/compiler_types.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/compiler_types.h b/include/linux/compiler_types.h
index 19e58b9138a0..095d55c3834d 100644
--- a/include/linux/compiler_types.h
+++ b/include/linux/compiler_types.h
@@ -112,6 +112,8 @@ struct ftrace_likely_data {
#if defined(CC_USING_HOTPATCH)
#define notrace __attribute__((hotpatch(0, 0)))
+#elif defined(CC_USING_PATCHABLE_FUNCTION_ENTRY)
+#define notrace __attribute__((patchable_function_entry(0, 0)))
#else
#define notrace __attribute__((__no_instrument_function__))
#endif
--
2.20.1
next prev parent reply other threads:[~2019-06-05 20:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:32 [PATCH v3 0/6] Dynamic FTRACE for PA-RISC Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 1/6] parisc: add support for patching multiple words Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 2/6] parisc: add spinlock to patch function Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 3/6] parisc: add WARN_ON() to clear_fixmap Sven Schnelle
2019-06-05 20:32 ` [PATCH v3 4/6] parisc: use pr_debug() in kernel/module.c Sven Schnelle
2019-06-05 20:32 ` Sven Schnelle [this message]
2019-06-05 20:32 ` [PATCH v3 6/6] parisc: add dynamic ftrace Sven Schnelle
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=20190605203222.6194-6-svens@stackframe.org \
--to=svens@stackframe.org \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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).