From: Yejune Deng <yejune.deng@gmail.com>
To: peterz@infradead.org, tglx@linutronix.de, mingo@kernel.org,
rafael.j.wysocki@intel.com, rostedt@goodmis.org,
npiggin@gmail.com, mark.rutland@arm.com, yejunedeng@gmail.com,
elver@google.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] irqflags: Remove the CONFIG_TRACE_IRQFLAGS
Date: Mon, 24 May 2021 10:51:19 +0800 [thread overview]
Message-ID: <1621824679-29258-1-git-send-email-yejunedeng@gmail.com> (raw)
trace_hardirqs_on() and trace_hardirqs_off() had include the
CONFIG_TRACE_IRQFLAGS, so remove the redundant CONFIG_TRACE_IRQFLAGS.
Signed-off-by: Yejune Deng <yejunedeng@gmail.com>
---
include/linux/irqflags.h | 16 ----------------
1 file changed, 16 deletions(-)
diff --git a/include/linux/irqflags.h b/include/linux/irqflags.h
index 600c10d..b5edd7b 100644
--- a/include/linux/irqflags.h
+++ b/include/linux/irqflags.h
@@ -189,12 +189,6 @@ extern void warn_bogus_irq_restore(void);
#define raw_irqs_disabled() (arch_irqs_disabled())
#define raw_safe_halt() arch_safe_halt()
-/*
- * The local_irq_*() APIs are equal to the raw_local_irq*()
- * if !TRACE_IRQFLAGS.
- */
-#ifdef CONFIG_TRACE_IRQFLAGS
-
#define local_irq_enable() \
do { \
trace_hardirqs_on(); \
@@ -230,16 +224,6 @@ extern void warn_bogus_irq_restore(void);
} while (0)
-#else /* !CONFIG_TRACE_IRQFLAGS */
-
-#define local_irq_enable() do { raw_local_irq_enable(); } while (0)
-#define local_irq_disable() do { raw_local_irq_disable(); } while (0)
-#define local_irq_save(flags) do { raw_local_irq_save(flags); } while (0)
-#define local_irq_restore(flags) do { raw_local_irq_restore(flags); } while (0)
-#define safe_halt() do { raw_safe_halt(); } while (0)
-
-#endif /* CONFIG_TRACE_IRQFLAGS */
-
#define local_save_flags(flags) raw_local_save_flags(flags)
/*
--
2.7.4
next reply other threads:[~2021-05-24 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 2:51 Yejune Deng [this message]
2021-05-24 11:26 ` [PATCH] irqflags: Remove the CONFIG_TRACE_IRQFLAGS Mark Rutland
2021-05-25 7:03 ` [irqflags] 21db66c4ff: will-it-scale.per_process_ops -4.5% regression kernel test robot
2021-05-28 0:59 ` Steven Rostedt
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=1621824679-29258-1-git-send-email-yejunedeng@gmail.com \
--to=yejune.deng@gmail.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=yejunedeng@gmail.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;
as well as URLs for NNTP newsgroup(s).