From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, x86@kernel.org,
Borislav Petkov <bp@alien8.de>
Subject: [RFC][PATCH 0/2 v2] tracing/x86_32: Remove non DYNAMIC_FTRACE and mcount support
Date: Fri, 10 May 2019 12:35:19 -0400 [thread overview]
Message-ID: <20190510163519.794235443@goodmis.org> (raw)
There's no need to support either DYNAMIC_FTRACE=n or mcount (non fentry)
in x86_32. As the static tracing (DYNAMIC_FTRACE=n) does not support
fentry, we can just remove it, as the static tracing is only around to
test the static tracing in generic code as other architectures have it
but not DYNAMIC_FTRACE.
This will allow also allow us to remove klp_check_compiler_support()
in later patches.
Steven Rostedt (VMware) (2):
ftrace/x86_32: Remove support for non DYNAMIC_FTRACE
ftrace/x86: Remove mcount support
----
arch/x86/Kconfig | 11 ++++++
arch/x86/include/asm/ftrace.h | 8 ++---
arch/x86/include/asm/livepatch.h | 3 --
arch/x86/kernel/ftrace_32.S | 75 +++-------------------------------------
arch/x86/kernel/ftrace_64.S | 28 +--------------
5 files changed, 20 insertions(+), 105 deletions(-)
next reply other threads:[~2019-05-10 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 16:35 Steven Rostedt [this message]
2019-05-10 16:35 ` [RFC][PATCH 1/2 v2] ftrace/x86_32: Remove support for non DYNAMIC_FTRACE Steven Rostedt
2019-05-10 16:35 ` [RFC][PATCH 2/2 v2] ftrace/x86: Remove mcount support Steven Rostedt
2019-05-10 16:43 ` [RFC][PATCH 0/2 v2] tracing/x86_32: Remove non DYNAMIC_FTRACE and " Steven Rostedt
2019-05-10 21:47 ` [RFC][PATCH 3/2] livepatch: remove klp_check_compiler_support() Jiri Kosina
2019-05-10 21:54 ` Steven Rostedt
2019-05-10 21:58 ` Josh Poimboeuf
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=20190510163519.794235443@goodmis.org \
--to=rostedt@goodmis.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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