From: Masami Hiramatsu <mhiramat@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Francis Deslauriers <francis.deslauriers@efficios.com>,
mathieu.desnoyers@efficios.com, Ingo Molnar <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S . Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -tip v5 1/2] irq: Introduce CONFIG_IRQENTRY kconfig
Date: Fri, 28 Jul 2017 18:07:29 +0900 [thread overview]
Message-ID: <20170728180729.572a625a88005fe9802bdcd7@kernel.org> (raw)
In-Reply-To: <20170728063603.gmew42j5luosk5hw@gmail.com>
On Fri, 28 Jul 2017 08:36:03 +0200
Ingo Molnar <mingo@kernel.org> wrote:
>
> * Masami Hiramatsu <mhiramat@kernel.org> wrote:
>
> > Introduce CONFIG_IRQENTRY to simplify generating
> > irqentry and softirqentry text sections.
> > Currently generating those sections depends on
> > CONFIG_FUNCTION_GRAPH_TRACER and/or CONFIG_KASAN, in
> > each source code. This moves those #ifdef dependencies
> > into Kconfig, instead of the actual code. This makes
> > it scalable for other user of irqentry section.
>
> Please just make it unconditional. That would remove a number of messy #ifdefs,
> and extra sections/symbols don't have much if any cost.
OK, I'll fix that and resend soon.
Thanks!
>
> Thanks,
>
> Ingo
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2017-07-28 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 16:18 Masami Hiramatsu
2017-07-27 16:19 ` [PATCH -tip v5 2/2] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code Masami Hiramatsu
2017-07-28 6:36 ` [PATCH -tip v5 1/2] irq: Introduce CONFIG_IRQENTRY kconfig Ingo Molnar
2017-07-28 9:07 ` Masami Hiramatsu [this message]
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=20170728180729.572a625a88005fe9802bdcd7@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=francis.deslauriers@efficios.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
Powered by JetHome