From: Alexander van Heukelum <heukelum@fastmail.fm>
To: Ingo Molnar <mingo@elte.hu>, lkml <linux-kernel@vger.kernel.org>
Cc: Alexander van Heukelum <heukelum@fastmail.fm>
Subject: [PATCH 6/7] traps: x86: remove trace_hardirqs_fixup from pagefault handler
Date: Fri, 26 Sep 2008 14:03:07 +0200 [thread overview]
Message-ID: <1222430588-29072-7-git-send-email-heukelum@fastmail.fm> (raw)
In-Reply-To: <1222430588-29072-6-git-send-email-heukelum@fastmail.fm>
The last use of trace_hardirqs_fixup is unnecessary, because the
trap is taken with interrupt off on i386 as well as x86_64, and
the irq-tracer is notified of this from the assembly code.
trace_hardirqs_fixup and trace_hardirqs_fixup_flags are removed
from include/asm-x86/irqflags.h as they are no longer used.
Signed-off-by: Alexander van Heukelum <heukelum@fastmail.fm>
---
arch/x86/mm/fault.c | 5 -----
include/asm-x86/irqflags.h | 21 ---------------------
2 files changed, 0 insertions(+), 26 deletions(-)
diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index 455f3fe..c5bafc9 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -593,11 +593,6 @@ void __kprobes do_page_fault(struct pt_regs *regs, unsigned long error_code)
unsigned long flags;
#endif
- /*
- * We can fault from pretty much anywhere, with unknown IRQ state.
- */
- trace_hardirqs_fixup();
-
tsk = current;
mm = tsk->mm;
prefetchw(&mm->mmap_sem);
diff --git a/include/asm-x86/irqflags.h b/include/asm-x86/irqflags.h
index 424acb4..2bdab21 100644
--- a/include/asm-x86/irqflags.h
+++ b/include/asm-x86/irqflags.h
@@ -166,27 +166,6 @@ static inline int raw_irqs_disabled(void)
return raw_irqs_disabled_flags(flags);
}
-/*
- * makes the traced hardirq state match with the machine state
- *
- * should be a rarely used function, only in places where its
- * otherwise impossible to know the irq state, like in traps.
- */
-static inline void trace_hardirqs_fixup_flags(unsigned long flags)
-{
- if (raw_irqs_disabled_flags(flags))
- trace_hardirqs_off();
- else
- trace_hardirqs_on();
-}
-
-static inline void trace_hardirqs_fixup(void)
-{
- unsigned long flags = __raw_local_save_flags();
-
- trace_hardirqs_fixup_flags(flags);
-}
-
#else
#ifdef CONFIG_X86_64
--
1.5.4.3
next prev parent reply other threads:[~2008-09-26 12:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 12:03 [PATCH 0/7] traps: x86: irqtrace cleanup and some traps.c unification Alexander van Heukelum
2008-09-26 12:03 ` [PATCH 1/7] traps: x86_64: add TRACE_IRQS_OFF in error_entry Alexander van Heukelum
2008-09-26 12:03 ` [PATCH 2/7] traps: x86_64: add TRACE_IRQS_OFF in paranoidentry macro Alexander van Heukelum
2008-09-26 12:03 ` [PATCH 3/7] traps: x86_64: remove trace_hardirqs_fixup from DO_ERROR_INFO macro Alexander van Heukelum
2008-09-26 12:03 ` [PATCH 4/7] traps: x86_64: remove trace_hardirqs_fixup from int3 handler Alexander van Heukelum
2008-09-26 12:03 ` [PATCH 5/7] traps: x86_64: remove trace_hardirqs_fixup from debug handler Alexander van Heukelum
2008-09-26 12:03 ` Alexander van Heukelum [this message]
2008-09-26 12:03 ` [PATCH 7/7] traps: i386: make do_trap more like x86_64 Alexander van Heukelum
2008-09-26 12:39 ` [PATCH 1/7] traps: x86_64: add TRACE_IRQS_OFF in error_entry Alexander van Heukelum
2008-09-27 16:30 ` [PATCH 0/7] traps: x86: irqtrace cleanup and some traps.c unification Ingo Molnar
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=1222430588-29072-7-git-send-email-heukelum@fastmail.fm \
--to=heukelum@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®