* [PATCH] Remove extra local_bh_disable/enable from arch do_softirq
@ 2006-06-25 12:13 Paul Mackerras
2006-06-27 10:08 ` Ingo Molnar
2006-06-27 11:43 ` Martin Schwidefsky
0 siblings, 2 replies; 3+ messages in thread
From: Paul Mackerras @ 2006-06-25 12:13 UTC (permalink / raw)
To: akpm, mingo, schwidefsky; +Cc: linuxppc-dev, linux-kernel
At the moment, powerpc and s390 have their own versions of do_softirq
which include local_bh_disable() and __local_bh_enable() calls. They
end up calling __do_softirq (in kernel/softirq.c) which also does
local_bh_disable/enable.
Apparently the two levels of disable/enable trigger a warning from
some validation code that Ingo is working on, and he would like to see
the outer level removed. But to do that, we have to move the
account_system_vtime calls that are currently in the arch do_softirq()
implementations for powerpc and s390 into the generic __do_softirq()
(this is a no-op for other archs because account_system_vtime is
defined to be an empty inline function on all other archs). This
patch does that.
Signed-off-by: Paul Mackerras <paulus@samba.org>
---
The s390 change here needs to be acked by the s390 folks, in case
there's a subtlety on s390 that I have missed.
diff --git a/arch/powerpc/kernel/irq.c b/arch/powerpc/kernel/irq.c
index 40d4c14..2b52802 100644
--- a/arch/powerpc/kernel/irq.c
+++ b/arch/powerpc/kernel/irq.c
@@ -425,13 +425,8 @@ void do_softirq(void)
local_irq_save(flags);
- if (local_softirq_pending()) {
- account_system_vtime(current);
- local_bh_disable();
+ if (local_softirq_pending())
do_softirq_onstack();
- account_system_vtime(current);
- __local_bh_enable();
- }
local_irq_restore(flags);
}
diff --git a/arch/s390/kernel/irq.c b/arch/s390/kernel/irq.c
index 480b6a5..1eef509 100644
--- a/arch/s390/kernel/irq.c
+++ b/arch/s390/kernel/irq.c
@@ -69,10 +69,6 @@ asmlinkage void do_softirq(void)
local_irq_save(flags);
- account_system_vtime(current);
-
- local_bh_disable();
-
if (local_softirq_pending()) {
/* Get current stack pointer. */
asm volatile("la %0,0(15)" : "=a" (old));
@@ -95,10 +91,6 @@ asmlinkage void do_softirq(void)
__do_softirq();
}
- account_system_vtime(current);
-
- __local_bh_enable();
-
local_irq_restore(flags);
}
diff --git a/kernel/softirq.c b/kernel/softirq.c
index 336f92d..20922c5 100644
--- a/kernel/softirq.c
+++ b/kernel/softirq.c
@@ -81,6 +81,7 @@ asmlinkage void __do_softirq(void)
pending = local_softirq_pending();
+ account_system_vtime(current);
local_bh_disable();
cpu = smp_processor_id();
restart:
@@ -109,6 +110,7 @@ restart:
if (pending)
wakeup_softirqd();
+ account_system_vtime(current);
__local_bh_enable();
}
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] Remove extra local_bh_disable/enable from arch do_softirq
2006-06-25 12:13 [PATCH] Remove extra local_bh_disable/enable from arch do_softirq Paul Mackerras
@ 2006-06-27 10:08 ` Ingo Molnar
2006-06-27 11:43 ` Martin Schwidefsky
1 sibling, 0 replies; 3+ messages in thread
From: Ingo Molnar @ 2006-06-27 10:08 UTC (permalink / raw)
To: Paul Mackerras; +Cc: akpm, schwidefsky, linux-kernel, linuxppc-dev
* Paul Mackerras <paulus@samba.org> wrote:
> At the moment, powerpc and s390 have their own versions of do_softirq
> which include local_bh_disable() and __local_bh_enable() calls. They
> end up calling __do_softirq (in kernel/softirq.c) which also does
> local_bh_disable/enable.
>
> Apparently the two levels of disable/enable trigger a warning from
> some validation code that Ingo is working on, and he would like to see
> the outer level removed. But to do that, we have to move the
> account_system_vtime calls that are currently in the arch do_softirq()
> implementations for powerpc and s390 into the generic __do_softirq()
> (this is a no-op for other archs because account_system_vtime is
> defined to be an empty inline function on all other archs). This
> patch does that.
>
> Signed-off-by: Paul Mackerras <paulus@samba.org>
thanks - this solves the problem nicely.
Acked-by: Ingo Molnar <mingo@elte.hu>
Ingo
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] Remove extra local_bh_disable/enable from arch do_softirq
2006-06-25 12:13 [PATCH] Remove extra local_bh_disable/enable from arch do_softirq Paul Mackerras
2006-06-27 10:08 ` Ingo Molnar
@ 2006-06-27 11:43 ` Martin Schwidefsky
1 sibling, 0 replies; 3+ messages in thread
From: Martin Schwidefsky @ 2006-06-27 11:43 UTC (permalink / raw)
To: Paul Mackerras; +Cc: akpm, linuxppc-dev, mingo, linux-kernel
On Sun, 2006-06-25 at 22:13 +1000, Paul Mackerras wrote:
> At the moment, powerpc and s390 have their own versions of do_softirq
> which include local_bh_disable() and __local_bh_enable() calls. They
> end up calling __do_softirq (in kernel/softirq.c) which also does
> local_bh_disable/enable.
>
> Apparently the two levels of disable/enable trigger a warning from
> some validation code that Ingo is working on, and he would like to see
> the outer level removed. But to do that, we have to move the
> account_system_vtime calls that are currently in the arch do_softirq()
> implementations for powerpc and s390 into the generic __do_softirq()
> (this is a no-op for other archs because account_system_vtime is
> defined to be an empty inline function on all other archs). This
> patch does that.
Nod, Heiko stumbled over that one as well as he ported the lock
validator patch. Moving the account_system_vtime call is the correct
solution.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-06-27 14:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-25 12:13 [PATCH] Remove extra local_bh_disable/enable from arch do_softirq Paul Mackerras
2006-06-27 10:08 ` Ingo Molnar
2006-06-27 11:43 ` Martin Schwidefsky
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).